[Desktop-packages] [Bug 1110613] [NEW] Display calibration profile is deactivated after screensaver kicks in

2013-01-30 Thread Andreas Siegert
Public bug reported: I am running a Lenovo T520 with an Nvidia proprietary driver 310.19 in dualscreen mode using 12.04 64bit. I have display profiles loaded for both screens. The profile of the primary screen is disabled (but still loaded) after xscreensaver has blanked the screen. I need to r

[Desktop-packages] [Bug 1316574] [NEW] xscreensave unloads ICC profile

2014-05-06 Thread Andreas Siegert
Public bug reported: I had to switch my 64bit Xubuntu 14.04 system to xscreensaver due to a suspend/resume issue with the default light-locker. In contrast to light-locker, my display profile is no longer loaded after a lock/unlock cycle wth xscreensaver (I have xscreensaver set to blank, just l

[Desktop-packages] [Bug 1317043] [NEW] Libreoffice screen rendering is broken

2014-05-07 Thread Andreas Siegert
Public bug reported: Using Libreoffice 4.2.3 from the Xbuntu repositories on 14.04 64bit. Nvidia proprietary driver 331.67 When resizing a writer window, the rendering in the window is competently broken, showing artifacts from window borders but not the text. Further resize attempts do not ch

[Desktop-packages] [Bug 1317043] Re: Libreoffice screen rendering is broken

2014-05-07 Thread Andreas Siegert
LO 4.3.3 from the Libreoffice web site does not show this problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1317043 Title: Libreoffice screen rendering is broken Status in

[Desktop-packages] [Bug 1319805] [NEW] DNS confused with multiple interfaces (eth/wlan)

2014-05-15 Thread Andreas Siegert
Public bug reported: Using a laptop with a hardware switch for enable/disable WLAN. Connected to two different LANs using DHCP on ETH/WLAN. When both interfaces are active (in different networks), the system uses the LAN interface as the default route as expected. But it does not use the the nam

[Desktop-packages] [Bug 1325833] Re: GCR has no man page and employs insecure defauts for GPG passphrase caching

2014-07-10 Thread Andreas Siegert
So why does this get importance undecided? This silly thing has a direct security impact. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1325833 Title: GCR has no man page and employs ins

[Desktop-packages] [Bug 1325833] Re: GCR has no man page and employs insecure defauts for GPG passphrase caching

2014-07-10 Thread Andreas Siegert
And then the next update also overwrites my user settings. Of course this is all undocumented and I have start hunting again for how to fix the idiotic cache permanently setting. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gcr in Ubun

[Desktop-packages] [Bug 1325833] Re: GCR has no man page and employs insecure defauts for GPG passphrase caching

2014-07-10 Thread Andreas Siegert
When I see a gcr password prompter asking for my password, then for me it looks like gcr is the thing responsible. See also https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1325832 This is how I stumbled into the issue. -- You received this bug notification because you are a member of Des

[Desktop-packages] [Bug 1325833] Re: GCR has no man page and employs insecure defauts for GPG passphrase caching

2014-07-10 Thread Andreas Siegert
gpg-agent is not involved at all. It is not running. I never asked for this. I stumble across the gcr password prompter and a messed up passphrase handling in Thunderbird/enigmail that use gcr under the hood (see referenced bug) without the user ever being asked about this. When I try to find out

[Desktop-packages] [Bug 1325833] Re: gnome-keyring has an inadequate man page and employs insecure defaults for GPG passphrase caching

2014-07-10 Thread Andreas Siegert
I have configured Enigmail to not use gpg-agent. It is not running at all... But this is an issue for the other bug... Gnome bug: https://bugzilla.gnome.org/show_bug.cgi?id=733032 ** Bug watch added: GNOME Bug Tracker #733032 https://bugzilla.gnome.org/show_bug.cgi?id=733032 -- You received