[Bug 1396048] Re: Evince misses font and only displays squares in menus
For me it seems to happen with symlinks from /usr/share/fonts to a different partition -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1396048 Title: Evince misses font and only displays squares in menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1396048/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631088] Re: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable
Still not working in 14.04. Strangely, using strace -eopen evince I can see that an open() system call returns EACCES, even though from the shell I can access the symlink (and its target) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/631088 Title: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/631088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 631088] Re: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable
Aha, it's Teh Apparmor. Edit /etc/apparmor.d/usr.bin.evince and add /**.[tT][tT][fF] rw, after the other supported formats (bmp, djvu etc) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/631088 Title: Incompatibilty with Windows font Deja Vu Sans 9.9990234375 makes evince menu unreadable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/631088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 17962] Re: newly opened gnome-terminal windows don't have .bash_profile sourced
That was absolute bull. Ubuntu obviously ships with /etc/profile, which is a version of bash_profile, so #8 was a specious argument. And placing profiley stuff into bashrc slows down the shell (as if it's not slow enough already!) Some .xsessionrc file (or whatever is read by the *dm's) must make sure to read /etc/profile. If that is not done at the system level it must be recommended to users as the preferred workaround for this utter nonsense. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/17962 Title: newly opened gnome-terminal windows don't have .bash_profile sourced To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/17962/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 515915] Re: evince hangs on start-up
The only way I can get out of this bug, when it bites, is to exit my X (and presumably dbus) session and log back in. Really annoying. evince prints all sorts of useless console clutter, but fails to print any useful diagnostics in this case. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/515915 Title: evince hangs on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/515915/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726480] Re: gnome-screensaver forces itself upon xscreensaver users
As per my above comment, the original issue was not addressed ** Package changed: lxde-common (Ubuntu) = gnome-screensaver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/726480 Title: gnome-screensaver forces itself upon xscreensaver users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726480] [NEW] gnome-screensaver forces itself upon xscreensaver users
Public bug reported: Binary package hint: gnome-screensaver gnome-screensaver installs the DBus file /usr/share/dbus-1/services/org.gnome.ScreenSaver.service which unconditionally starts gnome-screensaver whenever some other process (e.g. nm-applet, update-notifier) pull the trigger. This is troubling for users of non-gnome desktop environments, e.g. LXDE. A workaround for me was to install the following /usr/local/share/dbus-1/services/org.gnome.ScreenSaver.service: [D-BUS Service] Name=org.gnome.ScreenSaver Exec=/bin/sh -c 'if xscreensaver-command -version /dev/null 21; then renice +10 $$ /dev/null 21; while sleep 60; do :; done else exec /usr/bin/gnome-screensaver; fi' gnome-screensaver-placeholder The dummy process remains active because if it exited immediately, dbus might try to restart gnome-screensaver. I don't know if this is really necessary. First of all, this needs to be fixed -- screensavers should not step on each others' toes. Secondly, is there a more elegant workaround? Note that because of bug #726471, a user can't override a misguided /usr/share/ service file in his home (~/.local/share) configuration: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/726471 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gnome-screensaver 2.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.31-11.154-rt Uname: Linux 2.6.31-11-rt i686 Architecture: i386 Date: Mon Feb 28 12:44:49 2011 GnomeSessionIdleInhibited: Unknown GnomeSessionInhibitors: Failed to acquire InstallationMedia: Xubuntu 10.04 Lucid Lynx - Release i386 (20100429) ProcEnviron: LC_COLLATE=C PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: gnome-screensaver WindowManager: gnome-wm ** Affects: gnome-screensaver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/726480 Title: gnome-screensaver forces itself upon xscreensaver users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726480] Re: gnome-screensaver forces itself upon xscreensaver users
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/726480 Title: gnome-screensaver forces itself upon xscreensaver users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 726480] Re: gnome-screensaver forces itself upon xscreensaver users
My remark about processes that pull the trigger was based on an empirical observation: if I start LXDE with a disabled /etc/xdg/autostart/update-notifier.desktop, xscreensaver runs, and there is no gnome screensaver. Whenever one of nm-applet or update-notifier starts, dbus loads gnome-screensaver. What these two applets seem to have in common is that they both pop up small banner-like notices. I can't find any actual code in update- notifier that tickles the screensaver. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in ubuntu. https://bugs.launchpad.net/bugs/726480 Title: gnome-screensaver forces itself upon xscreensaver users -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 665195] Re: plymouthd alive when umountroot runs (prevents clean unmount)
I'm getting the feeling that the mechanism used to keep plymouth up / down appropriately AND avoid a VT change all the while is brittle; there are too many unpredictable interactions between plymouth, plymouth-stop, [gkx]dm and rc*.d stop. That's why I filed against plymouth in the first place -- perhaps there could be a simpler design... -- plymouthd alive when umountroot runs (prevents clean unmount) https://bugs.launchpad.net/bugs/665195 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
