ddterm fails to start on Alpine Linux

[tony1016]

GNOME Shell version

GNOME Shell 44.3

Session type

Wayland (echo $WAYLAND_DISPLAY output is non-empty)

Special configuration

• High DPI
• More than one monitor

ddterm version

Version: 47

Linux distro

Alpine Linux 3.18

ddterm settings dump

[/]
background-opacity=0.65000000000000002
ddterm-toggle-hotkey=['<Control>grave']
force-x11-gdk-backend=false
panel-icon-type='toggle-and-menu-button'
show-animation='disable'
show-animation-duration=0.10000000000000001
theme-variant='dark'
transparent-background=true
window-maximize=false
window-position='top'
window-resizable=false
window-size=0.78148854961832059
window-type-hint='normal'

Description

Last version is ok.Fail to open after version update.

[amezin]

Bug report without any error messages doesn't help much.

Please do the following:

1. Log out
2. Login
3. Without pressing ddterm's hotkey/shortcut, open GNOME Terminal/Console
4. Start journalctl -f in GNOME Terminal/Console
5. Press ddterm's hotkey/shortcut
6. Wait for ~1 minute
7. Paste all output from GNOME Terminal/Console here

[tony1016]

Sorry but alpine linux doesn't use journalctl.I try to find logs but there's none . Aleksandr Mezin ***@***.***> 于2023年10月30日周一 01:33写道：

…

Bug report without any error messages doesn't help much. Please do the following: 1. Log out 2. Login 3. Without pressing ddterm's hotkey/shortcut, open GNOME Terminal/Console 4. Start journalctl -f in GNOME Terminal/Console 5. Press ddterm's hotkey/shortcut 6. Copy journalctl -f output here — Reply to this email directly, view it on GitHub <#629 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ5SSUSMUIJPE3MPJAGHWLYB3YWTAVCNFSM6AAAAAA6UR2IEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUGM2DAOJQGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[amezin]

You'll have to figure out where GNOME Shell writes session logs on your system - otherwise I won't be able to help

[tony1016]

Ok, I will do that. Aleksandr Mezin ***@***.***> 于2023年10月30日周一 10:30写道：

…

You'll have to figure out where GNOME Shell writes session logs on your system - otherwise I won't be able to help — Reply to this email directly, view it on GitHub <#629 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQ5SSXGYWWXA267INX23JLYB4GM7AVCNFSM6AAAAAA6UR2IEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBUGM4DANBZGY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[amezin]

So the issue is likely that busybox's realpath doesn't understand --: #726

If still relevant, you should be able to fix this issue by editing ~/.local/share/gnome-shell/extensions/ddterm@amezin.github.com/bin/com.github.amezin.ddterm: replace every realpath -- with just realpath (there are two of them)

By the way, session logs are stored in ~/.cache/gdm/session.log.

[tony1016]

So the issue is likely that busybox's realpath doesn't understand --: #726

If still relevant, you should be able to fix this issue by editing ~/.local/share/gnome-shell/extensions/ddterm@amezin.github.com/bin/com.github.amezin.ddterm: replace every realpath -- with just realpath (there are two of them)

By the way, session logs are stored in ~/.cache/gdm/session.log.

Yes confirm that