Discussion:
Unable to start gnome-terminal from KDE session
(too old to reply)
Jeremy Brown
2017-06-07 17:46:54 UTC
Permalink
Raw Message
Hello arch-general!

I have a laptop running the latest KDE / Plasma, but I use gnome-terminal as my
terminal app. Recently I noticed that when I launch gnome-terminal from the
KDE start menu, it takes an incredibly long time to launch (maybe 20+ seconds)
and when it does launch, I just get a flashing prompt with no actual shell. If
I launch a second gnome-terminal after that, *that* gnome-terminal seems fine.
I get a normal working shell. If I launch xterm then the xterm is fine.

Running "journalctl -f" while I launch the initial gnome-terminal instance
shows:

-------
Jun 08 02:37:24 fourroses.brownjava.org kwin_x11[8054]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 62818, resource id: 37749768, major code: 18 (ChangeProperty), minor code: 0
Jun 08 02:37:24 fourroses.brownjava.org dbus-daemon[599]: Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service'
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: Starting GNOME Terminal Server...
Jun 08 02:37:24 fourroses.brownjava.org gnome-terminal-[10554]: Theme parsing error: gtk.css:68:35: The style property GtkButton:child-displacement-x is deprecated and shouldn't be used anymore. It will be removed in a future version
Jun 08 02:37:24 fourroses.brownjava.org gnome-terminal-[10554]: Theme parsing error: gtk.css:69:35: The style property GtkButton:child-displacement-y is deprecated and shouldn't be used anymore. It will be removed in a future version
Jun 08 02:37:24 fourroses.brownjava.org gnome-terminal-[10554]: Theme parsing error: gtk.css:71:36: The style property GtkCheckMenuItem:indicator-size is deprecated and shouldn't be used anymore. It will be removed in a future version
Jun 08 02:37:24 fourroses.brownjava.org gnome-terminal-[10554]: Theme parsing error: gtk.css:76:30: The style property GtkExpander:expander-size is deprecated and shouldn't be used anymore. It will be removed in a future version
Jun 08 02:37:24 fourroses.brownjava.org dbus-daemon[599]: Successfully activated service 'org.gnome.Terminal'
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: Started GNOME Terminal Server.
Jun 08 02:37:24 fourroses.brownjava.org dbus-daemon[599]: Activating via systemd: service name='org.freedesktop.portal.Desktop' unit='xdg-desktop-portal.service'
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: Starting Portal service...
Jun 08 02:37:24 fourroses.brownjava.org dbus-daemon[599]: Activating service name='org.freedesktop.impl.portal.desktop.kde'
Jun 08 02:37:24 fourroses.brownjava.org dbus-daemon[599]: Activated service 'org.freedesktop.impl.portal.desktop.kde' failed: Failed to execute program org.freedesktop.impl.portal.desktop.kde: No such file or directory
Jun 08 02:37:24 fourroses.brownjava.org xdg-desktop-por[10558]: Failed to create file chooser proxy: Error calling StartServiceByName for org.freedesktop.impl.portal.desktop.kde: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.impl.portal.desktop.kde: No such file or directory
Jun 08 02:37:24 fourroses.brownjava.org xdg-desktop-por[10558]: g_dbus_interface_skeleton_set_flags: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Jun 08 02:37:24 fourroses.brownjava.org xdg-desktop-por[10558]: invalid (NULL) pointer instance
Jun 08 02:37:24 fourroses.brownjava.org xdg-desktop-por[10558]: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
Jun 08 02:37:24 fourroses.brownjava.org xdg-desktop-por[10558]: g_dbus_interface_skeleton_export: assertion 'G_IS_DBUS_INTERFACE_SKELETON (interface_)' failed
Jun 08 02:37:24 fourroses.brownjava.org kernel: xdg-desktop-por[10558]: segfault at 8 ip 0000000000407240 sp 00007ffeb591a140 error 4 in xdg-desktop-portal[400000+5b000]
Jun 08 02:37:24 fourroses.brownjava.org systemd[1]: Started Process Core Dump (PID 10569/UID 0).
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: xdg-desktop-portal.service: Main process exited, code=dumped, status=11/SEGV
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: Failed to start Portal service.
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: xdg-desktop-portal.service: Unit entered failed state.
Jun 08 02:37:24 fourroses.brownjava.org systemd[574]: xdg-desktop-portal.service: Failed with result 'core-dump'.
Jun 08 02:37:24 fourroses.brownjava.org systemd-coredump[10570]: Process 10558 (xdg-desktop-por) of user 1000 dumped core.

Stack trace of thread 10558:
#0 0x0000000000407240 n/a (xdg-desktop-portal)
#1 0x0000000000407305 n/a (xdg-desktop-portal)
#2 0x00007f87235af664 n/a (libgio-2.0.so.0)
#3 0x00007f8723573643 n/a (libgio-2.0.so.0)
#4 0x00007f8723574106 n/a (libgio-2.0.so.0)
#5 0x00007f87235a20d2 n/a (libgio-2.0.so.0)
#6 0x00007f8723573643 n/a (libgio-2.0.so.0)
#7 0x00007f8723573679 n/a (libgio-2.0.so.0)
#8 0x00007f8722fcd66a g_main_context_dispatch (libglib-2.0.so.0)
#9 0x00007f8722fcda20 n/a (libglib-2.0.so.0)
#10 0x00007f8722fcdd42 g_main_loop_run (libglib-2.0.so.0)
#11 0x0000000000406c65 n/a (xdg-desktop-portal)
#12 0x00007f87229e043a __libc_start_main (libc.so.6)
#13 0x0000000000406f2a n/a (xdg-desktop-portal)

Stack trace of thread 10561:
#0 0x00007f8722aa83b9 syscall (libc.so.6)
#1 0x00007f872301344a g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f8722fa1f49 n/a (libglib-2.0.so.0)
#3 0x00007f8722ff5c66 n/a (libglib-2.0.so.0)
#4 0x00007f8722ff5295 n/a (libglib-2.0.so.0)
#5 0x00007f8722d6c297 start_thread (libpthread.so.0)
#6 0x00007f8722aad25f __clone (libc.so.6)

Stack trace of thread 10560:
#0 0x00007f8722aa32bd poll (libc.so.6)
#1 0x00007f8722fcd9b6 n/a (libglib-2.0.so.0)
#2 0x00007f8722fcdd42 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f87235b4f86 n/a (libgio-2.0.so.0)
#4 0x00007f8722ff5295 n/a (libglib-2.0.so.0)
#5 0x00007f8722d6c297 start_thread (libpthread.so.0)
#6 0x00007f8722aad25f __clone (libc.so.6)

Stack trace of thread 10562:
#0 0x00007f8722aa32bd poll (libc.so.6)
#1 0x00007f8722fcd9b6 n/a (libglib-2.0.so.0)
#2 0x00007f8722fcdacc g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f8719afa55d n/a (libdconfsettings.so)
#4 0x00007f8722ff5295 n/a (libglib-2.0.so.0)
#5 0x00007f8722d6c297 start_thread (libpthread.so.0)
#6 0x00007f8722aad25f __clone (libc.so.6)

Stack trace of thread 10559:
#0 0x00007f8722aa32bd poll (libc.so.6)
#1 0x00007f8722fcd9b6 n/a (libglib-2.0.so.0)
#2 0x00007f8722fcdacc g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f8722fcdb11 n/a (libglib-2.0.so.0)
#4 0x00007f8722ff5295 n/a (libglib-2.0.so.0)
#5 0x00007f8722d6c297 start_thread (libpthread.so.0)
#6 0x00007f8722aad25f __clone (libc.so.6)
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: Creating the cache for: "applications:org.gnome.Terminal.desktop"
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: Already in database? true
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: First update : QDateTime(2016-08-27 06:51:33.000 JST Qt::TimeSpec(LocalTime))
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: Last update : QDateTime(2017-06-08 02:36:44.000 JST Qt::TimeSpec(LocalTime))
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: After the adjustment
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: Current score : 39.4505
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: First update : QDateTime(2016-08-27 06:51:33.000 JST Qt::TimeSpec(LocalTime))
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: Last update : QDateTime(2017-06-08 02:36:44.000 JST Qt::TimeSpec(LocalTime))
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: Interval length is 0
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: New score : 40.4505
Jun 08 02:37:25 fourroses.brownjava.org kactivitymanagerd[8102]: ResourceScoreUpdated: "e0ccd030-50ca-4cbc-a4d7-ccb8e06c72a9" "org.kde.krunner" "applications:org.gnome.Terminal.desktop"
Jun 08 02:37:25 fourroses.brownjava.org plasmashell[8062]: KActivitiesStats( 0x5c0c5d0 ) ResultModelPrivate::onResultScoreUpdated result added: "applications:org.gnome.Terminal.desktop" score: 40.4505 last: 1496857044 first: 1472248293
-------


Googling that core dump led me to:

https://bbs.archlinux.org/viewtopic.php?id=224787

...which led me to:

https://github.com/flatpak/xdg-desktop-portal-gtk/issues/72

...which sounds a bit like what I'm seeing, at least the slowness part.
However, I use SDDM, so I can't put the recommended
dbus-update-activation-environment in any .xinitrc file (which is only run when
you do startx as far as I know).

So, two questions:

(1) Where would I put this command so that it's run by SDDM on login?

(2) Is there a bug here where some script in /etc somewhere should be doing
this? I poked around thinking maybe there was a .pacnew for some Xorg / SDDM
related file that might have this, but I didn't see anything. Mostly just
wondering if I should file a bug.

Jeremy
Vladimir Lomov via arch-general
2017-06-08 12:28:38 UTC
Permalink
Raw Message
Hello,
Post by Jeremy Brown
Hello arch-general!
I have a laptop running the latest KDE / Plasma, but I use gnome-terminal as my
terminal app. Recently I noticed that when I launch gnome-terminal from the
KDE start menu, it takes an incredibly long time to launch (maybe 20+ seconds)
and when it does launch, I just get a flashing prompt with no actual shell. If
I launch a second gnome-terminal after that, *that* gnome-terminal seems fine.
I get a normal working shell. If I launch xterm then the xterm is fine.
Running "journalctl -f" while I launch the initial gnome-terminal instance
[...]
Post by Jeremy Brown
https://bbs.archlinux.org/viewtopic.php?id=224787
https://github.com/flatpak/xdg-desktop-portal-gtk/issues/72
...which sounds a bit like what I'm seeing, at least the slowness part.
However, I use SDDM, so I can't put the recommended
dbus-update-activation-environment in any .xinitrc file (which is only run when
you do startx as far as I know).
/etc/sddm.conf:
...
# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/Xsession
...

/usr/share/sddm/scripts/Xsession:
...
USERXSESSION=$HOME/.xsession
...
if [ -f "$USERXSESSION" ]; then
. "$USERXSESSION"
fi

https://bbs.archlinux.org/viewtopic.php?id=224787

dumblob:
...
and the solution seems to be adding

dbus-update-activation-environment --systemd DBUS_SESSION_BUS_ADDRESS
DISPLAY XAUTHORITY

to .xinitrc or .xsession .
Post by Jeremy Brown
(1) Where would I put this command so that it's run by SDDM on login?
(2) Is there a bug here where some script in /etc somewhere should be doing
this? I poked around thinking maybe there was a .pacnew for some Xorg / SDDM
related file that might have this, but I didn't see anything. Mostly just
wondering if I should file a bug.
Jeremy
---
WBR, Vladimir Lomov
--
A young married couple had their first child. Their original pride
and joy slowly turned to concern however, for after a couple of years the
child had never uttered any form of speech. They hired the best speech
therapists, doctors, psychiatrists, all to no avail. The child simply refused
to speak. One morning when the child was five, while the husband was reading
the paper, and the wife was feeding the dog, the little kid looks up from
his bowl and said, "My cereal's cold."
The couple is stunned. The man, in tears, confronts his son. "Son,
after all these years, why have you waited so long to say something?".
Shrugs the kid, "Everything's been okay 'til now".
Damjan Georgievski via arch-general
2017-06-08 12:43:08 UTC
Permalink
Raw Message
Post by Jeremy Brown
...which sounds a bit like what I'm seeing, at least the slowness part.
However, I use SDDM, so I can't put the recommended
dbus-update-activation-environment in any .xinitrc file (which is only run when
you do startx as far as I know).
(1) Where would I put this command so that it's run by SDDM on login?
isn't that already done via:
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh


which is sourced by /usr/share/sddm/scripts/Xsession
--
damjan
Jeremy Brown
2017-06-19 17:11:14 UTC
Permalink
Raw Message
Post by Damjan Georgievski via arch-general
Post by Jeremy Brown
...which sounds a bit like what I'm seeing, at least the slowness part.
However, I use SDDM, so I can't put the recommended
dbus-update-activation-environment in any .xinitrc file (which is only run when
you do startx as far as I know).
(1) Where would I put this command so that it's run by SDDM on login?
/etc/X11/xinit/xinitrc.d/50-systemd-user.sh
which is sourced by /usr/share/sddm/scripts/Xsession
Sorry for the insanely slow follow up.

I think I was hitting a different issue. I just updated plasma-desktop and it
suddenly appears to be working now, so I think it was just a plasma bug.

Cheers,

Jeremy

Loading...