[Desktop-packages] [Bug 2061977] [NEW] t64 migration: libgtk-3-0t64 has unmet dependencies, blocks >200 packages
Public bug reported: lsb_release -rd No LSB modules are available. Description:Ubuntu Noble Numbat (development branch) Release:24.04 This unresolved dependency seems to be the main t64 migration blocker for the last weeks. I've manually thinned out the dependencies that "apt upgrade" can't solve but the libgtk-3-0t64/libreoffice-core unresolvable dependencies remain as main blocker. This has not changes for at least 2 weeks now. root@kyle:/# apt install vim-tiny Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libgtk-3-0t64 : Depends: libcups2 (>= 2.3~b6) Recommends: libgtk-3-bin libreoffice-core : Depends: libcups2t64 (>= 1.7.0) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. root@kyle:/# There are no held packages. root@kyle:/# apt update; apt upgrade Hit:1 http://dl.google.com/linux/earth/deb stable InRelease Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease Hit:3 http://apt.postgresql.org/pub/repos/apt jammy-pgdg InRelease Hit:4 https://download.tinkerforge.com/apt/ubuntu noble InRelease Hit:5 https://repo.steampowered.com/steam stable InRelease Hit:6 https://updates.signal.org/desktop/apt xenial InRelease Hit:7 https://updates.signal.org/desktop/apt artful InRelease Hit:8 https://mkvtoolnix.download/ubuntu mantic InRelease Hit:9 http://ppa.launchpad.net/yubico/stable/ubuntu kinetic InRelease Hit:10 http://security.ubuntu.com/ubuntu noble-security InRelease Hit:11 https://ppa.launchpadcontent.net/ubuntuhandbook1/handbrake/ubuntu mantic InRelease Hit:12 https://dl.google.com/linux/chrome/deb stable InRelease Hit:13 https://packages.microsoft.com/repos/ms-teams stable InRelease Hit:14 https://ppa.launchpadcontent.net/yubico/stable/ubuntu noble InRelease Hit:15 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/jammy pgadmin4 InRelease Hit:16 http://apt.postgresql.org/pub/repos/apt mantic-pgdg InRelease Hit:17 https://ftp.postgresql.org/pub/pgadmin/pgadmin4/apt/mantic pgadmin4 InRelease Hit:18 http://ppa.launchpad.net/yubico/stable/ubuntu mantic InRelease Hit:19 http://apt.postgresql.org/pub/repos/apt noble-pgdg InRelease Hit:20 http://ppa.launchpad.net/yubico/stable/ubuntu noble InRelease Hit:21 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:22 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:23 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:24 http://archive.ubuntu.com/ubuntu noble InRelease Hit:25 http://archive.ubuntu.com/ubuntu noble-updates InRelease Hit:26 http://archive.ubuntu.com/ubuntu noble-backports InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done 210 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: alsa-utils atril coreutils evince gimp gir1.2-gst-plugins-base-1.0 gir1.2-javascriptcoregtk-4.1 gir1.2-webkit2-4.1 gstreamer1.0-gl gstreamer1.0-gtk3 gstreamer1.0-libav gstreamer1.0-plugins-bad gstreamer1.0-plugins-base gstreamer1.0-plugins-good gstreamer1.0-plugins-ugly gstreamer1.0-pulseaudio gstreamer1.0-vaapi gstreamer1.0-x hexchat hexchat-common hexchat-plugins hexchat-python3 hplip hplip-data hplip-gui imagemagick-6.q16 libatk-wrapper-java-jni libblockdev-nvme3 libfcgi-perl libfido2-1 libfluidsynth3 libglusterfs0 libgssapi-krb5-2 libgssapi-krb5-2:i386 libgstreamer-gl1.0-0 libgstreamer-plugins-bad1.0-0 libgstreamer-plugins-base1.0-0 libgstreamer-plugins-good1.0-0 libhpmud0 libimage-magick-q16-perl
[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap
@Sebastien: Your new push fixed the issue. After the new snap was installed, I started Thunderbird and it immediately imported the original profile and started to download the emails from all IMAP accounts. The locally cached mail folders didn't get copied. So far things seem to be working but I didn't have time yet for closer test beyond deleting a few emails. What was notable was to see that thunderbird spit out a number of errors on vcf cards while downloading the emails. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: Fix Released Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap
@Heinrich: Exactly ONE. The snapped profile manager doesn't see the profile in the proper place ~/.thunderbird Snap is causing nothing but trouble. DEB had been working fine since its inception. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: In Progress Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2056668] Re: Thunderbird Snap migration loses user profile
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
@Patrik Lunquist Unfortunately this solution doesn't work for me.
As already shown in my previous post.
In the screenshot attached there you can see the "messenger window"
that opens up when starting thunderbird after moving the .thunderbird
directory.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:15:38.811: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0
unprotected)"
console.error: ({})
JavaScript error: chrome://messenger/content/aboutMessage.js, line 119:
NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener]
console.error: (new TypeError("NetworkError: Network request failed",
Re: [Desktop-packages] [Bug 2056434] Re: Thunderbird profile not migrated to snap
On 3/11/24 17:13, Patrik Lundquist wrote: > Close Thunderbird. > > Remove the new, empty profile. > rm -r ~/snap/thunderbird/common/.thunderbird > > > mv ~/.thunderbird ~/snap/thunderbird/common/ > That was my very first test. Unfortunately it does NOT work for me as described before and shown in the screenshot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2056434 Title: Thunderbird profile not migrated to snap Status in thunderbird package in Ubuntu: Confirmed Bug description: Today's update installed the thunderbird snap and removed the thunderbird binary but it did not migrate my thunderbird profile. Now I don't have access to any old mails anymore. Looking at ~/.thunderbird: $ cat profiles.ini [Profile1] Name=default IsRelative=1 Path=ao6t0qef.default Default=1 [InstallFDC34C9F024745EB] Default=ji04wv64.default-release Locked=1 [Profile0] Name=default-release IsRelative=1 Path=ji04wv64.default-release [General] StartWithLastProfile=1 Version=2 ji04wv64.default-release is the folder that should have been migrated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2056434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2056668] Re: Thunderbird Snap migration loses user profile
*** This bug is a duplicate of bug 2056434 ***
https://bugs.launchpad.net/bugs/2056434
On 3/11/24 10:30, Skia wrote:
> Here is how I worked around this:
> * close thunderbird, make sure it's not running in the background
> * `rsync -raxPHAX ~/.thunderbird/ ~/snap/thunderbird/common/.thunderbird/`
> * edit `~/snap/thunderbird/common/.thunderbird/profiles.ini` to make sure the
> only profile listed here is the one with the data (the biggest folder in
> `~/snap/thunderbird/common/.thunderbird/`)
> * run thunderbird
>
> So far, everything seems to be in order, including contacts, calendars
> on multiple accounts, sieve filter and message redirect plugins.
>
Unfortunately this has not worked for me.
Before I had also tried moving the whole ~/.thunderbird folder to
~/snap/thunderbird/common/ (which does essentially the same thing as
your rsync)
I just get the error message that you can see in the attached
screenshot.
When I move back the empty profile I get what you'd expect: An empty
profile with no settings etc.
** Attachment added: "Thunderbird_SNAP_FUBAR_2024-03-11_13-16-23.png"
https://bugs.launchpad.net/bugs/2056668/+attachment/5754808/+files/Thunderbird_SNAP_FUBAR_2024-03-11_13-16-23.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description: Ubuntu Noble Numbat (development branch)
Release: 24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
[Desktop-packages] [Bug 2056668] [NEW] Thunderbird Snap migration loses user profile
Public bug reported:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the migration from normal deb to snap all and any settings, addons,
accounts, etc got lost.
This is a big no-no.
Architecture: amd64
Version: 1:115.8.1+build1+snap2
No LSB modules are available.
Description:Ubuntu Noble Numbat (development branch)
Release:24.04
root@kyle:/opt/DATA/media/incoming/tmp# apt-cache policy thunderbird
thunderbird:
Installed: 1:115.8.1+build1+snap2
Candidate: 1:115.8.1+build1+snap2
Version table:
*** 1:115.8.1+build1+snap2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
100 /var/lib/dpkg/status
1:115.8.1+build1-0ubuntu0.23.10.1 500
500 http://archive.ubuntu.com/ubuntu mantic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
1:115.3.1+build1-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
neuffer@kyle:~$ ls -la ~/.thunderbird/
total 28
drwx-- 5 neuffer neuffer 4096 Okt 7 2019 .
drwxr-x--- 26 neuffer neuffer 4096 Mär 10 11:09 ..
drwx-- 17 neuffer neuffer 4096 Mär 5 17:50 8ru3o2xn.default
drwx-- 4 neuffer neuffer 4096 Mär 5 15:58 'Crash Reports'
-rw-rw-r-- 1 neuffer neuffer 45 Okt 7 2019 installs.ini
drwx-- 2 neuffer neuffer 4096 Apr 2 2019 'Pending Pings'
-rw-rw-r-- 1 neuffer neuffer 166 Okt 7 2019 profiles.ini
neuffer@kyle:~$
neuffer@kyle:~$ thunderbird --ProfileManager
_IceTransSocketINETConnect() no usable address for kyle:44955
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:14:30.844: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
JavaScript error: resource://gre/modules/XULStore.sys.mjs, line 60: Error:
Can't find profile directory.
console.error: (new UnknownError("IndexedDB:
thunderbird/url-classifier-skip-urls getLastModified() IndexedDB: The
operation failed for reasons unrelated to the database itself and not covered
by any other error code.", "resource://services-settings/IDBHelpers.jsm", 18))
_IceTransSocketINETConnect() no usable address for kyle:44955
[ImapModuleLoader] Using nsImapService.cpp
[Parent 27516, Main Thread] WARNING: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory: 'glib
warning', file
/build/thunderbird/parts/thunderbird/build/toolkit/xre/nsSigHandlers.cpp:167
(thunderbird:27516): IBUS-WARNING **: 11:15:38.811: Failed to mkdir
/home/neuffer/snap/thunderbird/450/.config/ibus/bus: Not a directory
[GFX1-]: glxtest: libpci missing
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0
unprotected)"
console.error: ({})
JavaScript error: chrome://messenger/content/aboutMessage.js, line 119:
NS_ERROR_ILLEGAL_VALUE: Component returned failure code: 0x80070057
(NS_ERROR_ILLEGAL_VALUE) [nsIWebProgress.addProgressListener]
console.error: (new TypeError("NetworkError: Network request failed",
"resource://services-settings/Utils.sys.mjs", 229))
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: grave release-critical
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2056668
Title:
Thunderbird Snap migration loses user profile
Status in thunderbird package in Ubuntu:
New
Bug description:
TL;DR: Snap implementation is FUBAR, how do I get back to a non-SNAP
version?
I consider this bug to be Grave since it not only affects thunderbid,
but also a huge number of depending other services, bug-reporting
amongst it.
Thunderbird Snap migration loses user profile
With the
[Desktop-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
With BIOS A25 and eoan it is still not fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
On 01.12.2014 11:57, Christopher M. Penalver wrote: Michael Neuffer, could you please boot into the kernel that comes with Ubuntu by default (i.e. not 3.11.x) What do you mean with that comes with Ubuntu by default ? I currently use 3.16.0-26-generic and execute the following in a terminal as it will automatically gather and attach updated debug information to this report: apport-collect -p xorg 1268151 Please ensure you have xdiagnose installed, That is currently not possible: --- root@charion:~# apt-get install xdiagnose Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: xdiagnose : Depends: python3-pygtk but it is not installable Recommends: intel-gpu-tools but it is not going to be installed E: Unable to correct problems, you have held broken packages. Once the dependcy can be fullfilled I can install it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in xorg package in Ubuntu: Incomplete Bug description: With my Dell Precision M4800, GK106GLM [Quadro K2100M], QHD+ display, and either nvidia-graphics-drivers-331 or nvidia-graphics-drivers-319 once the display shuts off, it will not wake up anymore, and the screen stays dark. A cycle of the following will leave the display dark: xset dpms force off; sleep 30; xset dpms force on WORKAROUND: A restart of the Xserver will bring back the display. WORKAROUND: Don't allow DPMS to switch off the display: xset dpms 0 0 0 xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] Re: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep
I can confirm that, as of today the latest BIOS for the Dell Precision M4800 is A09. The problem still exists with this BIOS version. BIOS version A10 was made available only for a very short period and then replaced again with A09, since it tended to brick the machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: [Dell M4800] DPMS support broken, fails to wake up the monitor after putting it to sleep Status in The Dell Project: Incomplete Status in HWE Next Project: Incomplete Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in OEM Priority Project: Incomplete Status in “nvidia-graphics-drivers-331” package in Ubuntu: Incomplete Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Incomplete Status in “xserver-xorg-video-nouveau” package in Ubuntu: Incomplete Bug description: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394639] [NEW] lightdm fails to start with 3 connected displays but works 2 displays
Public bug reported: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
** Attachment added: X Server log with 3 displays connected https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+attachment/4264462/+files/Xorg.0.log.borked -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
lightdm log with 3 displays attached [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.13.0, UID=0 PID=4640 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registered seat module xlocal [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Monitoring logind for seats [+0.00s] DEBUG: New seat added from logind: seat0 [+0.00s] DEBUG: Loading properties from config section SeatDefaults [+0.00s] DEBUG: Seat seat0: Starting [+0.00s] DEBUG: Seat seat0: Creating greeter session [+0.00s] DEBUG: Seat seat0: Creating display server of type x [+0.00s] DEBUG: Using VT 7 [+0.00s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.00s] DEBUG: DisplayServer x-0: Logging to /var/log/lightdm/x-0.log [+0.00s] DEBUG: DisplayServer x-0: Writing X server authority to /var/run/lightdm/root/:0 [+0.00s] DEBUG: DisplayServer x-0: Launching X Server [+0.00s] DEBUG: Launching process 4650: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.00s] DEBUG: DisplayServer x-0: Waiting for ready signal from X server :0 [+0.00s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.00s] DEBUG: Loading users from org.freedesktop.Accounts [+0.00s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+2.09s] DEBUG: Got signal 10 from process 4650 [+2.09s] DEBUG: DisplayServer x-0: Got signal from X server :0 [+2.09s] DEBUG: DisplayServer x-0: Connecting to XServer :0 [+2.09s] DEBUG: Seat seat0: Display server ready, starting session authentication [+2.09s] DEBUG: Session pid=4694: Started with service 'lightdm-greeter', username 'lightdm' [+2.10s] DEBUG: Session pid=4694: Authentication complete with return value 0: Success [+2.10s] DEBUG: Seat seat0: Session authenticated, running command [+2.10s] DEBUG: Session pid=4694: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/lightdm-gtk-greeter [+2.10s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+2.10s] DEBUG: Session pid=4694: Logging to /var/log/lightdm/x-0-greeter.log [+2.11s] DEBUG: Activating VT 7 [+2.11s] DEBUG: Activating login1 session c3 [+2.14s] DEBUG: Session pid=4694: Greeter connected version=1.13.0 resettable=false [+2.40s] DEBUG: Session pid=4694: Greeter closed communication channel [+2.40s] DEBUG: Session pid=4694: Exited with return value 0 [+2.40s] DEBUG: Seat seat0: Session stopped [+2.40s] DEBUG: Seat seat0: Stopping; failed to start a greeter [+2.40s] DEBUG: Seat seat0: Stopping [+2.40s] DEBUG: Seat seat0: Stopping display server [+2.40s] DEBUG: Sending signal 15 to process 4650 [+3.61s] DEBUG: Process 4650 exited with return value 0 [+3.61s] DEBUG: DisplayServer x-0: X server stopped [+3.61s] DEBUG: Releasing VT 7 [+3.61s] DEBUG: DisplayServer x-0: Removing X server authority /var/run/lightdm/root/:0 [+3.61s] DEBUG: Seat seat0: Display server stopped [+3.61s] DEBUG: Seat seat0: Stopped [+3.61s] DEBUG: Required seat has stopped [+3.61s] DEBUG: Stopping display manager [+3.61s] DEBUG: Display manager stopped [+3.61s] DEBUG: Stopping daemon [+3.61s] DEBUG: Exiting with return value 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0
Re: [Desktop-packages] [Bug 1394639] Re: lightdm fails to start with 3 connected displays but works 2 displays
On 20.11.2014 20:55, Andrew P. wrote: Since you are using gtk-greeter - can you test version from this PPA? https://code.launchpad.net/~kalgasnik/+archive/ubuntu/lightdm-gtk-greeter-background-transition Yes, the new version works fine! No more fiddling with monitor cables. Please do not wait to long before uploading it. :-) Thanks! Cheers Mike -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1394639 Title: lightdm fails to start with 3 connected displays but works 2 displays Status in “lightdm” package in Ubuntu: New Bug description: lightdm fails to start with 3 connected displays but works 2 displays. Once lightdm has started and displays the Greeter I can connect the third display without a hitch. After logging in I can enable the third display #!/bin/sh xrandr --output VGA-0 --off --output DP-6 --off --output DP-5 --off --output DP-4 --mode 3200x1800 --pos 0x0 --rotate normal --output DP-3 --scale 1.5x1.5 --mode 1920x1200 --pos 3200x0 --rotate normal --output DP-2 --scale 1.5x1.5 --mode 1920x1080 --pos 6080x0 --rotate normal --output DP-1 --off --output DP-0 --off When lightdm is started with all three displays connected, it will terminate and force the Xserver to go down as well, triggering a cycle of Xserver/lightdm restarts. Disconnecting the 3rd display will bring up lightdm immediately without a glitch. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Nov 20 14:09:40 2014 InstallationDate: Installed on 2014-05-30 (174 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) LightdmGreeterLog: (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed (lightdm-gtk-greeter:7540): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (lightdm-gtk-greeter:7540): WARNING **: Failed to load user image: Failed to open file '/home/neuffer/.face': No such file or directory SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1394639/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1387642] [NEW] lightdm fails to open Pipe - too many open files (with link to patch)
Public bug reported: Please check https://bugs.launchpad.net/lightdm/+bug/1190344 for details and hopefully the fix. The bug report mentioned above is against Fedora and the fix might not have made it into Debian/Ubuntu as it seems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 30 13:47:37 2014 InstallationDate: Installed on 2014-05-30 (153 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1387642 Title: lightdm fails to open Pipe - too many open files (with link to patch) Status in “lightdm” package in Ubuntu: New Bug description: Please check https://bugs.launchpad.net/lightdm/+bug/1190344 for details and hopefully the fix. The bug report mentioned above is against Fedora and the fix might not have made it into Debian/Ubuntu as it seems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Oct 30 13:47:37 2014 InstallationDate: Installed on 2014-05-30 (153 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1387642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363227] [NEW] gpu-manager FUBARs nvidia X server drivers links via update-alternative
Public bug reported: TLDR Version: All current Nvidia drivers get BORKed by ubuntu-drivers-common's gpu-manager After every reboot (restart of gpu-manager) most links which get set via update-alternatives are overwritten Rest: and look for example like this: root@charion:/var/lib/dpkg/info# ls -la /etc/alternatives/i386-linux-gnu_gl_conf /etc/alternatives/x86_64-linux-gnu_gl_conf lrwxrwxrwx 1 root root 39 Aug 29 18:02 /etc/alternatives/i386-linux-gnu_gl_conf - /usr/lib/i386-linux-gnu/mesa/ld.so.conf lrwxrwxrwx 1 root root 41 Aug 29 18:02 /etc/alternatives/x86_64-linux-gnu_gl_conf - /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf This also prevents the Xserver from loading the nvidia_drv.so module [36.765] (II) LoadModule: nvidia [36.765] (WW) Warning, couldn't open module nvidia [36.765] (II) UnloadModule: nvidia [36.765] (II) Unloading nvidia [36.765] (EE) Failed to load module nvidia (module does not exist, 0) [36.765] (II) LoadModule: nouveau [36.765] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [36.765] (II) Module nouveau: vendor=X.Org Foundation [36.765]compiled for 1.15.0, module version = 1.0.10 [36.765]Module class: X.Org Video Driver [36.765]ABI class: X.Org Video Driver, version 15.0 [36.765] (II) LoadModule: modesetting [36.765] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [36.765] (II) Module modesetting: vendor=X.Org Foundation since the link has gone AWOL ls -la /usr/lib/xorg/modules/drivers/ total 4892 drwxr-xr-x 2 root root4096 Aug 29 18:02 . drwxr-xr-x 6 root root4096 Jul 31 11:21 .. -rw-r--r-- 1 root root 10472 Jul 29 13:38 ati_drv.so -rw-r--r-- 1 root root 31704 Mai 11 07:11 cirrus_alpine.so -rw-r--r-- 1 root root 19352 Mai 11 07:11 cirrus_drv.so -rw-r--r-- 1 root root 27832 Mai 11 07:11 cirrus_laguna.so -rw-r--r-- 1 root root 23560 Feb 5 2014 fbdev_drv.so -rw-r--r-- 1 root root 1617744 Jul 29 13:32 intel_drv.so -rw-r--r-- 1 root root 174648 Feb 5 2014 mach64_drv.so -rw-r--r-- 1 root root 140656 Mai 11 07:12 mga_drv.so -rw-r--r-- 1 root root 44496 Jun 26 19:11 modesetting_drv.so -rw-r--r-- 1 root root 66544 Feb 5 2014 neomagic_drv.so -rw-r--r-- 1 root root 207440 Feb 5 2014 nouveau_drv.so -rw-r--r-- 1 root root 356336 Feb 5 2014 openchrome_drv.so -rw-r--r-- 1 root root 172456 Feb 5 2014 qxl_drv.so -rw-r--r-- 1 root root 108712 Feb 5 2014 r128_drv.so -rw-r--r-- 1 root root 434984 Jul 29 13:38 radeon_drv.so -rw-r--r-- 1 root root 57656 Feb 5 2014 s3_drv.so -rw-r--r-- 1 root root 140848 Feb 5 2014 savage_drv.so -rw-r--r-- 1 root root 112192 Feb 5 2014 siliconmotion_drv.so -rw-r--r-- 1 root root 547064 Apr 2 13:01 sis_drv.so -rw-r--r-- 1 root root 77144 Feb 5 2014 sisusb_drv.so -rw-r--r-- 1 root root 189392 Feb 5 2014 spiceqxl_drv.so -rw-r--r-- 1 root root 65936 Feb 5 2014 tdfx_drv.so -rw-r--r-- 1 root root 142224 Feb 5 2014 trident_drv.so -rw-r--r-- 1 root root 27624 Feb 5 2014 vesa_drv.so -rw-r--r-- 1 root root 157720 Apr 10 10:56 vmware_drv.so root@charion:/var/lib/dpkg/info# ./nvidia-331.postinst configure update-alternatives: automatic updates of /etc/alternatives/x86_64-linux-gnu_gl_conf are disabled; leaving it alone update-alternatives: to return to automatic updates use 'update-alternatives --auto x86_64-linux-gnu_gl_conf' update-alternatives: automatic updates of /etc/alternatives/x86_64-linux-gnu_gl_conf are disabled; leaving it alone update-alternatives: to return to automatic updates use 'update-alternatives --auto x86_64-linux-gnu_gl_conf' update-alternatives: automatic updates of /etc/alternatives/i386-linux-gnu_gl_conf are disabled; leaving it alone update-alternatives: to return to automatic updates use 'update-alternatives --auto i386-linux-gnu_gl_conf' update-alternatives: automatic updates of /etc/alternatives/i386-linux-gnu_gl_conf are disabled; leaving it alone update-alternatives: to return to automatic updates use 'update-alternatives --auto i386-linux-gnu_gl_conf' INFO:Enable nvidia-331 the same with -x + update-alternatives --verbose --force --install /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf x86_64-linux-gnu_gl_conf /usr/lib/nvidia-331/ld.so.conf 8604 --slave /usr/share/man/man1/nvidia-xconfig.1.gz x86_64-linux-gnu_man_nvidiaxconfig.gz /usr/share/man/man1/alt-nvidia-331-xconfig.1.gz --slave /usr/share/man/man1/nvidia-smi.1.gz x86_64-linux-gnu_nvidia-smi.1.gz /usr/share/man/man1/alt-nvidia-331-smi.1.gz --slave /usr/share/man/man1/nvidia-cuda-mps-control.1.gz x86_64-linux-gnu_nvidia-cuda-mps-control.1.gz /usr/share/man/man1/alt-nvidia-331-cuda-mps-control.1.gz --slave /usr/share/man/man1/nvidia-persistenced.1.gz x86_64-linux-gnu_man_persistenced.gz /usr/share/man/man1/alt-nvidia-331-persistenced.1.gz --slave /usr/bin/nvidia-smi x86_64-linux-gnu_nvidia_smi /usr/lib/nvidia-331/bin/nvidia-smi --slave /usr/bin/nvidia-xconfig x86_64-linux-gnu_nvidia_xconfig
[Desktop-packages] [Bug 1363227] Re: gpu-manager FUBARs nvidia X server drivers links via update-alternative
Shutting up gpu-manager by commenting out the upstart config prevents further corruption of the links. This is a band aid but at least it lets me continue to work again for the moment /etc/init$ diff -uN gpu-manager.conf~ gpu-manager.conf --- gpu-manager.conf~ 2014-05-28 16:09:45.0 +0200 +++ gpu-manager.conf2014-08-29 21:25:14.581358404 +0200 @@ -1,7 +1,7 @@ -start on (starting lightdm - or starting gdm - or starting kdm - or starting xdm - or starting lxdm) -task -exec gpu-manager --log /var/log/gpu-manager.log +#start on (starting lightdm +# or starting gdm +# or starting kdm +# or starting xdm +# or starting lxdm) +#task +#exec gpu-manager --log /var/log/gpu-manager.log ** Also affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1363227 Title: gpu-manager FUBARs nvidia X server drivers links via update- alternative Status in “nvidia-graphics-drivers-331” package in Ubuntu: New Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Status in “ubuntu-drivers-common” package in Ubuntu: New Bug description: TLDR Version: All current Nvidia drivers get BORKed by ubuntu-drivers-common's gpu-manager After every reboot (restart of gpu-manager) most links which get set via update-alternatives are overwritten Rest: and look for example like this: root@charion:/var/lib/dpkg/info# ls -la /etc/alternatives/i386-linux-gnu_gl_conf /etc/alternatives/x86_64-linux-gnu_gl_conf lrwxrwxrwx 1 root root 39 Aug 29 18:02 /etc/alternatives/i386-linux-gnu_gl_conf - /usr/lib/i386-linux-gnu/mesa/ld.so.conf lrwxrwxrwx 1 root root 41 Aug 29 18:02 /etc/alternatives/x86_64-linux-gnu_gl_conf - /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf This also prevents the Xserver from loading the nvidia_drv.so module [36.765] (II) LoadModule: nvidia [36.765] (WW) Warning, couldn't open module nvidia [36.765] (II) UnloadModule: nvidia [36.765] (II) Unloading nvidia [36.765] (EE) Failed to load module nvidia (module does not exist, 0) [36.765] (II) LoadModule: nouveau [36.765] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so [36.765] (II) Module nouveau: vendor=X.Org Foundation [36.765]compiled for 1.15.0, module version = 1.0.10 [36.765]Module class: X.Org Video Driver [36.765]ABI class: X.Org Video Driver, version 15.0 [36.765] (II) LoadModule: modesetting [36.765] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [36.765] (II) Module modesetting: vendor=X.Org Foundation since the link has gone AWOL ls -la /usr/lib/xorg/modules/drivers/ total 4892 drwxr-xr-x 2 root root4096 Aug 29 18:02 . drwxr-xr-x 6 root root4096 Jul 31 11:21 .. -rw-r--r-- 1 root root 10472 Jul 29 13:38 ati_drv.so -rw-r--r-- 1 root root 31704 Mai 11 07:11 cirrus_alpine.so -rw-r--r-- 1 root root 19352 Mai 11 07:11 cirrus_drv.so -rw-r--r-- 1 root root 27832 Mai 11 07:11 cirrus_laguna.so -rw-r--r-- 1 root root 23560 Feb 5 2014 fbdev_drv.so -rw-r--r-- 1 root root 1617744 Jul 29 13:32 intel_drv.so -rw-r--r-- 1 root root 174648 Feb 5 2014 mach64_drv.so -rw-r--r-- 1 root root 140656 Mai 11 07:12 mga_drv.so -rw-r--r-- 1 root root 44496 Jun 26 19:11 modesetting_drv.so -rw-r--r-- 1 root root 66544 Feb 5 2014 neomagic_drv.so -rw-r--r-- 1 root root 207440 Feb 5 2014 nouveau_drv.so -rw-r--r-- 1 root root 356336 Feb 5 2014 openchrome_drv.so -rw-r--r-- 1 root root 172456 Feb 5 2014 qxl_drv.so -rw-r--r-- 1 root root 108712 Feb 5 2014 r128_drv.so -rw-r--r-- 1 root root 434984 Jul 29 13:38 radeon_drv.so -rw-r--r-- 1 root root 57656 Feb 5 2014 s3_drv.so -rw-r--r-- 1 root root 140848 Feb 5 2014 savage_drv.so -rw-r--r-- 1 root root 112192 Feb 5 2014 siliconmotion_drv.so -rw-r--r-- 1 root root 547064 Apr 2 13:01 sis_drv.so -rw-r--r-- 1 root root 77144 Feb 5 2014 sisusb_drv.so -rw-r--r-- 1 root root 189392 Feb 5 2014 spiceqxl_drv.so -rw-r--r-- 1 root root 65936 Feb 5 2014 tdfx_drv.so -rw-r--r-- 1 root root 142224 Feb 5 2014 trident_drv.so -rw-r--r-- 1 root root 27624 Feb 5 2014 vesa_drv.so -rw-r--r-- 1 root root 157720 Apr 10 10:56 vmware_drv.so root@charion:/var/lib/dpkg/info# ./nvidia-331.postinst configure update-alternatives: automatic updates of /etc/alternatives/x86_64-linux-gnu_gl_conf are disabled; leaving it alone update-alternatives: to return to automatic updates use 'update-alternatives --auto x86_64-linux-gnu_gl_conf' update-alternatives: automatic updates of /etc/alternatives/x86_64-linux-gnu_gl_conf are disabled; leaving it alone update-alternatives: to return to
[Desktop-packages] [Bug 1320436] [NEW] Please update to 337.19 - Linux kernel 3.15 is not supported with this old version
Public bug reported: Please update to 337.19 - Linux kernel 3.15 is not supported with this old version [...] Preparing to unpack .../linux-image-3.15.0-1-generic_3.15.0-1.3_amd64.deb ... Done. Unpacking linux-image-3.15.0-1-generic (3.15.0-1.3) ... Preparing to unpack .../upstart_1.12.1-0ubuntu7_amd64.deb ... [...] Setting up linux-image-3.15.0-1-generic (3.15.0-1.3) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic Error! Bad return status for module build on kernel: 3.15.0-1-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates-uvm/331.38/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic update-initramfs: Generating /boot/initrd.img-3.15.0-1-generic [...] Setting up linux-image-generic (3.15.0.1.2) ... Setting up linux-headers-3.15.0-1 (3.15.0-1.3) ... Setting up linux-headers-3.15.0-1-generic (3.15.0-1.3) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic Error! Bad return status for module build on kernel: 3.15.0-1-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates-uvm/331.38/build/make.log for more information. Setting up linux-headers-generic (3.15.0.1.2) ... [...] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 17 09:29:07 2014 InstallationDate: Installed on 2014-02-04 (102 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202) SourcePackage: nvidia-graphics-drivers-331-updates UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331-updates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kernel nvidia utopic ** Attachment added: /var/lib/dkms/nvidia-331-updates-uvm/331.38/build/make.log https://bugs.launchpad.net/bugs/1320436/+attachment/4114227/+files/make.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331-updates in Ubuntu. https://bugs.launchpad.net/bugs/1320436 Title: Please update to 337.19 - Linux kernel 3.15 is not supported with this old version Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: New Bug description: Please update to 337.19 - Linux kernel 3.15 is not supported with this old version [...] Preparing to unpack .../linux-image-3.15.0-1-generic_3.15.0-1.3_amd64.deb ... Done. Unpacking linux-image-3.15.0-1-generic (3.15.0-1.3) ... Preparing to unpack .../upstart_1.12.1-0ubuntu7_amd64.deb ... [...] Setting up linux-image-3.15.0-1-generic (3.15.0-1.3) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic Error! Bad return status for module build on kernel: 3.15.0-1-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates-uvm/331.38/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic update-initramfs: Generating /boot/initrd.img-3.15.0-1-generic [...] Setting up linux-image-generic (3.15.0.1.2) ... Setting up linux-headers-3.15.0-1 (3.15.0-1.3) ... Setting up linux-headers-3.15.0-1-generic (3.15.0-1.3) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.15.0-1-generic /boot/vmlinuz-3.15.0-1-generic Error! Bad return status for module build on kernel: 3.15.0-1-generic (x86_64) Consult /var/lib/dkms/nvidia-331-updates-uvm/331.38/build/make.log for more information. Setting up linux-headers-generic (3.15.0.1.2) ... [...] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331-updates 331.38-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: XFCE Date: Sat May 17 09:29:07 2014 InstallationDate: Installed on 2014-02-04 (102 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Alpha amd64 (20140202) SourcePackage: nvidia-graphics-drivers-331-updates UpgradeStatus: No upgrade
Re: [Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep
On 05.04.2014 10:31, Arjen wrote: I have the same issue with my HTPC, using a brand new Pioneer receiver (and the same with a older Marantz). Switching either of those receivers in standby is probably similar to just pulling out the hdmi-plug. In the Xorg.0.log I see this, when I turn a receiver off: (II) NVIDIA(0): Setting mode NULL And when the receiver is turned back on again, I see the normal report of its EDID information. I have another workaround to switch it back on again, since I use x11vnc, I have access to my display server via the network. Using nvidia-settings I can see under X Server Display Configuration it has switched the Resolution to off. Switching that back to Auto or 1920x1080 also re-enables my screen. When I do that, I see this in the Xorg.0.log: (II) NVIDIA(0): Setting mode DPY-1:1920x1080+0+0 It'd be nice if it did that automatically when the screen is turned on again. Guys, what you're describing is an entirely DIFFERENT issue. This is an HDMI handshaking issue that plagues many receivers and other devices in the middle of an HDMI chain. Please open a seperate bug for this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: DPMS support broken, fails to wake up the monitor after putting it to sleep Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Bug description: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep
@Ivan R.: Good to hear, I'll also verify the CTRL-ALT-F1 - CTRL- ALT-F7 workaround next week when I'll have access to my M4800 again. How is your console configured? Do you boot the kernel with the nomodeset parameter? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: DPMS support broken, fails to wake up the monitor after putting it to sleep Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Bug description: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep
On 31.03.2014 18:48, Raj B wrote: to clarify, switching off the projector is fine. turning off the receiver causes the issue. In all cases, nothing is done to the computer itself. It is on and fully operational at all times (i.e., it is never suspended / shut down etc.). What happens when you connect the projector directly to your PC? I sometimes have a similar issue with a Samsung TV, a Denon 4308 Receiver and a Raspberry Pi. The problem here is the receiver in the middle. Cheers Mike -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: DPMS support broken, fails to wake up the monitor after putting it to sleep Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Bug description: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1268151] Re: DPMS support broken, fails to wake up the monitor after putting it to sleep
On 24.03.2014 12:33, Marius B. Kotsbak wrote: Hmm, I wonder if this is the same I see with my M4800 running 12.04 LTS. A workaround for me is typing CTRL-ALT-F1 and then CTRL-ALT-F7. Does this work for you too? ** Tags added: precise I can't check before April 7th. I just went on holiday and only took my old laptop with me. I can't remember trying that while the screen was dark. I boot my M4800 with nomodeset to get a console - did you figure out a better setting? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-331 in Ubuntu. https://bugs.launchpad.net/bugs/1268151 Title: DPMS support broken, fails to wake up the monitor after putting it to sleep Status in “nvidia-graphics-drivers-331” package in Ubuntu: Triaged Bug description: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1268151/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1268151] [NEW] DPMS support broken, fails to wake up the monitor after putting it to sleep
Public bug reported: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. HW is Dell Precision M4800 with GK106GLM [Quadro K2100M] and QHD+ display Once the display shuts off, it will not be woken up anymore and the screen stays dark. Only a restart of the Xserver will bring back the display at that point. A cycle of xset dpms force off; sleep 30; xset dpms force on will leave the display dark. At the moment I help myself by not allowing DPMS to switch off the display: neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: auto repeat: onkey click percent: 0LED mask: XKB indicators: 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off 03: Compose: off04: Kana:off05: Sleep: off 06: Suspend: off07: Mute:off08: Misc:off 09: Mail:off10: Charging:off11: Shift Lock: off 12: Group 2: off13: Mouse Keys: off auto repeat delay: 500repeat rate: 20 auto repeating keys: 00ffdbbf fadfffefffed 9fff fff7 bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: acceleration: 2/1threshold: 4 Screen Saver: prefer blanking: yesallow exposures: yes timeout: 0cycle: 0 Colors: default colormap: 0x20BlackPixel: 0x0WhitePixel: 0xff Font Path: /usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,built-ins DPMS (Energy Star): Standby: 0Suspend: 0Off: 0 DPMS is Enabled Monitor is On ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-331 331.20-0ubuntu9 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.1-0ubuntu1 Architecture: amd64 Date: Sat Jan 11 12:06:30 2014 InstallationDate: Installed on 2014-01-07 (3 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Description changed: Also affects nvidia-graphics-drivers-319 The effect is identical to https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/958279 but with Nvidia instead of AMD/ATI drivers. Once the display shuts off, it will not be woken up anymore and the screen stays dark. - Only a restart of the Xserver with bring back the display at that point. + Only a restart of the Xserver will bring back the display at that point. - A cycle of - xset dpms force off; sleep 30; xset dpms force on + A cycle of + xset dpms force off; sleep 30; xset dpms force on will leave the display dark. - - At them moment I help myself by not allowing DPMS to switch off the display: - neuffer@charion:~$ xset dpms 0 0 0 + At the moment I help myself by not allowing DPMS to switch off the display: + neuffer@charion:~$ xset dpms 0 0 0 neuffer@charion:~$ xset -q -d :0.0 Keyboard Control: - auto repeat: onkey click percent: 0LED mask: - XKB indicators: - 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off - 03: Compose: off04: Kana:off05: Sleep: off - 06: Suspend: off07: Mute:off08: Misc:off - 09: Mail:off10: Charging:off11: Shift Lock: off - 12: Group 2: off13: Mouse Keys: off - auto repeat delay: 500repeat rate: 20 - auto repeating keys: 00ffdbbf - fadfffefffed - 9fff - fff7 - bell percent: 50bell pitch: 400bell duration: 100 + auto repeat: onkey click percent: 0LED mask: + XKB indicators: + 00: Caps Lock: off01: Num Lock:off02: Scroll Lock: off + 03: Compose: off04: Kana:off05: Sleep: off + 06: Suspend: off07: Mute:off08: Misc:off + 09: Mail:off10: Charging:off11: Shift Lock: off + 12: Group 2: off13: Mouse Keys: off + auto repeat delay: 500repeat rate: 20 + auto repeating keys: 00ffdbbf + fadfffefffed + 9fff + fff7 + bell percent: 50bell pitch: 400bell duration: 100 Pointer Control: - acceleration: 2/1threshold: 4 + acceleration: 2/1threshold: 4
[Desktop-packages] [Bug 576648] Re: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.)
root@kyle:/var/lib/dkms/nvidia-experimental-310/310.14/build# apt-get install --reinstall nvidia-experimental-310 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-image-3.8.0-14-generic linux-image-3.8.0-15-generic linux-image-extra-3.8.0-14-generic linux-image-extra-3.8.0-15-generic Use 'apt-get autoremove' to remove them. 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 5 not upgraded. Need to get 67.0 MB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://ftp.ubuntu.com/ubuntu/ raring/restricted nvidia-experimental-310 amd64 310.14-0ubuntu2 [67.0 MB] Fetched 67.0 MB in 7s (9,525 kB/s) (Reading database ... 273009 files and directories currently installed.) Preparing to replace nvidia-experimental-310 310.14-0ubuntu2 (using .../nvidia-experimental-310_310.14-0ubuntu2_amd64.deb) ... Removing all DKMS Modules Done. Unpacking replacement nvidia-experimental-310 ... Processing triggers for man-db ... Processing triggers for desktop-file-utils ... Processing triggers for gnome-menus ... Setting up nvidia-experimental-310 (310.14-0ubuntu2) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-experimental-310 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad Loading new nvidia-experimental-310-310.14 DKMS files... Building only for 3.8.0-17-generic Building for architecture x86_64 Building initial module for 3.8.0-17-generic Traceback (most recent call last): File /usr/share/apport/package-hooks/dkms_packages.py, line 22, in module import apport ImportError: No module named apport Error! Bad return status for module build on kernel: 3.8.0-17-generic (x86_64) Consult /var/lib/dkms/nvidia-experimental-310/310.14/build/make.log for more information. Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-3.8.0-17-generic [ Rootkit Hunter version 1.4.0 ] File updated: searched for 169 files, found 138 localepurge: Disk space freed in /usr/share/locale: 0 KiB localepurge: Disk space freed in /usr/share/man: 0 KiB localepurge: Disk space freed in /usr/share/gnome/help: 0 KiB localepurge: Disk space freed in /usr/share/omf: 0 KiB localepurge: Disk space freed in /usr/share/doc/kde/HTML: 0 KiB Total disk space freed by localepurge: 0 KiB root@kyle:/var/lib/dkms/nvidia-experimental-310/310.14/build# - KMS make.log for nvidia-experimental-310-310.14 for kernel 3.8.0-17-generic (x86_64) Tue Apr 9 20:34:23 CEST 2013 If you are using a Linux 2.4 kernel, please make sure you either have configured kernel sources matching your kernel or the correct set of kernel headers installed on your system. If you are using a Linux 2.6 kernel, please make sure you have configured kernel sources matching your kernel installed on your system. If you specified a separate output directory using either the KBUILD_OUTPUT or the O KBUILD parameter, make sure to specify this directory with the SYSOUT environment variable or with the equivalent nvidia-installer command line option. Depending on where and how the kernel sources (or the kernel headers) were installed, you may need to specify their location with the SYSSRC environment variable or the equivalent nvidia-installer command line option. *** Unable to determine the target kernel version. *** make: *** [select_makefile] Error 1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/576648 Title: package nvidia-* failed to install/upgrade: nvidia-* kernel module failed to build (Unable to determine the target kernel version.) Status in NVIDIA Drivers Ubuntu: Confirmed Status in “nvidia-graphics-drivers” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-96” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-experimental-304” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-experimental-310” package in Ubuntu: Triaged Status in “nvidia-graphics-drivers-updates” package in Ubuntu: Triaged Bug description: WORKAROUND: Revert back to the kernel version that your Ubuntu release came with: Ubuntu 10.04 -- kernel 2.6.32 Ubuntu 11.04 -- kernel 2.6.38 TEST CASE FOR 10.04: Starting with a fresh Ubuntu 10.04.3 installation... sudo add-apt-repository ppa:kernel-ppa/ppa sudo apt-get update sudo apt-get install linux-image-3.0.0-8-generic sudo apt-get install
[Desktop-packages] [Bug 1078543] Re: Pulse audio failed to start; no audio present in raring
Some modules seem indeed to be 32 bit, I have the same issue root@kyle:/usr/lib/pulse-2.1/modules# file *| grep -v 64-bit libprotocol-esound.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xba465c853f9f4a756be3c5799004d5dad154d779, stripped module-esound-compat-spawnfd.so:ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xfb762fd5be52f7ecacdcd853e03620c1a55ae9a1, stripped module-esound-compat-spawnpid.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xcbf384e8214682b6b01fa73a8fb29454ae69842e, stripped module-esound-protocol-tcp.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xf20628b16f34bf4109d8cf27c5a4f6159485bf6f, stripped module-esound-protocol-unix.so: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), dynamically linked, BuildID[sha1]=0xe22999757c6a8a55851c0d46d7eb60b287619536, stripped root@kyle:/usr/lib/pulse-2.1/modules# root@kyle:/usr/lib/pulse-2.1/modules# for a in libprotocol-esound.so module-esound-compat-spawnfd.so module-esound-compat-spawnpid.so module-esound-protocol-tcp.so module-esound-protocol-unix.so do dpkg -S `pwd`/$a done pulseaudio-esound-compat: /usr/lib/pulse-2.1/modules/libprotocol-esound.so pulseaudio-esound-compat: /usr/lib/pulse-2.1/modules/module-esound-compat-spawnfd.so pulseaudio-esound-compat: /usr/lib/pulse-2.1/modules/module-esound-compat-spawnpid.so pulseaudio-esound-compat: /usr/lib/pulse-2.1/modules/module-esound-protocol-tcp.so pulseaudio-esound-compat: /usr/lib/pulse-2.1/modules/module-esound-protocol-unix.so It seems that the upgrade installs the 32bit version instead of the 64bit one. pulseaudio-esound-compat:i386 - PulseAudio ESD compatibility layer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1078543 Title: Pulse audio failed to start; no audio present in raring Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: When I dist-upgraded to raring I lost audio. The indicator and settings showed no volume control. Some debugging later showed that pulse audio wasn't running. When running manually: bob@alchemy:~/bzr/ubuntu/vte3$ pulseaudio E: [pulseaudio] module.c: Failed to open module module-esound-protocol-unix: file not found E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. I installed pulseaudio-esound-compat and then it worked: bob@alchemy:~/bzr/ubuntu/vte3$ sudo apt-get install pulseaudio-esound-compat Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: pulseaudio-esound-compat:i386 The following NEW packages will be installed: pulseaudio-esound-compat 0 upgraded, 1 newly installed, 1 to remove and 26 not upgraded. Need to get 36.8 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue [Y/n]? Luke said it worked for him without this module, but it appears having the i386 module installed was confusing pulse into thinking it was available but being unable to load it (I am using an amd64 machine). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 2.6.2-0ubuntu3 Architecture: amd64 CheckboxSubmission: e440e09ef58a53bccc45087674ba6b8e CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Nov 14 15:15:35 2012 InstallationDate: Installed on 2011-04-01 (593 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to raring on 2011-07-05 (497 days ago) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0NVXFV dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3500:pvrA10:rvnDellInc.:rn0NVXFV:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3500 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1078543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078543] Re: Pulse audio failed to start; no audio present in raring
replace pulseaudio-esound-compat:i386 with pulseaudio-esound-compat:amd64 and the pulseaudo server will be able to start again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1078543 Title: Pulse audio failed to start; no audio present in raring Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: When I dist-upgraded to raring I lost audio. The indicator and settings showed no volume control. Some debugging later showed that pulse audio wasn't running. When running manually: bob@alchemy:~/bzr/ubuntu/vte3$ pulseaudio E: [pulseaudio] module.c: Failed to open module module-esound-protocol-unix: file not found E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. I installed pulseaudio-esound-compat and then it worked: bob@alchemy:~/bzr/ubuntu/vte3$ sudo apt-get install pulseaudio-esound-compat Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: pulseaudio-esound-compat:i386 The following NEW packages will be installed: pulseaudio-esound-compat 0 upgraded, 1 newly installed, 1 to remove and 26 not upgraded. Need to get 36.8 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue [Y/n]? Luke said it worked for him without this module, but it appears having the i386 module installed was confusing pulse into thinking it was available but being unable to load it (I am using an amd64 machine). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 2.6.2-0ubuntu3 Architecture: amd64 CheckboxSubmission: e440e09ef58a53bccc45087674ba6b8e CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Nov 14 15:15:35 2012 InstallationDate: Installed on 2011-04-01 (593 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to raring on 2011-07-05 (497 days ago) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0NVXFV dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3500:pvrA10:rvnDellInc.:rn0NVXFV:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3500 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1078543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1078543] Re: Pulse audio failed to start; no audio present in raring
remove pulseaudio-esound-compat:i386 and install pulseaudio-esound-compat:amd64 instead and the pulseaudio server will start again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1078543 Title: Pulse audio failed to start; no audio present in raring Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: When I dist-upgraded to raring I lost audio. The indicator and settings showed no volume control. Some debugging later showed that pulse audio wasn't running. When running manually: bob@alchemy:~/bzr/ubuntu/vte3$ pulseaudio E: [pulseaudio] module.c: Failed to open module module-esound-protocol-unix: file not found E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. I installed pulseaudio-esound-compat and then it worked: bob@alchemy:~/bzr/ubuntu/vte3$ sudo apt-get install pulseaudio-esound-compat Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: pulseaudio-esound-compat:i386 The following NEW packages will be installed: pulseaudio-esound-compat 0 upgraded, 1 newly installed, 1 to remove and 26 not upgraded. Need to get 36.8 kB of archives. After this operation, 8,192 B of additional disk space will be used. Do you want to continue [Y/n]? Luke said it worked for him without this module, but it appears having the i386 module installed was confusing pulse into thinking it was available but being unable to load it (I am using an amd64 machine). ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: pulseaudio 1:2.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 2.6.2-0ubuntu3 Architecture: amd64 CheckboxSubmission: e440e09ef58a53bccc45087674ba6b8e CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed Nov 14 15:15:35 2012 InstallationDate: Installed on 2011-04-01 (593 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta amd64 (20110330) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to raring on 2011-07-05 (497 days ago) dmi.bios.date: 10/25/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0NVXFV dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A10 dmi.modalias: dmi:bvnDellInc.:bvrA10:bd10/25/2010:svnDellInc.:pnVostro3500:pvrA10:rvnDellInc.:rn0NVXFV:rvrA10:cvnDellInc.:ct8:cvrA10: dmi.product.name: Vostro 3500 dmi.product.version: A10 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1078543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1036998] [NEW] [with fix] gnome-keyring installs duplicate identical config files gnome-keyring[-.]module
Public bug reported: root@kyle:/etc/pkcs11/modules# ls -la total 16 drwxr-xr-x 2 root root 4096 Aug 13 08:43 . drwxr-xr-x 3 root root 4096 Sep 9 2011 .. -rw-r--r-- 1 root root 293 Sep 18 2011 gnome-keyring-module -rw-r--r-- 1 root root 293 Aug 13 02:57 gnome-keyring.module root@kyle:/etc/pkcs11/modules# dpkg -S gnome-keyring-module gnome-keyring: /etc/pkcs11/modules/gnome-keyring-module root@kyle:/etc/pkcs11/modules# dpkg -S gnome-keyring.module gnome-keyring: /etc/pkcs11/modules/gnome-keyring.module root@kyle:/etc/pkcs11/modules# diff gnome-keyring-module gnome-keyring.module root@kyle:/etc/pkcs11/modules# This causes errors : p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so Fix: One of the two /etc/pkcs11/modules/gnome-keyring[.-]module files should be removed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-keyring 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Wed Aug 15 09:55:53 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1036998 Title: [with fix] gnome-keyring installs duplicate identical config files gnome-keyring[-.]module Status in “gnome-keyring” package in Ubuntu: New Bug description: root@kyle:/etc/pkcs11/modules# ls -la total 16 drwxr-xr-x 2 root root 4096 Aug 13 08:43 . drwxr-xr-x 3 root root 4096 Sep 9 2011 .. -rw-r--r-- 1 root root 293 Sep 18 2011 gnome-keyring-module -rw-r--r-- 1 root root 293 Aug 13 02:57 gnome-keyring.module root@kyle:/etc/pkcs11/modules# dpkg -S gnome-keyring-module gnome-keyring: /etc/pkcs11/modules/gnome-keyring-module root@kyle:/etc/pkcs11/modules# dpkg -S gnome-keyring.module gnome-keyring: /etc/pkcs11/modules/gnome-keyring.module root@kyle:/etc/pkcs11/modules# diff gnome-keyring-module gnome-keyring.module root@kyle:/etc/pkcs11/modules# This causes errors : p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so Fix: One of the two /etc/pkcs11/modules/gnome-keyring[.-]module files should be removed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-keyring 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Wed Aug 15 09:55:53 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1036998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1036998] Re: [with fix] gnome-keyring installs duplicate identical config files gnome-keyring[-.]module
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1036998 Title: [with fix] gnome-keyring installs duplicate identical config files gnome-keyring[-.]module Status in “gnome-keyring” package in Ubuntu: New Bug description: root@kyle:/etc/pkcs11/modules# ls -la total 16 drwxr-xr-x 2 root root 4096 Aug 13 08:43 . drwxr-xr-x 3 root root 4096 Sep 9 2011 .. -rw-r--r-- 1 root root 293 Sep 18 2011 gnome-keyring-module -rw-r--r-- 1 root root 293 Aug 13 02:57 gnome-keyring.module root@kyle:/etc/pkcs11/modules# dpkg -S gnome-keyring-module gnome-keyring: /etc/pkcs11/modules/gnome-keyring-module root@kyle:/etc/pkcs11/modules# dpkg -S gnome-keyring.module gnome-keyring: /etc/pkcs11/modules/gnome-keyring.module root@kyle:/etc/pkcs11/modules# diff gnome-keyring-module gnome-keyring.module root@kyle:/etc/pkcs11/modules# This causes errors : p11-kit: duplicate configured module: gnome-keyring.module: /usr/lib/x86_64-linux-gnu/pkcs11/gnome-keyring-pkcs11.so Fix: One of the two /etc/pkcs11/modules/gnome-keyring[.-]module files should be removed. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-keyring 3.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0 Uname: Linux 3.5.0-8-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Wed Aug 15 09:55:53 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901) SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1036998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 431177] Re: Dell 5520 Mobile Broadband card is again not beeing detected by NetworkManager 0.8 on Karmic
On 01.07.2012 12:25, Thomas Hood wrote: Has this been fixed in Ubuntu 12.04? ** Changed in: network-manager (Ubuntu) Status: New = Incomplete Yes. But the Network manager has developed another anoying problem: When the network connection fails (while beeing on the train for example), the connection not only is not beeing automatically re-established, but instead NM is not even able to establish a manually triggered connection anymore, even even when good reception is available. Sometimes it even looses all knowledge about the available UMTS Modem. In those cases only a complete NM restart will bring the subsystem back to life. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/431177 Title: Dell 5520 Mobile Broadband card is again not beeing detected by NetworkManager 0.8 on Karmic Status in “network-manager” package in Ubuntu: Incomplete Bug description: Binary package hint: network-manager Somewhat similar to #262498 (same hardware, different symptoms) network manager doesn't detect the Dell 5520 Mobile Broadband HSDPA card. Somewhere between the releases network-manager_0.7.1.git.5.272c6a626 and some higher version network manager looses the ability to detect/manage this card. Downgrading to network-manager_0.7.1.git.5.272c6a626 and network-manager-applet_0.7.1~rc4.1 instantly restores the functionality. Current version: network-manager: Installed: 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6 Candidate: 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6 Version table: *** 0.8~a~git.20090911t130220.4c77fa0-0ubuntu6 0 500 http://archive.ubuntu.com karmic/main Packages 100 /var/lib/dpkg/status 0.8~a~git.20090911t130220.4c77fa0-0ubuntu1~nmt1 0 500 http://ppa.launchpad.net karmic/main Packages HAL listing: udi = '/org/freedesktop/Hal/devices/usb_device_413c_8137_Novatel_Wireless_HSDPA_Modem' info.linux.driver = 'usb' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_1d6b_1__00_1a_1' (string) info.product = 'Wireless 5520 Voda L Mobile Broadband (3G HSDPA) Minicard Status Port' (string) info.subsystem = 'usb_device' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_413c_8137_Novatel_Wireless_HSDPA_Modem' (string) info.vendor = 'Dell Computer Corp.' (string) linux.device_file = '/dev/bus/usb/004/002' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'usb' (string) linux.sysfs_path = '/sys/devices/pci:00/:00:1a.1/usb4/4-2' (string) usb_device.bus_number = 4 (0x4) (int) usb_device.can_wake_up = true (bool) usb_device.configuration_value = 1 (0x1) (int) usb_device.device_class = 0 (0x0) (int) usb_device.device_protocol = 0 (0x0) (int) usb_device.device_revision_bcd = 0 (0x0) (int) usb_device.device_subclass = 0 (0x0) (int) usb_device.is_self_powered = true (bool) usb_device.linux.device_number = 2 (0x2) (int) usb_device.linux.sysfs_path = '/sys/devices/pci:00/:00:1a.1/usb4/4-2' (string) usb_device.max_power = 100 (0x64) (int) usb_device.num_configurations = 1 (0x1) (int) usb_device.num_interfaces = 2 (0x2) (int) usb_device.num_ports = 0 (0x0) (int) usb_device.product = 'Wireless 5520 Voda L Mobile Broadband (3G HSDPA) Minicard Status Port' (string) usb_device.product_id = 33079 (0x8137) (int) usb_device.serial = 'Novatel Wireless HSDPA Modem' (string) usb_device.speed = 12.0 (12) (double) usb_device.vendor = 'Dell Computer Corp.' (string) usb_device.vendor_id = 16700 (0x413c) (int) usb_device.version = 1.1 (1.1) (double) udi = '/org/freedesktop/Hal/devices/usb_device_413c_8137_Novatel_Wireless_HSDPA_Modem_if1' info.linux.driver = 'option' (string) info.parent = '/org/freedesktop/Hal/devices/usb_device_413c_8137_Novatel_Wireless_HSDPA_Modem' (string) info.product = 'USB Vendor Specific Interface' (string) info.subsystem = 'usb' (string) info.udi = '/org/freedesktop/Hal/devices/usb_device_413c_8137_Novatel_Wireless_HSDPA_Modem_if1' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'usb' (string) linux.sysfs_path = '/sys/devices/pci:00/:00:1a.1/usb4/4-2/4-2:1.1' (string) usb.bus_number = 4 (0x4) (int) usb.can_wake_up = true (bool) usb.configuration_value = 1 (0x1) (int) usb.device_class = 0 (0x0) (int) usb.device_protocol = 0 (0x0) (int) usb.device_revision_bcd = 0 (0x0) (int) usb.device_subclass = 0 (0x0) (int) usb.interface.class = 255 (0xff) (int) usb.interface.description = 'Data Interface' (string) usb.interface.number = 1 (0x1) (int) usb.interface.protocol = 255 (0xff) (int) usb.interface.subclass = 255 (0xff) (int)
Re: [Desktop-packages] [Bug 864479] Re: System goes to hibernate or suspend even when set to Don't suspend
On 10/03/2011 10:57 AM, Rodrigo Moya wrote:
Before setting it, can you please let us know what are the values for
sleep-inactive-ac-timeout, sleep-inactive-ac, sleep-inactive-
battery-timeout and sleep-inactive-battery?
You can get the values fromt he command line with:
gsettings get org.gnome.settings-daemon.plugins.power $key
** Changed in: gnome-control-center (Ubuntu Oneiric)
Assignee: (unassigned) = Rodrigo Moya (rodrigo-moya)
I followed Colins suggestion to force sleep-inactive-{ac, battery}-type
to 'nothing' with gsettings. Before they had been set to hibernate, even
so I had played with several different values in the power settings before.
gsettings list-recursively org.gnome.settings-daemon.plugins.power
org.gnome.settings-daemon.plugins.power active true
org.gnome.settings-daemon.plugins.power button-hibernate 'hibernate'
org.gnome.settings-daemon.plugins.power button-power 'interactive'
org.gnome.settings-daemon.plugins.power button-sleep 'suspend'
org.gnome.settings-daemon.plugins.power button-suspend 'suspend'
org.gnome.settings-daemon.plugins.power critical-battery-action 'shutdown'
org.gnome.settings-daemon.plugins.power idle-brightness 30
org.gnome.settings-daemon.plugins.power idle-dim-ac false
org.gnome.settings-daemon.plugins.power idle-dim-battery true
org.gnome.settings-daemon.plugins.power idle-dim-time 10
org.gnome.settings-daemon.plugins.power lid-close-ac-action 'nothing'
org.gnome.settings-daemon.plugins.power lid-close-battery-action 'nothing'
org.gnome.settings-daemon.plugins.power notify-perhaps-recall true
org.gnome.settings-daemon.plugins.power percentage-action 2
org.gnome.settings-daemon.plugins.power percentage-critical 3
org.gnome.settings-daemon.plugins.power percentage-low 10
org.gnome.settings-daemon.plugins.power priority 1
org.gnome.settings-daemon.plugins.power sleep-display-ac 600
org.gnome.settings-daemon.plugins.power sleep-display-battery 600
org.gnome.settings-daemon.plugins.power sleep-inactive-ac false
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 1800
org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'nothing'
org.gnome.settings-daemon.plugins.power sleep-inactive-battery false
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 0
org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type
'nothing'
org.gnome.settings-daemon.plugins.power time-action 120
org.gnome.settings-daemon.plugins.power time-critical 300
org.gnome.settings-daemon.plugins.power time-low 1200
org.gnome.settings-daemon.plugins.power use-time-for-policy true
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/864479
Title:
System goes to hibernate or suspend even when set to Don't suspend
Status in “gnome-control-center” package in Ubuntu:
Confirmed
Status in “gnome-control-center” source package in Oneiric:
Confirmed
Bug description:
System goes to hibernate or suspend even when set to Don't suspend on
the Suspend when inactive setting
I use the affected Laptop additionally as a fileserver. The
powermanagement in 11.10 changed in the last few days in a way so that
I can't let the laptop sit without console input for more then 30
minutes without it going into hibernate or suspend regardles of what
long running background processes I have. NFS services are beeing
interrupted, ssh connections (with long running upgrade sessions on
remote Debian/Ubuntu servers) etc pp.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: gnome-control-center 1:3.2.0-0ubuntu4
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sun Oct 2 08:53:23 2011
InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901)
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_gnome-control-center:
deja-dup 20.0-0ubuntu3
gnome-bluetooth3.2.0-0ubuntu1
indicator-datetime 0.3.0-0ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/864479/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 864479] Re: System goes to hibernate or suspend even when set to Don't suspend
** Description changed: - System goes to hibernate or suspend even when set to Don't suspend on + System goes to hibernate or suspend even when set to Don't suspend on the Suspend when inactive setting - I use the affected Laptop additionally as a fileserver. The powermanagement in 11.10 changed - in the last few days in a way so that I can't let the laptop sit without console input for more then - 30 minutes without it going into hibernate or suspend regardles of what long running background - processes I have. NFS services are beeing interrupted, ssh connections (with long running upgrade - sessions on remote Debian/Ubuntu servers) etc pp. + I use the affected Laptop additionally as a fileserver. The + powermanagement in 11.10 changed in the last few days in a way so that I + can't let the laptop sit without console input for more then 30 minutes + without it going into hibernate or suspend regardles of what long + running background processes I have. NFS services are beeing + interrupted, ssh connections (with long running upgrade sessions on + remote Debian/Ubuntu servers) etc pp. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 2 08:53:23 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901) ProcEnviron: - LANGUAGE=en_US:en - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: - deja-dup 20.0-0ubuntu3 - gnome-bluetooth3.2.0-0ubuntu1 - indicator-datetime 0.3.0-0ubuntu1 + deja-dup 20.0-0ubuntu3 + gnome-bluetooth3.2.0-0ubuntu1 + indicator-datetime 0.3.0-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/864479 Title: System goes to hibernate or suspend even when set to Don't suspend Status in “gnome-control-center” package in Ubuntu: New Bug description: System goes to hibernate or suspend even when set to Don't suspend on the Suspend when inactive setting I use the affected Laptop additionally as a fileserver. The powermanagement in 11.10 changed in the last few days in a way so that I can't let the laptop sit without console input for more then 30 minutes without it going into hibernate or suspend regardles of what long running background processes I have. NFS services are beeing interrupted, ssh connections (with long running upgrade sessions on remote Debian/Ubuntu servers) etc pp. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 2 08:53:23 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110901) ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu1 indicator-datetime 0.3.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/864479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
