[Bug 179631] Re: {kubuntu} bashism in /usr/bin/startkde

2008-07-12 Thread Edward Shornock
** Changed in: kdebase (Ubuntu) Status: Incomplete => New -- {kubuntu} bashism in /usr/bin/startkde https://bugs.launchpad.net/bugs/179631 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@li

[Bug 179631] Re: {kubuntu} bashism in /usr/bin/startkde

2008-07-11 Thread Edward Shornock
...that's great...it *IS* in the version in hardy so there's no way this is invalid! I just downloaded the package and checked it. :/tmp$ wget http://ubuntu.uni-klu.ac.at/ubuntu/pool/main/k/kdebase/ksmserver_3.5.9-0ubuntu7.2_amd64.deb --2008-07-11 18:20:37-- http://ubuntu.uni-klu.ac.at/ubunt

[Bug 179631] {kubuntu} bashism in /usr/bin/startkde

2007-12-31 Thread Edward Shornock
Public bug reported: Binary package hint: ksmserver In ~/.xsession-errors one can see [: 41: ==: unexpected operator It turns out that it's a bashism in /usr/bin/startkde that causes it. --- kubuntu_17_check_for_prelinking.diff2007-12-31 20:44:54.0 -0500 +++ kubuntu_17_check_

[Bug 144589] Re: [gutsy] kicker does not start at login

2007-12-31 Thread Edward Shornock
I can reproduce it fairly easily. Steps: 1) load kcmshell kcm_tweak 2) Pick any "tweaks" but don't look at the Panel tab 2) hit apply then OK Result: The next time you log in `kicker` won't run. The Panel tab defaults to "Start Panel with KDE" unchecked which creates the file ~/.kde/share/auto

[Bug 89832] Re: An unhandled exception was thrown: Unable to open the session message bus.

2007-12-23 Thread Edward Shornock
Missing dependency on dbus-x11 ** Changed in: f-spot (Ubuntu) Status: Invalid => Incomplete -- An unhandled exception was thrown: Unable to open the session message bus. https://bugs.launchpad.net/bugs/89832 You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 89832] Re: An unhandled exception was thrown: Unable to open the session message bus.

2007-12-23 Thread Edward Shornock
I had the same problem. Install dbus-x11 to resolve it. I think that there should probably be a dependency on dbus-x11 by f-spot. The problem is that without dbus-x11 installed the DBUS_SESSION_BUS_ADDRESS variable is empty. With the empty variable, f-spot doesn't know how to find the session bus