[Bug 1716967] Re: Amarok causes gnome-shell to crash

2017-09-22 Thread monochromec
Please close this one as I filed a new, more fitting bug report: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1718993. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/1716967 Title:

[Bug 1716967] Re: Amarok causes gnome-shell to crash

2017-09-18 Thread monochromec
Apparently this is caused by a rogue Gnome Shell extension. Running gnome-shell inside a gdb session reveals the following BT after the crash: ... Thread 1 "gnome-shell" received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:58 58

[Bug 1716967] Re: Amarok causes gnome-shell to crash

2017-09-13 Thread monochromec
The gnome shell seems to be the only environment affected by this issue - I tried Plasma, Cinnamon, XFCE and Mate. None of them crash when Amarok exits. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to amarok in Ubuntu.

[Bug 1716967] [NEW] Amarok causes gnome-shell to crash

2017-09-13 Thread monochromec
Public bug reported: The subject says it all: when quitting Amarok, the surrounding gnome- shell is restarted. Apparently, something sends a SIGABRT to the shell: Sep 13 18:17:45 darkstar-xps kde4-amarok.desktop[8715]:

[Bug 1465933] Re: gwenview error: URL not found on startup

2015-06-16 Thread monochromec
Other people have confirmed this too for this particular version: https://bugs.kde.org/show_bug.cgi?format=multipleid=343997. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to gwenview in Ubuntu. https://bugs.launchpad.net/bugs/1465933 Title:

[Bug 1465933] Re: gwenview error: URL not found on startup

2015-06-16 Thread monochromec
Running kbuildsycoca5 to recreate the KService desktop file system configuration cache fixes the problem. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to gwenview in Ubuntu. https://bugs.launchpad.net/bugs/1465933 Title: gwenview error:

[Bug 1004932] Re: kdm.conf file not removed after dpkg-reconfigure

2012-11-04 Thread monochromec
Upstart jobs start depending on certain signals being emitted by other jobs (cf. http://upstart.ubuntu.com/cookbook/#startup-process for further details). If you have two .conf files both depending on the EXACT same set of signals (as both lightdm.conf AND kdm.conf do) starting different display

[Bug 1004932] [NEW] kdm.conf file not removed after dpkg-reconfigure

2012-05-26 Thread monochromec
Public bug reported: The upstart file for kdm is not removed from /etc/init when choosing lightdm over kdm as the default DM. When installing kdm after lightdm and then selecting kdm as a default DM and subsequently changing this back to lightdm by dpkg-reconfigure lightdm, the upstart stanza for

[Bug 1004932] Re: kdm.conf file not removed after dpkg-reconfigure

2012-05-26 Thread monochromec
-- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/1004932 Title: kdm.conf file not removed after dpkg-reconfigure To manage notifications about this bug go to: