[Bug 1408229] [NEW] cpufrequtils init script overridden by ondemand script

2015-01-07 Thread Bruce Merry
Public bug reported: The cpufrequtils installs an init script, /etc/init.d/cpufrequtils, that sets the governors at bootup. I changed the default in /etc/default/cpufrequtils, but the script is ineffective because /etc/init.d/ondemand forces the governors to ondemand anyway. What's more, the

[Bug 1303736] Re: Black screen after wakeup from suspending by closing the laptop lid

2014-05-23 Thread Bruce Merry
New package (comment #91) works for me, as did the previous version (#56). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303736 Title: Black screen after wakeup from suspending by closing the

[Bug 1303736] Re: Black screen after login from suspend in Xubuntu 14.04

2014-05-13 Thread Bruce Merry
I can confirm the fix in post 56 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1303736 Title: Black screen after login from suspend in Xubuntu 14.04 To manage notifications about this bug go

[Bug 1303736] Re: Black screen after login from suspend in Xubuntu 14.04

2014-05-06 Thread Bruce Merry
I have uploaded a slightly modified version of xfce4-power-manager to https://launchpad.net/~thad-fisch/+archive/xfce4-power-manager for testing purpose. The screen will be now locked on wake up (as opposed to while suspending the system). Installing the PPA did not change my symptoms at all

[Bug 1307114] [NEW] Blank screen after resume if lid closed

2014-04-13 Thread Bruce Merry
Public bug reported: I have a Lenovo G570 laptop (Intel Sandy Bridge graphics). If I suspend via the user interface, then resume by pressing the power button, everything works. However, when closing the lid to suspend, I observe the following sequence: 1. Close lid, wait a few seconds for

[Bug 1255573] Re: libstdc++ debug script sets wrong PYTHONPATH

2014-03-17 Thread Bruce Merry
Also affects Trusty Tahr beta (libstdc++6-4.8-dbg 4.8.2-16ubuntu6). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1255573 Title: libstdc++ debug script sets wrong PYTHONPATH To manage

[Bug 1291017] [NEW] light-locker blanking settings not taking effect

2014-03-11 Thread Bruce Merry
Public bug reported: I've used light-locker settings to set a blank time of 4 minutes and a display suspend time of 6 minutes. However, when I power up the machine and log in, these settings are not in effect, and 'xset q' reports the following (unrelated output cut): Screen Saver: prefer

[Bug 1291019] [NEW] xflock4 still uses xscreensaver by default

2014-03-11 Thread Bruce Merry
Public bug reported: According to http://xubuntu.org/news/xubuntu-14-04-beta-1/, light-locker is supposed to replace xscreensaver for XUbuntu 14.04, but /usr/bin/xflock4 uses xscreensaver in preference to light-locker if both are present. Since xscreensaver is also installed by the default

[Bug 1291017] Re: light-locker blanking settings not taking effect

2014-03-11 Thread Bruce Merry
xscreensaver seems to be partially to blame. After uninstalling it, logging out and logging in, xset q reports Screen Saver: prefer blanking: yesallow exposures: yes timeout: 240cycle: 600 ... DPMS (Energy Star): Standby: 600Suspend: 0Off: 900 DPMS is Enabled Monitor

[Bug 1255573] [NEW] libstdc++ debug script sets wrong PYTHONPATH

2013-11-27 Thread Bruce Merry
Public bug reported: libstdc++6-4.8-dbg on installs /usr/lib/debug/usr/lib/x86_64-linux- gnu/libstdc++.so.6.0.18-gdb.py. This is supposed to autoload the pretty- printers for libstdc++ into gdb when a program is started. However, its logic for determining the path to set seems to be broken,

[Bug 1251262] [NEW] Qt5 windows may be randomly unmapped due to assumption sizeof(long)==4

2013-11-14 Thread Bruce Merry
Public bug reported: The patch debian/patches/0001-Implement-XEmbed-protocol.patch adds XEmbed protocol support, but it has some undefined behaviour bugs on LP64 systems like x86-64. In particular, the _XEMBED_INFO property is defined as two CARD32 values (http://standards.freedesktop.org/xembed-

[Bug 400259] Re: Bogus SystemID in XHTML catalog makes org.apache.xml.resolver fail

2013-10-28 Thread Bruce Merry
This bug also affects 13.10, and is causing the maven-xml-plugin to fail (which wasn't the cause in 12.04). I've attached a patch against the source tree for version 1.2-4. ** Patch added: Patch again w3c-dtd-xhtml_1.2-4 for Ubuntu 13.10

[Bug 400259] Re: Bogus SystemID in XHTML catalog makes org.apache.xml.resolver fail

2013-10-13 Thread Bruce Merry
This still affects Ubuntu 12.04.3. I've attached a patch against w3c- dtd-xhtml_1.1-5ubuntu1.diff, which should make this easier to fix. And I agree with comment #2 - regardless of which package is at fault, resolution is failing, so it is a bug in the Ubuntu system. ** Patch added: Patch to the