[Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
** Also affects: hplip (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793675 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
I suggest that the hplip maintainers update the file hplip/hplip-systray.desktop.in by adding this line at the end: NotShowIn=GNOME; I think doing this will close: - https://bugs.launchpad.net/hplip/+bug/1714659 (this bug) - https://bugs.launchpad.net/hplip/+bug/1721534 - https://bugs.launchpad.net/hplip/+bug/1770027 - and a lot of other downstream bugs like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793675 ** Bug watch added: Debian Bug tracker #793675 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793675 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714659] Re: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.)
The hp-systray command is commonly started as part of the session's autostart; for example, in Debian. When it doesn't find a system tray on the current environment, it displays an error dialog box. This is the case of GNOME which has dropped support for the system tray functionality in favour of a unified "notifications" functionality, pushing developers to quit relying on a system tray. This comes from hplip/ui4/systemtray.py where QSystemTrayIcon.isSystemTrayAvailable() returns False when run under GNOME. Solutions I see: - Change the /etc/xdg/autostart/hplip-systray.desktop and add a property (NotShowIn, see https://specifications.freedesktop.org/menu-spec/latest/ar01s03.html) to not start in GNOME. It simply means adding this line: NotShowIn=GNOME; - Change the hplip code to fail silently if it detects that there is no system tray. This might hide real issues however. - Add a new dedicated binary package for hplip-gui-systray, and do not install it by default, especially for GNOME users. - Understand the functionality of hp-systray and implement an alternative using GNOME's notifications; choose it when running in GNOME. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714659 Title: HPLIP is not compatible with modern GNOME (No system tray detected on this system. Unable to start, exiting.) To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1714659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1287127] Re: Linux-image 3.11.0-17-generic can't boot
Same problem here, 3.11.0-17-generic, 3.11.0-18-generic doesn't work for me, only the 3.11.0-15-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1287127 Title: Linux-image 3.11.0-17-generic can't boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-saucy/+bug/1287127/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 366728] Re: LD_LIBRARY_PATH not loading from .profile nor /etc/environment
*** This bug is a duplicate of bug 47958 *** https://bugs.launchpad.net/bugs/47958 The cleanest workaround would be the comment #17 above (except maybe naming the file 89preserve_ld_library_path instead of 90preserve...). The fix would be to add that code into the 90x11-common_ssh-agent script with an explanatory comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/366728 Title: LD_LIBRARY_PATH not loading from .profile nor /etc/environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/366728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 878612] Re: Linker fails when compiling fuse files with "undefined reference to `fuse_main_real'
LDFLAGS is the variable for the linker flags. Linker libs such as -lfuse should be put in the LDLIBS variable, not in LDFLAGS. To solve the problem and simplify the Makefile at the same time: In the Makefile, the LDFLAGS definition should be replaced with LDLIBS: LDLIBS := $(shell pkg-config fuse --libs) Also the 2-line fusexmp_fh section should be simplified with: fusexml_fh: LDLIBS += -lulockmgr (To make it even cleaner, there should be separate CFLAGS and CPPFLAGS pkg-config settings: --cflags-only-other and --cflags-only-I respectively) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/878612 Title: Linker fails when compiling fuse files with "undefined reference to `fuse_main_real' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/878612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1155327] Re: skype crashed with SIGSEGV in malloc@plt()
ld.so: object '/usr/lib/i386-linux-gnu/mesa/libGL.so.1' from LD_PRELOAD cannot be preloaded: ignored. Falha de segmentação (imagem do núcleo gravada) :( -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qtwebkit-source in Ubuntu. https://bugs.launchpad.net/bugs/1155327 Title: skype crashed with SIGSEGV in malloc@plt() To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1155327/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 945798] Re: colord crashed with SIGABRT in g_assertion_message()
Up -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/945798 Title: colord crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/945798/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 356261] Re: Bitlbee does not start at boot time
Karmic doesn't have this problem On Sat, Dec 26, 2009 at 11:47 PM, Kenyon Ralph wrote: > Is this still a problem? I'm pretty sure BitlBee started at boot last > time I booted my Ubuntu karmic server, which was 45 days ago, with > BitlBee 1.2.4-1. > > -- > Bitlbee does not start at boot time > https://bugs.launchpad.net/bugs/356261 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “bitlbee” package in Ubuntu: Confirmed > > Bug description: > Binary package hint: bitlbee > > Upon upgrading to Jaunty, bitlbee no longer starts up at boot time. > Instead, I have to manually issue a /etc/init.d/bitlbee restart once network > is up to get it started. > > ProblemType: Bug > Architecture: i386 > DistroRelease: Ubuntu 9.04 > Package: bitlbee 1.2.3-1 > ProcEnviron: > PATH=(custom, user) > LANG=en_US.UTF-8 > SHELL=/bin/bash > SourcePackage: bitlbee > Uname: Linux 2.6.28-11-generic i686 > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/ubuntu/+source/bitlbee/+bug/356261/+subscribe > -- Bitlbee does not start at boot time https://bugs.launchpad.net/bugs/356261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 356261] Re: Bitlbee does not start at boot time
Confirmed on Jaunty 64 bit as well -- Bitlbee does not start at boot time https://bugs.launchpad.net/bugs/356261 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
