[Desktop-packages] [Bug 1497996] Re: When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check
This is occurring on both i386 and amd64 VM's. The description has been updated to this effect. ** Description changed: - This is noticed during health-check's tests on trusty (mostly i386) - ISO's. + This is noticed during health-check's tests on trusty (mostly i386 but + also on amd64) ISO's. The failed builds in https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-desktop-i386-smoke-health-check/ are all due to this issue. - The following is excerpts from cking's debugging of the failure: "NetworkManager does not show this issue when no connections are made old connections are re-established. Only new connections since reboot seem to trigger this. The large mmap is a bit ridiculous, it's either the heap (via malloc/free) or glib memory allocator being a bit generous in the way it requests more memory for the heap or network manager itself doing a large mmap request (which I think is very unlikely). The good news is that the memory is mapped but not all used, so there is little actual physical demand for these mapped in pages. Even so, I think it may be worth somebody with NetworkManager experience to dig in deeper to see why and where this allocation is occurring as a medium/low bug. To reproduce this issue: 1. Clean boot 2. Wait until existing network connections are established (e.g. wifi) 3. Run health-check on Network Manager 4. Make a new connection, e.g. plug in ethernet connection for an auto-ethernet connection to be established. 5. Stop health-check, observe that a huge allocation has occurred." ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 Date: Mon Sep 21 13:24:45 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-08 (13 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150908) IpRoute: default via 192.168.122.1 dev eth0 proto static 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.148 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 185b3134d-a657-40be-8229-248bcd0ce79c 802-3-ethernet1442841756 Mon 21 Sep 2015 01:22:36 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled -- 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/1497996 Title: When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check Status in network-manager package in Ubuntu: New Bug description: This is noticed during health-check's tests on trusty (mostly i386 but also on amd64) ISO's. The failed builds in https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-desktop-i386-smoke-health-check/ are all due to this issue. The following is excerpts from cking's debugging of the failure: "NetworkManager does not show this issue when no connections are made old connections are re-established. Only new connections since reboot seem to trigger this. The large mmap is a bit ridiculous, it's either the heap (via malloc/free) or glib memory allocator being a bit generous in the way it requests more memory for the heap or network manager itself doing a large mmap request (which I think is very unlikely). The good news is that the memory is mapped but not all used, so there is little actual physical demand for these mapped in pages. Even so, I think it may be worth somebody with NetworkManager experience to dig in deeper to see why and where this allocation is occurring as a
[Desktop-packages] [Bug 1497996] [NEW] When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check
Public bug reported: This is noticed during health-check's tests on trusty (mostly i386) ISO's. The failed builds in https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-desktop-i386-smoke-health-check/ are all due to this issue. The following is excerpts from cking's debugging of the failure: "NetworkManager does not show this issue when no connections are made old connections are re-established. Only new connections since reboot seem to trigger this. The large mmap is a bit ridiculous, it's either the heap (via malloc/free) or glib memory allocator being a bit generous in the way it requests more memory for the heap or network manager itself doing a large mmap request (which I think is very unlikely). The good news is that the memory is mapped but not all used, so there is little actual physical demand for these mapped in pages. Even so, I think it may be worth somebody with NetworkManager experience to dig in deeper to see why and where this allocation is occurring as a medium/low bug. To reproduce this issue: 1. Clean boot 2. Wait until existing network connections are established (e.g. wifi) 3. Run health-check on Network Manager 4. Make a new connection, e.g. plug in ethernet connection for an auto-ethernet connection to be established. 5. Stop health-check, observe that a huge allocation has occurred." ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.1 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 Date: Mon Sep 21 13:24:45 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-09-08 (13 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150908) IpRoute: default via 192.168.122.1 dev eth0 proto static 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.148 metric 1 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 185b3134d-a657-40be-8229-248bcd0ce79c 802-3-ethernet1442841756 Mon 21 Sep 2015 01:22:36 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty ** Summary changed: - when a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second (30 minute) run of heath-check + When a new connection occurs, NetworkManager mmaps 64Mb hunk which is equivalent to the 32.28Kb per second rate over a 1800 second run of heath-check ** Description changed: This is noticed during health-check's tests on trusty (mostly i386) ISO's. The failed builds in https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job /trusty-desktop-i386-smoke-health-check/ are all due to this issue. - NetworkManager does not show this issue when no connections are made old + + The following is excerpts from cking's debugging of the failure: + + "NetworkManager does not show this issue when no connections are made old connections are re-established. Only new connections since reboot seem to trigger this. + The large mmap is a bit ridiculous, it's either the heap (via + malloc/free) or glib memory allocator being a bit generous in the way it + requests more memory for the heap or network manager itself doing a + large mmap request (which I think is very unlikely). + + The good news is that the memory is mapped but not all used, so there is + little actual physical demand for these mapped in pages. Even so, I + think it may be worth somebody with NetworkManager experience to dig in + deeper to see why and where this allocation is occurring as a medium/low + bug. To reproduce this issue: 1. Clean boot 2. Wait until existing network connections are established (e.g. wifi) 3. Run health-check on Network Manager 4. Make a new connection, e.g.
[Desktop-packages] [Bug 1351262] [NEW] precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~)'
Public bug reported: Precise alternate preseeded installations fail with unmet deps due to the following: Jul 31 08:54:29 in-target: The following information may help to resolve the situation: Jul 31 08:54:29 in-target: Jul 31 08:54:29 in-target: The following packages have unmet dependencies: Jul 31 08:54:29 in-target: libgl1-mesa-dri-lts-trusty : Conflicts: libgl1-mesa-dri Jul 31 08:54:29 in-target: libgl1-mesa-glx : Conflicts: libgl1 Jul 31 08:54:29 in-target: libgl1-mesa-glx-lts-trusty : Conflicts: libgl1 Jul 31 08:54:29 in-target: Conflicts: libgl1-mesa-glx Jul 31 08:54:29 in-target: libglapi-mesa-lts-trusty : Conflicts: libglapi-mesa Jul 31 08:54:29 in-target: xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~) Jul 31 08:54:29 in-target:Conflicts: libgl1-mesa-glx (= 0~) Jul 31 08:54:29 in-target:Conflicts: libglapi-mesa (= 0~) Jul 31 08:54:29 in-target: E Jul 31 08:54:29 in-target: : Jul 31 08:54:29 in-target: Unable to correct problems, you have held broken packages. The d-i installs based on iso were broken until 20140731 due to kernel version mismatch between the archive and d-i. Therefore it's proving very hard to find from our side when this was introduced. This issue impacts both amd64 and i386 installations and the failing preseeded install logs can be found: https://jenkins.qa.ubuntu.com/job/precise-alternate-i386_default/ https://jenkins.qa.ubuntu.com/job/precise-alternate-amd64_default/ The installer syslog is attached. The preseed being used for this install is: http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-precise/view/head:/preseeds-common/base ** Affects: xorg-lts-transitional (Ubuntu) Importance: Undecided Status: New ** Attachment added: d-i-syslog.log https://bugs.launchpad.net/bugs/1351262/+attachment/4167294/+files/d-i-syslog.log ** Package changed: xorg-lts-raring (Ubuntu) = xorg-lts-transitional (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-lts-transitional in Ubuntu. https://bugs.launchpad.net/bugs/1351262 Title: precise alternate installations fail with unmet deps due to the conflict ' xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~)' Status in “xorg-lts-transitional” package in Ubuntu: New Bug description: Precise alternate preseeded installations fail with unmet deps due to the following: Jul 31 08:54:29 in-target: The following information may help to resolve the situation: Jul 31 08:54:29 in-target: Jul 31 08:54:29 in-target: The following packages have unmet dependencies: Jul 31 08:54:29 in-target: libgl1-mesa-dri-lts-trusty : Conflicts: libgl1-mesa-dri Jul 31 08:54:29 in-target: libgl1-mesa-glx : Conflicts: libgl1 Jul 31 08:54:29 in-target: libgl1-mesa-glx-lts-trusty : Conflicts: libgl1 Jul 31 08:54:29 in-target: Conflicts: libgl1-mesa-glx Jul 31 08:54:29 in-target: libglapi-mesa-lts-trusty : Conflicts: libglapi-mesa Jul 31 08:54:29 in-target: xserver-xorg-lts-trusty : Conflicts: libgl1-mesa-dri (= 0~) Jul 31 08:54:29 in-target:Conflicts: libgl1-mesa-glx (= 0~) Jul 31 08:54:29 in-target:Conflicts: libglapi-mesa (= 0~) Jul 31 08:54:29 in-target: E Jul 31 08:54:29 in-target: : Jul 31 08:54:29 in-target: Unable to correct problems, you have held broken packages. The d-i installs based on iso were broken until 20140731 due to kernel version mismatch between the archive and d-i. Therefore it's proving very hard to find from our side when this was introduced. This issue impacts both amd64 and i386 installations and the failing preseeded install logs can be found: https://jenkins.qa.ubuntu.com/job/precise-alternate-i386_default/ https://jenkins.qa.ubuntu.com/job/precise-alternate-amd64_default/ The installer syslog is attached. The preseed being used for this install is: http://bazaar.launchpad.net/~ubuntu-server-iso-testing-dev/+junk/server-tests-precise/view/head:/preseeds-common/base To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1351262/+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 1340217] Re: [mako] wlan0 state 'unavailable' after flashing
This (or a similar issue to bug 1321627) was impacting the wifi network setup on mako devices for smoke test with image 123. When I tried the workaround suggested in https://bugs.launchpad.net/ubuntu/+source/urfkill/+bug/1321627/comments/17, the wifi became active and useable -- 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/1340217 Title: [mako] wlan0 state 'unavailable' after flashing Status in “network-manager” package in Ubuntu: Confirmed Bug description: After flashing latest image from today, I noticed that on the first boot the wlan0 device has it state reported as 'unavailable' and thus no WiFi connection is possible. urfkill verion: 0.6.0~20140708.110711.a0581f3-0ubuntu1 $ nmcli d DEVICE TYPE STATE /ril_0 gsm connected wlan0 802-11-wireless unavailable $ rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.Get string:org.freedesktop.URfkill.Killswitch string:state method return sender=:1.4 - dest=:1.122 reply_serial=2 variant int32 0 $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/WWAN org.freedesktop.DBus.Properties.Get string:org.freedesktop.URfkill.Killswitch string:state method return sender=:1.4 - dest=:1.123 reply_serial=2 variant int32 0 $ dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/BLUETOOTH org.freedesktop.DBus.Properties.Get string:org.freedesktop.URfkill.Killswitch string:state method return sender=:1.4 - dest=:1.124 reply_serial=2 variant int32 0 $ sudo system-image-cli -i current build number: 123 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-07-10 13:20:45 version version: 123 version ubuntu: 20140710 version device: 20140709 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1340217/+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 1256299] Re: NetworkManager crashed with signal 5 in g_object_finalize()
Marking this fix-released since the crash has not been reproduced after the fix in glib. Please re-open it if it's needed. ** Changed in: network-manager (Ubuntu) Status: New = Fix Released -- 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/1256299 Title: NetworkManager crashed with signal 5 in g_object_finalize() Status in “network-manager” package in Ubuntu: Fix Released Bug description: From http://q-jenkins.ubuntu-ci:8080/job/trusty-touch-mako-smoke- security/34/artifact/clientlogs/_usr_sbin_NetworkManager.0.crash/*view*/ Retraced locally. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.4-0ubuntu3 Uname: Linux 3.4.0-3-mako armv7l Architecture: armhf Date: Fri Nov 29 12:20:04 2013 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1383642404 ProcCmdline: NetworkManager ProcCwd: / ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 RetraceOutdatedPackages: outdated debug symbol package for libpolkit-gobject-1-0: package version 0.105-4ubuntu1 dbgsym version 0.105-3ubuntu3 Signal: 5 SourcePackage: network-manager StacktraceTop: g_object_finalize (object=0x11f7298) at /build/buildd/glib2.0-2.39.1/./gobject/gobject.c:1030 g_object_unref (_object=0x11f7298) at /build/buildd/glib2.0-2.39.1/./gobject/gobject.c:3173 constructor (type=optimized out, n_construct_params=optimized out, construct_params=optimized out) at nm-device.c:470 constructor (type=18820416, n_construct_params=13, construct_params=0x11979b8) at nm-device-wired.c:301 constructor (type=18820416, n_construct_params=13, construct_params=0x11979b8) at nm-device-ethernet.c:246 UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1256299/+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 1248143] Re: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases
This is the reason for maguro failures as well.. https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-maguro-smoke-gallery-app-autopilot/16/artifact/clientlogs/top_after.log/*view*/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1248143 Title: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases Status in “friends” package in Ubuntu: Confirmed Bug description: with image 11 the fix for the above bug landed. it causes the systemsettle test to fail on mako for any test where friends-service is involved. http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/ https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/ this currently causes a regression in the overall pass rate of the image builds which blocks us from releasing new touch images. please revert the change or fix it in a non-regressive way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1248143/+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 1248143] Re: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases
The issue does not occur with friends-0.2.0+13.10.20130926-0ubuntu1: https://jenkins.qa.ubuntu.com/view/Trusty/view/Smoke%20Testing/job/trusty-touch-maguro-smoke-friends-app-autopilot/14/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1248143 Title: the fix for Bug #1238083 seems to cause the systemsettle tests on mako to fail, blocking image releases Status in “friends” package in Ubuntu: Confirmed Bug description: with image 11 the fix for the above bug landed. it causes the systemsettle test to fail on mako for any test where friends-service is involved. http://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-gallery-app-autopilot/12/artifact/clientlogs/top_after.log/*view*/ https://jenkins.qa.ubuntu.com/job/trusty-touch-mako-smoke-friends-app-autopilot/13/artifact/clientlogs/top_after.log/*view*/ this currently causes a regression in the overall pass rate of the image builds which blocks us from releasing new touch images. please revert the change or fix it in a non-regressive way. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1248143/+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 1240531] [NEW] gnome-settings-daemon crashed with SIGSEGV
Public bug reported: This crash occurred soon after an oem installation of saucy desktop i386 image of 20131016. Steps: 1. Perform and oem installation 2. Reboot after the installation. 3. This crash was reported soon after the reboot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Oct 16 14:53:23 2013 Disassembly: = 0xb6f10040: Cannot access memory at address 0xb6f10040 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1381919282 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /var/lib/lightdm ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0xb6f10040: Cannot access memory at address 0xb6f10040 PC (0xb6f10040) ok SP (0xbfd5d070) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0xb6f10040 in ?? () No symbol table info available. StacktraceTop: ?? () Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace rls-s-incoming saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1240531 Title: gnome-settings-daemon crashed with SIGSEGV Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: This crash occurred soon after an oem installation of saucy desktop i386 image of 20131016. Steps: 1. Perform and oem installation 2. Reboot after the installation. 3. This crash was reported soon after the reboot. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gnome-settings-daemon 3.8.5-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2 Architecture: i386 Date: Wed Oct 16 14:53:23 2013 Disassembly: = 0xb6f10040: Cannot access memory at address 0xb6f10040 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ExecutableTimestamp: 1381919282 InstallationDate: Installed on 2013-10-16 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016) MarkForUpload: True ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcCwd: /var/lib/lightdm ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0xb6f10040:Cannot access memory at address 0xb6f10040 PC (0xb6f10040) ok SP (0xbfd5d070) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0xb6f10040 in ?? () No symbol table info available. StacktraceTop: ?? () Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1240531/+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 1206860] [NEW] xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images
Public bug reported: The precise alternate installations of i386 and amd64 have the following installation error reported. Probably a known issue since report.html lists this package as uninstallable. Bug is required to account the smoke test failure. Install error: = Jul 31 09:00:15 in-target: The following packages have unmet dependencies: Jul 31 09:00:15 in-target: xserver-xorg-input-all-lts-raring : Depends: xserver-xorg-input-wacom-lts-raring but it is not installable Jul 31 09:00:15 in-target: E Jul 31 09:00:15 in-target: : Jul 31 09:00:15 in-target: Unable to correct problems, you have held broken packages. Jul 31 09:00:15 in-target: ... ... Jul 31 09:00:15 main-menu[1738]: WARNING **: Configuring 'pkgsel' failed with error code 1 Jul 31 09:00:15 debconf: -- GET debconf/priority Jul 31 09:00:15 debconf: -- 0 critical Jul 31 09:00:15 main-menu[1738]: WARNING **: Menu item 'pkgsel' failed. Jul 31 09:00:15 debconf: -- SETTITLE debian-installer/pkgsel/title Jul 31 09:00:15 debconf: -- 0 OK Jul 31 09:00:15 debconf: -- CAPB Jul 31 09:00:15 debconf: -- 0 multiselect backup progresscancel align plugin-detect-keyboard plugin-terminal Jul 31 09:00:15 debconf: -- METAGET debian-installer/pkgsel/title Description Jul 31 09:00:15 debconf: -- 0 Select and install software Jul 31 09:00:15 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Select and install software Jul 31 09:00:15 debconf: Adding [ITEM] - [Select and install software] Jul 31 09:00:15 debconf: -- 0 Jul 31 09:00:15 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jul 31 09:00:15 debconf: -- 0 question will be asked Jul 31 09:00:15 debconf: -- GO report.html: == (http://cdimage.ubuntu.com/precise/daily/pending/report.html) xorg-lts-raring 1:7.7+1ubuntu4~precise1 produces uninstallable binaries: xserver-xorg-input-all-lts-raring (amd64 i386) The impacted smoke jobs: == https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-amd64_default/902/console and https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-i386_default/888/console An d-i syslog is attached. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing qa-daily-testing ** Attachment added: d-i syslog.log https://bugs.launchpad.net/bugs/1206860/+attachment/3755815/+files/d-i%20syslog.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1206860 Title: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images Status in “xorg-server” package in Ubuntu: New Bug description: The precise alternate installations of i386 and amd64 have the following installation error reported. Probably a known issue since report.html lists this package as uninstallable. Bug is required to account the smoke test failure. Install error: = Jul 31 09:00:15 in-target: The following packages have unmet dependencies: Jul 31 09:00:15 in-target: xserver-xorg-input-all-lts-raring : Depends: xserver-xorg-input-wacom-lts-raring but it is not installable Jul 31 09:00:15 in-target: E Jul 31 09:00:15 in-target: : Jul 31 09:00:15 in-target: Unable to correct problems, you have held broken packages. Jul 31 09:00:15 in-target: ... ... Jul 31 09:00:15 main-menu[1738]: WARNING **: Configuring 'pkgsel' failed with error code 1 Jul 31 09:00:15 debconf: -- GET debconf/priority Jul 31 09:00:15 debconf: -- 0 critical Jul 31 09:00:15 main-menu[1738]: WARNING **: Menu item 'pkgsel' failed. Jul 31 09:00:15 debconf: -- SETTITLE debian-installer/pkgsel/title Jul 31 09:00:15 debconf: -- 0 OK Jul 31 09:00:15 debconf: -- CAPB Jul 31 09:00:15 debconf: -- 0 multiselect backup progresscancel align plugin-detect-keyboard plugin-terminal Jul 31 09:00:15 debconf: -- METAGET debian-installer/pkgsel/title Description Jul 31 09:00:15 debconf: -- 0 Select and install software Jul 31 09:00:15 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Select and install software Jul 31 09:00:15 debconf: Adding [ITEM] - [Select and install software] Jul 31 09:00:15 debconf: -- 0 Jul 31 09:00:15 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jul 31 09:00:15 debconf: -- 0 question will be asked Jul 31 09:00:15 debconf: -- GO report.html: == (http://cdimage.ubuntu.com/precise/daily/pending/report.html) xorg-lts-raring 1:7.7+1ubuntu4~precise1 produces uninstallable binaries: xserver-xorg-input-all-lts-raring (amd64 i386) The impacted smoke jobs: ==
[Desktop-packages] [Bug 1206860] Re: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images
** Description changed: The precise alternate installations of i386 and amd64 have the - following installation error reported. Probably a known issue since - report.html lists this package as uninstallable. Bug is required to - account the smoke test failure. + following installation error reported with today's images (20130731). + Probably a known issue since report.html lists this package as + uninstallable. Bug is required to account the smoke test failure. + + Steps to reproduce: + 1. Install precise alternate image of 20130731. + 2. Leave the default selections and continue the installations + 3. The error will be seen towards the end of the installation. + Install error: = Jul 31 09:00:15 in-target: The following packages have unmet dependencies: Jul 31 09:00:15 in-target: xserver-xorg-input-all-lts-raring : Depends: xserver-xorg-input-wacom-lts-raring but it is not installable Jul 31 09:00:15 in-target: E - Jul 31 09:00:15 in-target: : + Jul 31 09:00:15 in-target: : Jul 31 09:00:15 in-target: Unable to correct problems, you have held broken packages. - Jul 31 09:00:15 in-target: + Jul 31 09:00:15 in-target: ... ... Jul 31 09:00:15 main-menu[1738]: WARNING **: Configuring 'pkgsel' failed with error code 1 Jul 31 09:00:15 debconf: -- GET debconf/priority Jul 31 09:00:15 debconf: -- 0 critical Jul 31 09:00:15 main-menu[1738]: WARNING **: Menu item 'pkgsel' failed. Jul 31 09:00:15 debconf: -- SETTITLE debian-installer/pkgsel/title Jul 31 09:00:15 debconf: -- 0 OK Jul 31 09:00:15 debconf: -- CAPB Jul 31 09:00:15 debconf: -- 0 multiselect backup progresscancel align plugin-detect-keyboard plugin-terminal Jul 31 09:00:15 debconf: -- METAGET debian-installer/pkgsel/title Description Jul 31 09:00:15 debconf: -- 0 Select and install software Jul 31 09:00:15 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Select and install software Jul 31 09:00:15 debconf: Adding [ITEM] - [Select and install software] Jul 31 09:00:15 debconf: -- 0 Jul 31 09:00:15 debconf: -- INPUT critical debian-installer/main-menu/item-failure Jul 31 09:00:15 debconf: -- 0 question will be asked Jul 31 09:00:15 debconf: -- GO report.html: == (http://cdimage.ubuntu.com/precise/daily/pending/report.html) xorg-lts-raring 1:7.7+1ubuntu4~precise1 produces uninstallable binaries: - xserver-xorg-input-all-lts-raring (amd64 i386) + xserver-xorg-input-all-lts-raring (amd64 i386) The impacted smoke jobs: == https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-amd64_default/902/console and https://jenkins.qa.ubuntu.com/view/Precise/view/ISO%20Testing%20Dashboard/job/precise-alternate-i386_default/888/console An d-i syslog is attached. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1206860 Title: xserver-xorg-input-all-lts-raring are unintstallable with precise alternate images Status in “xorg-server” package in Ubuntu: New Bug description: The precise alternate installations of i386 and amd64 have the following installation error reported with today's images (20130731). Probably a known issue since report.html lists this package as uninstallable. Bug is required to account the smoke test failure. Steps to reproduce: 1. Install precise alternate image of 20130731. 2. Leave the default selections and continue the installations 3. The error will be seen towards the end of the installation. Install error: = Jul 31 09:00:15 in-target: The following packages have unmet dependencies: Jul 31 09:00:15 in-target: xserver-xorg-input-all-lts-raring : Depends: xserver-xorg-input-wacom-lts-raring but it is not installable Jul 31 09:00:15 in-target: E Jul 31 09:00:15 in-target: : Jul 31 09:00:15 in-target: Unable to correct problems, you have held broken packages. Jul 31 09:00:15 in-target: ... ... Jul 31 09:00:15 main-menu[1738]: WARNING **: Configuring 'pkgsel' failed with error code 1 Jul 31 09:00:15 debconf: -- GET debconf/priority Jul 31 09:00:15 debconf: -- 0 critical Jul 31 09:00:15 main-menu[1738]: WARNING **: Menu item 'pkgsel' failed. Jul 31 09:00:15 debconf: -- SETTITLE debian-installer/pkgsel/title Jul 31 09:00:15 debconf: -- 0 OK Jul 31 09:00:15 debconf: -- CAPB Jul 31 09:00:15 debconf: -- 0 multiselect backup progresscancel align plugin-detect-keyboard plugin-terminal Jul 31 09:00:15 debconf: -- METAGET debian-installer/pkgsel/title Description Jul 31 09:00:15 debconf: -- 0 Select and install software Jul 31 09:00:15 debconf: -- SUBST debian-installer/main-menu/item-failure ITEM Select and
[Desktop-packages] [Bug 1202634] [NEW] evince crashed with SIGABRT in raise()
Public bug reported: Description later ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evince 3.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 18 11:09:08 2013 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-07-18 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130718) MarkForUpload: True ProcAttrCurrent: /usr/bin/evince (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=ce5ddb64-d8db-4bae-a571-f2dce752d188 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: evince StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evince crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-crash need-amd64-retrace saucy ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1202634 Title: evince crashed with SIGABRT in raise() Status in “evince” package in Ubuntu: New Bug description: Description later ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evince 3.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 18 11:09:08 2013 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-07-18 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130718) MarkForUpload: True ProcAttrCurrent: /usr/bin/evince (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=ce5ddb64-d8db-4bae-a571-f2dce752d188 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: evince StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evince crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1202634/+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 1202634] Re: evince crashed with SIGABRT in raise()
** Description changed: - Description later + This crash occurs when running the autopilot tests using utah. + Attempting to find an easy way to reproduce. The information will be + added later. + + ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evince 3.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 18 11:09:08 2013 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-07-18 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130718) MarkForUpload: True ProcAttrCurrent: /usr/bin/evince (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=ce5ddb64-d8db-4bae-a571-f2dce752d188 ro quiet splash vt.handoff=7 ProcEnviron: - LANGUAGE=en_US - TERM=unknown - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US + TERM=unknown + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash Signal: 6 SourcePackage: evince StacktraceTop: - raise () from /lib/x86_64-linux-gnu/libc.so.6 - abort () from /lib/x86_64-linux-gnu/libc.so.6 - ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + raise () from /lib/x86_64-linux-gnu/libc.so.6 + abort () from /lib/x86_64-linux-gnu/libc.so.6 + ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evince crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1202634 Title: evince crashed with SIGABRT in raise() Status in “evince” package in Ubuntu: New Bug description: This crash occurs when running the autopilot tests using utah. Attempting to find an easy way to reproduce. The information will be added later. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evince 3.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 18 11:09:08 2013 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-07-18 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130718) MarkForUpload: True ProcAttrCurrent: /usr/bin/evince (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=ce5ddb64-d8db-4bae-a571-f2dce752d188 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: evince StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evince crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1202634/+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 1202634] Re: evince crashed with SIGABRT in raise()
** Description changed: - This crash occurs when running the autopilot tests using utah. - Attempting to find an easy way to reproduce. The information will be - added later. + This crash occurs when running the autopilot tests using an ssh + connection. + + == + How to reproduce: + 1. Install utah using +sudo apt-add-repository -y ppa:utah/stable +sudo apt-get update +sudo apt-get install utah + + 2. sudo -u utah -i UTAH_FEATURE_PROVISIONED_AUTORUN=1 run_utah_tests.py + -i /path/to/saucy-desktop-amd64.iso -p lp:~psivaa/ubuntu-test- + cases/autopilot/preseeds/autopilot.cfg lp:~psivaa/ubuntu-test- + cases/autopilot/runlists/autopilot.run -x /etc/utah/bridged-network- + vm.xml + 3. Now it could be seen that the the connection to the VMs from the host after the installation fails. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evince 3.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 18 11:09:08 2013 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-07-18 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130718) MarkForUpload: True ProcAttrCurrent: /usr/bin/evince (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=ce5ddb64-d8db-4bae-a571-f2dce752d188 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: evince StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evince crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1202634 Title: evince crashed with SIGABRT in raise() Status in “evince” package in Ubuntu: New Bug description: This crash occurs when running the autopilot tests using an ssh connection. == How to reproduce: 1. Install utah using sudo apt-add-repository -y ppa:utah/stable sudo apt-get update sudo apt-get install utah 2. sudo -u utah -i UTAH_FEATURE_PROVISIONED_AUTORUN=1 run_utah_tests.py -i /path/to/saucy-desktop-amd64.iso -p lp:~psivaa /ubuntu-test-cases/autopilot/preseeds/autopilot.cfg lp:~psivaa/ubuntu- test-cases/autopilot/runlists/autopilot.run -x /etc/utah/bridged- network-vm.xml 3. Now it could be seen that the the connection to the VMs from the host after the installation fails. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: evince 3.8.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic x86_64 ApportVersion: 2.11-0ubuntu1 Architecture: amd64 Date: Thu Jul 18 11:09:08 2013 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2013-07-18 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Alpha amd64 (20130718) MarkForUpload: True ProcAttrCurrent: /usr/bin/evince (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.10.0-3-generic root=UUID=ce5ddb64-d8db-4bae-a571-f2dce752d188 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_US TERM=unknown PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: evince StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: evince crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1202634/+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 1160441] Re: Calendar is still in English despite French is selected as the Language during the installation
locale returns the following ubuntu@ubuntu-Inspiron-N4010:~$ locale LANG=fr_FR.UTF-8 LANGUAGE= LC_CTYPE=fr_FR.UTF-8 LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=fr_FR.UTF-8 LC_MONETARY=en_GB.UTF-8 LC_MESSAGES=fr_FR.UTF-8 LC_PAPER=en_GB.UTF-8 LC_NAME=en_GB.UTF-8 LC_ADDRESS=en_GB.UTF-8 LC_TELEPHONE=en_GB.UTF-8 LC_MEASUREMENT=en_GB.UTF-8 LC_IDENTIFICATION=en_GB.UTF-8 LC_ALL= The issue that I reported in this bug is that even though the locale is French, the calendar entries are in English ( the location that I selected during the installation was London). Screen_1.jpg shows the exact thing that I think as a regression. We used to have the calendar entries localised in the language selected up-until the images that contained ubiquity (2.13.11) or earlier. It may not be a regression in ubiquity but the behaviour changed after 2.13.12 onwards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1160441 Title: Calendar is still in English despite French is selected as the Language during the installation Status in The Date and Time Indicator: In Progress Status in “evolution” package in Ubuntu: In Progress Status in “evolution-data-server” package in Ubuntu: In Progress Status in “localechooser” package in Ubuntu: Triaged Status in “ubiquity” package in Ubuntu: Triaged Status in “evolution” source package in Raring: In Progress Status in “evolution-data-server” source package in Raring: In Progress Status in “localechooser” source package in Raring: Won't Fix Status in “ubiquity” source package in Raring: Won't Fix Bug description: When London is selected as the location and language is selected as French, the calendar entries are shown in English. The calendar shows correct London date and time but presents them in English. One would expect that the calendar entries would be shown in French as it used to be the case. This occurs in installations with and without network, with and without live session and on both amd64 and i386 of 20130326 images. When Paris is selected as the location, the calendar entries are shown in French. Incomplete language support dialog pops up (for networkless installations) after the reboot but updating the language does not solve the issue. Steps to reproduce: 1. Boot the usb with todays image (20130326) 2. Select French language for installation 3. Continue with default settings except the location setting, which should be set to London 4. Finish the installation and reboot. 5. Check the calendar entries ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.13.17 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic i686 ApportVersion: 2.9.2-0ubuntu4 Architecture: i386 CasperVersion: 1.330 Date: Tue Mar 26 15:20:47 2013 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130326) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1160441/+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 1160441] Re: Calendar is still in English despite French is selected as the Language during the installation
I can confirm again that the ppa does not fix the issue that I reported. i.e. even after installing the ppa and rebooting, the calendar entries were still in English. Here follows the package installed ubuntu@ubuntu-Inspiron-N4010:~$ dpkg -l | grep indicator-datetime ii indicator-datetime 12.10.3daily13.03.26-0ubuntu1+daysMonths amd64Simple clock And as Brian confirmed in comment #11 that changing the Regional Formats section of Language Support to francais (France) solved the issue ( that is even before installing the above ppa ) :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1160441 Title: Calendar is still in English despite French is selected as the Language during the installation Status in The Date and Time Indicator: In Progress Status in “evolution” package in Ubuntu: In Progress Status in “evolution-data-server” package in Ubuntu: In Progress Status in “localechooser” package in Ubuntu: Triaged Status in “ubiquity” package in Ubuntu: Triaged Status in “evolution” source package in Raring: In Progress Status in “evolution-data-server” source package in Raring: In Progress Status in “localechooser” source package in Raring: Won't Fix Status in “ubiquity” source package in Raring: Won't Fix Bug description: When London is selected as the location and language is selected as French, the calendar entries are shown in English. The calendar shows correct London date and time but presents them in English. One would expect that the calendar entries would be shown in French as it used to be the case. This occurs in installations with and without network, with and without live session and on both amd64 and i386 of 20130326 images. When Paris is selected as the location, the calendar entries are shown in French. Incomplete language support dialog pops up (for networkless installations) after the reboot but updating the language does not solve the issue. Steps to reproduce: 1. Boot the usb with todays image (20130326) 2. Select French language for installation 3. Continue with default settings except the location setting, which should be set to London 4. Finish the installation and reboot. 5. Check the calendar entries ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.13.17 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic i686 ApportVersion: 2.9.2-0ubuntu4 Architecture: i386 CasperVersion: 1.330 Date: Tue Mar 26 15:20:47 2013 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130326) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1160441/+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 1160441] Re: Calendar is still in English despite French is selected as the Language during the installation
@gunnarhj: Yes, The calendar that I refer in this bug report is the one that shows up when I click the time indicator at the top right corner of the screen. Please see attachment 7 (Screen_1). Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1160441 Title: Calendar is still in English despite French is selected as the Language during the installation Status in “evolution” package in Ubuntu: In Progress Status in “evolution-data-server” package in Ubuntu: In Progress Status in “localechooser” package in Ubuntu: Triaged Status in “ubiquity” package in Ubuntu: Triaged Status in “evolution” source package in Raring: In Progress Status in “evolution-data-server” source package in Raring: In Progress Status in “localechooser” source package in Raring: Won't Fix Status in “ubiquity” source package in Raring: Won't Fix Bug description: When London is selected as the location and language is selected as French, the calendar entries are shown in English. The calendar shows correct London date and time but presents them in English. One would expect that the calendar entries would be shown in French as it used to be the case. This occurs in installations with and without network, with and without live session and on both amd64 and i386 of 20130326 images. When Paris is selected as the location, the calendar entries are shown in French. Incomplete language support dialog pops up (for networkless installations) after the reboot but updating the language does not solve the issue. Steps to reproduce: 1. Boot the usb with todays image (20130326) 2. Select French language for installation 3. Continue with default settings except the location setting, which should be set to London 4. Finish the installation and reboot. 5. Check the calendar entries ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: ubiquity 2.13.17 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic i686 ApportVersion: 2.9.2-0ubuntu4 Architecture: i386 CasperVersion: 1.330 Date: Tue Mar 26 15:20:47 2013 LiveMediaBuild: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20130326) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1160441/+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 1133471] [NEW] colord-sane crashed with SIGSEGV in libusb_get_device_list() during quantal to raring upgrade
Public bug reported: This crash occurred during quantal to raring desktop auto-upgrades amd64. The crash occurred only once and the consecutive run has passed. A manual upgrade of an updated quantal desktop installation to raring did not produce this crash either. The testing was done in an automated way and here are the major steps involved. 1. Create a quantal base image using ubuntu-vm-builder and bootstrap it to get the ubuntu standard desktop packages 2. Use do-release-upgrade to perform the upgrade. The impacted job is, https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-upgrade-quantal-desktop/123/ARCH=amd64,LTS=non-lts,PROFILE=desktop,label=upgrade-test/ ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: colord 0.1.23-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 26 00:22:39 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord-sane MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord-sane ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f55512c0d60: cmpb $0x0,(%rsi) PC (0x7f55512c0d60) ok source $0x0 ok destination (%rsi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 hpmud_probe_devices () from /usr/lib/libhpmud.so.0 Title: colord-sane crashed with SIGSEGV in libusb_get_device_list() UpgradeStatus: Upgraded to raring on 2013-02-25 (0 days ago) UserGroups: ** Affects: colord (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash dist-upgrade need-amd64-retrace qa-daily-testing raring ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1133471 Title: colord-sane crashed with SIGSEGV in libusb_get_device_list() during quantal to raring upgrade Status in “colord” package in Ubuntu: New Bug description: This crash occurred during quantal to raring desktop auto-upgrades amd64. The crash occurred only once and the consecutive run has passed. A manual upgrade of an updated quantal desktop installation to raring did not produce this crash either. The testing was done in an automated way and here are the major steps involved. 1. Create a quantal base image using ubuntu-vm-builder and bootstrap it to get the ubuntu standard desktop packages 2. Use do-release-upgrade to perform the upgrade. The impacted job is, https://jenkins.qa.ubuntu.com/view/Raring/view/Smoke%20Testing/job/raring-upgrade-quantal-desktop/123/ARCH=amd64,LTS=non-lts,PROFILE=desktop,label=upgrade-test/ ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: colord 0.1.23-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Tue Feb 26 00:22:39 2013 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord-sane MarkForUpload: True ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord-sane ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f55512c0d60:cmpb $0x0,(%rsi) PC (0x7f55512c0d60) ok source $0x0 ok destination (%rsi) (0x) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: colord StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 hpmud_probe_devices () from /usr/lib/libhpmud.so.0 Title: colord-sane crashed with SIGSEGV in libusb_get_device_list() UpgradeStatus: Upgraded to raring on 2013-02-25 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1133471/+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 1122072] Re: [Precise amd64 on VirtualBox] Fatal server error: no screen found in Xorg.0.log
Confirmed with ubuntu-desktop-amd64 and ubuntu-desktop-i386 when using VirtualBox. Did not see this issue on virt-manager using KVM and on hardware. -- 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/1122072 Title: [Precise amd64 on VirtualBox] Fatal server error: no screen found in Xorg.0.log Status in “xorg” package in Ubuntu: Confirmed Bug description: Hello! I have tested Edubuntu amd64 (5d76226ca924f5c5b4e683c4ac177a6b *precise-dvd-amd64.iso 20130210), on VirtualBox. 1) I have started the system. 2) I have chosen the language. 3) I have clicked on Try Edubuntu ... 4) This system is started no graphics. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CasperVersion: 1.315.1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Feb 11 12:04:20 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu ExtraDebuggingInterest: Yes, GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Edubuntu 12.04.2 LTS Precise Pangolin - Release amd64 (20130210) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Feb 11 12:28:13 2013 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputSleep Button KEYBOARD, id 7 inputVirtualBox USB Tablet TOUCHSCREEN, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImExPS/2 Generic Explorer Mouse MOUSE, id 10 xserver.errors: Failed to load module vboxvideo (module does not exist, 0) Failed to load module vboxvideo (module does not exist, 0) open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.2-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1122072/+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 1119569] [NEW] jockey-gtk crashed with DBusException in call_blocking()
Public bug reported: The attached crash occurred when the display resolution was changed soon after the installation of 20130208 precise desktop amd64+mac image on a Mac min 5.1 The following are the steps involved. 1. Install precise desktop amd64+mac 20130208 as given in http://testcases.qa.ubuntu.com/Install/DesktopWhole but with no network support 2. Reboot and login afther the installation 3. Change the display resolution ( in the display that is used for this testing the change was from 1280x720 to 1366 x 768 4. The crash could be observed at this point. (The amd64 image and i386 image onother hardwares did NOT have this issue) The crash file is attached (ubuntu-bug /var/crash/crashfile does not report this as a bug) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-gtk 0.9.7-0ubuntu7.7 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 8 16:35:14 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64+mac (20130208) MachineType: Apple Inc. Macmini5,1 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=8a6f023d-150e-40c0-815f-8eca7bdf91ba ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: jockey (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug iso-testing precise qa-daily-testing running-unity ** Attachment added: _usr_bin_jockey-gtk.1000.crash https://bugs.launchpad.net/bugs/1119569/+attachment/3520928/+files/_usr_bin_jockey-gtk.1000.crash -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1119569 Title: jockey-gtk crashed with DBusException in call_blocking() Status in “jockey” package in Ubuntu: New Bug description: The attached crash occurred when the display resolution was changed soon after the installation of 20130208 precise desktop amd64+mac image on a Mac min 5.1 The following are the steps involved. 1. Install precise desktop amd64+mac 20130208 as given in http://testcases.qa.ubuntu.com/Install/DesktopWhole but with no network support 2. Reboot and login afther the installation 3. Change the display resolution ( in the display that is used for this testing the change was from 1280x720 to 1366 x 768 4. The crash could be observed at this point. (The amd64 image and i386 image onother hardwares did NOT have this issue) The crash file is attached (ubuntu-bug /var/crash/crashfile does not report this as a bug) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-gtk 0.9.7-0ubuntu7.7 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 8 16:35:14 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64+mac (20130208) MachineType: Apple Inc. Macmini5,1 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=8a6f023d-150e-40c0-815f-8eca7bdf91ba ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1119569] Re: jockey-gtk crashed with DBusException in call_blocking()
** Description changed: The attached crash occurred when the display resolution was changed soon after the installation of 20130208 precise desktop amd64+mac image on a Mac min 5.1 The following are the steps involved. 1. Install precise desktop amd64+mac 20130208 as given in http://testcases.qa.ubuntu.com/Install/DesktopWhole but with no network support 2. Reboot and login afther the installation 3. Change the display resolution ( in the display that is used for this testing the change was from 1280x720 to 1366 x 768 - 4. The crash could be observed at this point. + 4. The crash could be observed at this point and it can be reliably reproduced. (The amd64 image and i386 image onother hardwares did NOT have this issue) The crash file is attached (ubuntu-bug /var/crash/crashfile does not report this as a bug) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-gtk 0.9.7-0ubuntu7.7 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 8 16:35:14 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64+mac (20130208) MachineType: Apple Inc. Macmini5,1 MarkForUpload: True PackageArchitecture: all ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=8a6f023d-150e-40c0-815f-8eca7bdf91ba ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jockey in Ubuntu. https://bugs.launchpad.net/bugs/1119569 Title: jockey-gtk crashed with DBusException in call_blocking() Status in “jockey” package in Ubuntu: New Bug description: The attached crash occurred when the display resolution was changed soon after the installation of 20130208 precise desktop amd64+mac image on a Mac min 5.1 The following are the steps involved. 1. Install precise desktop amd64+mac 20130208 as given in http://testcases.qa.ubuntu.com/Install/DesktopWhole but with no network support 2. Reboot and login afther the installation 3. Change the display resolution ( in the display that is used for this testing the change was from 1280x720 to 1366 x 768 4. The crash could be observed at this point and it can be reliably reproduced. (The amd64 image and i386 image onother hardwares did NOT have this issue) The crash file is attached (ubuntu-bug /var/crash/crashfile does not report this as a bug) ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: jockey-gtk 0.9.7-0ubuntu7.7 ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Feb 8 16:35:14 2013 InstallationMedia: Ubuntu 12.04.2 LTS Precise Pangolin - Release amd64+mac (20130208) MachineType: Apple Inc. Macmini5,1 MarkForUpload: True PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=8a6f023d-150e-40c0-815f-8eca7bdf91ba ro quiet splash vt.handoff=7 SourcePackage: jockey UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1105102] Re: dconf-service crashed with SIGSEGV in g_variant_builder_add_value()
The latest traces are attached from an installation with 20130129 ** Attachment added: Stacktrace.txt https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+attachment/3505562/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1105102 Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value() Status in Ubuntu on the Nexus 7: New Status in “glib2.0” package in Ubuntu: Confirmed Bug description: Occured after the raring desktop amd64 installation on 20130125 on a VM based on qemu-kvm usign virt-manager 1. Boot a VM to raring desktop amd64 live session with the image of 20130125 2. Start the installer from the live session 3. Perform manual partition (with 3 ext4 partitions and a swap) 4. Reboot after the installation 5. This crash was observed after the first reboot ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: dconf-service 0.15.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Fri Jan 25 13:57:33 2013 ExecutablePath: /usr/lib/dconf/dconf-service InstallationDate: Installed on 2013-01-25 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) MarkForUpload: True ProcCmdline: /usr/lib/dconf/dconf-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fdfa0181520:mov0x20(%rdi),%eax PC (0x7fdfa0181520) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: d-conf StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1105102/+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 1105102] Re: dconf-service crashed with SIGSEGV in g_variant_builder_add_value()
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+attachment/3505564/+files/ThreadStacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1105102 Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value() Status in Ubuntu on the Nexus 7: New Status in “glib2.0” package in Ubuntu: Confirmed Bug description: Occured after the raring desktop amd64 installation on 20130125 on a VM based on qemu-kvm usign virt-manager 1. Boot a VM to raring desktop amd64 live session with the image of 20130125 2. Start the installer from the live session 3. Perform manual partition (with 3 ext4 partitions and a swap) 4. Reboot after the installation 5. This crash was observed after the first reboot ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: dconf-service 0.15.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Fri Jan 25 13:57:33 2013 ExecutablePath: /usr/lib/dconf/dconf-service InstallationDate: Installed on 2013-01-25 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) MarkForUpload: True ProcCmdline: /usr/lib/dconf/dconf-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fdfa0181520:mov0x20(%rdi),%eax PC (0x7fdfa0181520) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: d-conf StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-nexus7/+bug/1105102/+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 1105102] Re: dconf-service crashed with SIGSEGV in g_variant_builder_add_value()
The crash is occurring in a live system even where the installed version on libglib2.0-bin is 2.35.4-0ubuntu5. This was observed on 20130128 raring desktop images. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1105102 Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value() Status in “glib2.0” package in Ubuntu: Confirmed Bug description: Occured after the raring desktop amd64 installation on 20130125 on a VM based on qemu-kvm usign virt-manager 1. Boot a VM to raring desktop amd64 live session with the image of 20130125 2. Start the installer from the live session 3. Perform manual partition (with 3 ext4 partitions and a swap) 4. Reboot after the installation 5. This crash was observed after the first reboot ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: dconf-service 0.15.2-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Fri Jan 25 13:57:33 2013 ExecutablePath: /usr/lib/dconf/dconf-service InstallationDate: Installed on 2013-01-25 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130125) MarkForUpload: True ProcCmdline: /usr/lib/dconf/dconf-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SegvAnalysis: Segfault happened at: 0x7fdfa0181520:mov0x20(%rdi),%eax PC (0x7fdfa0181520) ok source 0x20(%rdi) (0x0020) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: d-conf StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_builder_add_value () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new_va () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_variant_new () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: dconf-service crashed with SIGSEGV in g_variant_builder_add_value() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1105102/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
** Attachment added: with-1-1-5-2.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/3482830/+files/with-1-1-5-2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. Status in Cairo Graphics Library: Confirmed Status in “cairo” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “xserver-xorg-video-cirrus” package in Ubuntu: Confirmed Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox.
xserver-xorg-video-cirrus 1:1.5.2-0ubuntu1 has NOT fixed the issue. Please see the screenshot attached above. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics). Affects KVM but not VBox. Status in Cairo Graphics Library: Confirmed Status in “cairo” package in Ubuntu: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “xserver-xorg-video-cirrus” package in Ubuntu: Confirmed Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1080674/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)
This only occurs with with KVM and not with VBox. The installation of 20121210 on VBox came up with correct desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics) Status in “linux” package in Ubuntu: Invalid Status in “xserver-xorg-video-cirrus” package in Ubuntu: Confirmed Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+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 1084064] Re: Can not ssh to raring VM's using hostname
OK, here's what I have found lately, To the VM's created using an old image raring-desktop-i386 -20121108.2 i386 (using libvirt on quantal host) I can ssh fromt he same host using ssh ubuntu@ubuntu-virtual-machine But to the VM's crated using the latest images -20121129 ( using the same method as the old VM was created) I can not ssh using the same command but instead i need to add a .local at the end of the host name i.e. in the new VMs ssh ubuntu@ubuntu-virtual-machine does NOT work but instead ssh ubuntu@ubuntu-virtual-machine.local DOES work NB: openssh-server was installed on the VMs soon after the installation of VMs -- 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/1084064 Title: Can not ssh to raring VM's using hostname Status in “network-manager” package in Ubuntu: Confirmed Bug description: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop vm using libvirt on a precise or quantal host (20121128-amd64) 2. Install openssh-server on the vm 3. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084064/+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 1084064] [NEW] hostname of raring desktop vm does not match the entries in /etc/hostname /etc/hosts
Public bug reported: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop (20121128-amd64) 2. Install openssh-server 3. Get the hostname using hostname -A ( this returns the actual-host-name.domain-name) 4. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug iso-testing qa-daily-testing qa-manual-testing raring running-unity ** Summary changed: - hostname of raring desktop vm does not match the entries /etc/hostname /etc/hosts + hostname of raring desktop vm does not match the entries in /etc/hostname /etc/hosts -- 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/1084064 Title: hostname of raring desktop vm does not match the entries in /etc/hostname /etc/hosts Status in “network-manager” package in Ubuntu: New Bug description: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop (20121128-amd64) 2. Install openssh-server 3. Get the hostname using hostname -A ( this returns the actual-host-name.domain-name) 4. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE
[Desktop-packages] [Bug 1084064] Re: hostname of raring desktop vm does not match the entries in /etc/hostname /etc/hosts
Logs related to avahi-daemon using the host name with (.local) domain name is attached ubuntu@ubuntu2-virtual-machine:/var/log$ cat syslog | grep '\.local' Nov 28 12:37:36 ubuntu2-virtual-machine avahi-daemon[643]: Server startup complete. Host name is ubuntu2-virtual-machine.local. Local service cookie is 4005645905. ** Attachment added: syslog https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084064/+attachment/3445997/+files/syslog -- 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/1084064 Title: hostname of raring desktop vm does not match the entries in /etc/hostname /etc/hosts Status in “network-manager” package in Ubuntu: New Bug description: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop (20121128-amd64) 2. Install openssh-server 3. Get the hostname using hostname -A ( this returns the actual-host-name.domain-name) 4. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084064/+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 1084064] Re: Can not ssh to raring VM's using hostname
** Summary changed: - hostname of raring desktop vm does not match the entries in /etc/hostname /etc/hosts + Can not ssh to raring VM's using hostname -- 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/1084064 Title: Can not ssh to raring VM's using hostname Status in “network-manager” package in Ubuntu: Confirmed Bug description: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop (20121128-amd64) 2. Install openssh-server 3. Get the hostname using hostname -A ( this returns the actual-host-name.domain-name) 4. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084064/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)
@bryce: Booting with quantal kernel does not work around the problem. The desktop is still corrupted. Please see attached image ** Attachment added: with_quantal_kernel.png https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+attachment/3446108/+files/with_quantal_kernel.png ** Changed in: linux (Ubuntu) Status: Incomplete = New ** Changed in: xserver-xorg-video-cirrus (Ubuntu) Status: Incomplete = New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-cirrus in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics) Status in “linux” package in Ubuntu: New Status in “xserver-xorg-video-cirrus” package in Ubuntu: New Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1080674/+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 1084064] Re: Can not ssh to raring VM's using hostname
** Description changed: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. - 1. Install raring desktop (20121128-amd64) - 2. Install openssh-server - 3. Get the hostname using hostname -A ( this returns the actual-host-name.domain-name) - 4. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) + 1. Install raring desktop vm using libvirt on a precise or quantal host (20121128-amd64) + 2. Install openssh-server on the vm + 3. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: - default via 192.168.122.1 dev eth0 proto static - 169.254.0.0/16 dev eth0 scope link metric 1000 - 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 + default via 192.168.122.1 dev eth0 proto static + 169.254.0.0/16 dev eth0 scope link metric 1000 + 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: - eth0 no wireless extensions. - - lono wireless extensions. + eth0 no wireless extensions. + + lono wireless extensions. MarkForUpload: True NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true - WimaxEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true + WimaxEnabled=true RfKill: - + SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH - Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 + NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH + Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: - DEVICE TYPE STATE DBUS-PATH - eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 + DEVICE TYPE STATE DBUS-PATH + eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: - RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN - running 0.9.7.0connected enabled enabled enabledenabled disabled + RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN + running 0.9.7.0connected enabled enabled enabledenabled disabled -- 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/1084064 Title: Can not ssh to raring VM's using hostname Status in “network-manager” package in Ubuntu: Incomplete Bug description: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop vm using libvirt on a precise or quantal host (20121128-amd64) 2. Install openssh-server on the vm 3. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
[Desktop-packages] [Bug 1084064] Re: Can not ssh to raring VM's using hostname
What I am trying to do is to ssh to VMs installed using libvirt from precise/ quantal hosts. I have updated the steps to be clearer. I am able to ssh to a VM with 20121108.2 i386 raring image installed using libvirt without any issues . 'ssh ubuntu@ubuntu-virtual-machine' connects fine to this machine without any issues from my quantal host. But a VM installed with today's image (20121128) on the same host, same libvirt is not connecting in a similar way. It was attempted to add .local since the output of hostname -A did not match to the entries in /etc/hosts and /etc/hostname. ( I had to change the entries to match them, purge openssh-server, reboot the VM, install openssh-server again and then reboot the VM in order to make my ssh from the same host to work and I did NOT have to do all these things for the VM with the old image said above (20121108.2). I think that indicates a regression. ** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed -- 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/1084064 Title: Can not ssh to raring VM's using hostname Status in “network-manager” package in Ubuntu: Confirmed Bug description: It is impossible to ssh to a raring desktop vm using the hostname except the ip. It is required to manually edit /etc/hostname and /etc/hosts to include the domain name (.local) inorder for the ssh connection using the hostname to succeede. 1. Install raring desktop vm using libvirt on a precise or quantal host (20121128-amd64) 2. Install openssh-server on the vm 3. ssh to the vm from the host using the hostname (attempting with .local and without .local fails) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201211131441.e9e2c56-0ubuntu2 ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7 Uname: Linux 3.7.0-4-generic x86_64 ApportVersion: 2.6.2-0ubuntu5 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed Nov 28 12:45:54 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2012-11-28 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20121128) IpRoute: default via 192.168.122.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.122.0/24 dev eth0 proto kernel scope link src 192.168.122.197 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 10310d219-ab38-445f-8771-fdd7cad7392a 802-3-ethernet1354106562 Wed 28 Nov 2012 12:42:42 GMT yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1084064/+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 1080674] Re: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics)
Right, thanks for the workaround. Raring VMs work fine when started with -vga std. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1080674 Title: [QEMU] Corrupted desktop screen for raring desktop installation in QEMU guest (Cirrus graphics) Status in “mesa” package in Ubuntu: New Status in “xserver-xorg-video-cirrus” package in Ubuntu: New Bug description: The desktop screen appears corrupted after raring desktop installation. Please see attached screenshot for how it looks. Going through System settings - Appearance and selecting different wall papers does not solve the isssue. Test Steps: 1. Install Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) 2. Reboot after the installation and log in ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: unity 6.12.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.7.0-2.8-generic 3.7.0-rc5 Uname: Linux 3.7.0-2-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.6.2-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: [ 18.945219] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Mon Nov 19 12:26:26 2012 DistUpgraded: Fresh install DistroCodename: raring DistroVariant: ubuntu GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationDate: Installed on 2012-11-19 (0 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha i386 (20121119) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-2-generic root=UUID=131c13a4-8227-4946-8a1f-2aaa6043670d ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu1 version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.0.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.4-0ubuntu1 xserver.bootTime: Mon Nov 19 12:23:11 2012 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputAT Translated Set 2 keyboard KEYBOARD, id 7 inputImExPS/2 Generic Explorer Mouse MOUSE, id 8 xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.13.0-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1080674/+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 1065113] Re: Xorg crashed with SIGABRT in free()
Tried with quantal final image and i could not reproduce this after more than 5 attempts. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1065113 Title: Xorg crashed with SIGABRT in free() Status in “xorg-server” package in Ubuntu: Incomplete Status in “xorg-server” source package in Quantal: Incomplete Bug description: Occurred during screen reader testing for amd64 quantal 20121010 soon after the installer started 1. Start your machine with the install media in place 1.1 Wait to hear the drums 2. Press Ctrl+s to start the screen-reader 3. Press Alt+Tab to change to the installer 4. Press Up or Down arrow to select your language(default is English) 5. Press Tab once to Try Ubuntu 6. Press Enter 7. Wait for the Desktop to begin the installation. 8. Press Super+1 to begin the installation. Super is the left windows key *** The crash occurred at this point ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.327 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 10 16:00:00 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121010) MachineType: Dell Inc. Inspiron N4010 ProcCmdline: X -br -ac -noreset -nolisten tcp -background none vt7 :0 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity Signal: 6 SourcePackage: xorg-server StacktraceTop: free () from /lib/x86_64-linux-gnu/libc.so.6 SrvXkbFreeServerMap () SrvXkbFreeKeyboard () XkbFreeInfo () ?? () Title: Xorg crashed with SIGABRT in free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/19/2011:svnDellInc.:pnInspironN4010:pvrA11:rvnDellInc.:rn021CN3:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N4010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1065113/+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 1066321] Re: 'Failed to add/activate connection' from the login screen after wubi installation
This is probably the expected behaviour. Marking the bug as invalid ** Changed in: network-manager (Ubuntu) Status: New = Invalid -- 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/1066321 Title: 'Failed to add/activate connection' from the login screen after wubi installation Status in “network-manager” package in Ubuntu: Invalid Bug description: On the first reboot to finish wubi installation of (both amd64 and i386) trying to connect one of the listed wifi networks failed with the following message Failed to add/activate connection: (32) insufficient privileges. It was not possible to select a network inorder to enter the wireless key. Clicking the network threw the error message before entering the wireless security password. Once logged in, it was possible to select a network and enter the keys inorder to connect. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Sat Oct 13 16:16:15 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.71 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH BTHub3-24MT 8524e471-df0c-4ca0-8e11-f07ea3fa151b 802-11-wireless 1350141362 Sat 13 Oct 2012 16:16:02 BST yes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 1bd8dc5c8-c9f5-43d8-b8f0-61afa06a2144 802-3-ethernet1350140998 Sat 13 Oct 2012 16:09:58 BST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1066321/+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 1065113] Re: Xorg crashed with SIGABRT in free()
I have tried a few times today to reproduce this without success. I'll keep trying and would add the trace once i hit the bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1065113 Title: Xorg crashed with SIGABRT in free() Status in “xorg-server” package in Ubuntu: Incomplete Status in “xorg-server” source package in Quantal: Incomplete Bug description: Occurred during screen reader testing for amd64 quantal 20121010 soon after the installer started 1. Start your machine with the install media in place 1.1 Wait to hear the drums 2. Press Ctrl+s to start the screen-reader 3. Press Alt+Tab to change to the installer 4. Press Up or Down arrow to select your language(default is English) 5. Press Tab once to Try Ubuntu 6. Press Enter 7. Wait for the Desktop to begin the installation. 8. Press Super+1 to begin the installation. Super is the left windows key *** The crash occurred at this point ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.327 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 10 16:00:00 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121010) MachineType: Dell Inc. Inspiron N4010 ProcCmdline: X -br -ac -noreset -nolisten tcp -background none vt7 :0 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity Signal: 6 SourcePackage: xorg-server StacktraceTop: free () from /lib/x86_64-linux-gnu/libc.so.6 SrvXkbFreeServerMap () SrvXkbFreeKeyboard () XkbFreeInfo () ?? () Title: Xorg crashed with SIGABRT in free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/19/2011:svnDellInc.:pnInspironN4010:pvrA11:rvnDellInc.:rn021CN3:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N4010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1065113/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
** Attachment added: dmesg_good_first_boot https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401554/+files/dmesg_good_first_boot -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
** Attachment added: dmesg_bad_second_boot https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3401556/+files/dmesg_bad_second_boot -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
Failure was observed in the second boot -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
When attempted with plymouth-splash disabled I am able to bring up the desktop in the standard graphics mode. When plymouth-splash was re- enabled, the issue is reproducible with mainline kernel 3.5.5. -- 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/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
Was able to reproduce with 3.5.4 mainline kernel version as well -- 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/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
Occurs with 3.5.3 mainline kernel as well with plymouth-splash enabled -- 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/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
A fresh install with quantal desktop - amd+mac 20121011 also has the same issue. First boot after the installation went well but the subsequent ones do not boot in standard graphics mode. -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
When tried with 20120724.2 amd+mac quantal desktop, this issue was not reproducible (with ~10 reboots). Hence looking at bug 1066228 it appears be a regression that occurred between alpha3 and beta 1. -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
So here is the list of test runs, 20120724.2 - worked 20120918.1-worked 20121001 - worked 20121011 - FAILED The kernel was updated to the latest on top of a working 20121001 and it still worked -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] Re: [Macmini 5, 1] Fatal server error: Can not run in framebuffer mode on reboot
@apw Rebooted many times (more than 20) after updating the kernel to the latest on a known (20121001) good image, it worked ok, no failures could be observed. Removing /var/lib/ureadahead/pack from the known bad image seem to solve the issue. When it was made sure the file is removed before the reboot, the next reboot did not have this issue, the desktop came up on the standard gfx mode. When the file was present the next reboot failed, not so deterministically every time, but most of the times. -- 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/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot Status in “linux” package in Ubuntu: Confirmed Status in “xorg” package in Ubuntu: New Status in “linux” source package in Quantal: Confirmed Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1066883/+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 1066883] [NEW] Fatal server error: Can not run in framebuffer mode on reboot
Public bug reported: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 qa-manual-testing quantal rls-q-incoming running-unity ubuntu ** Description changed: - Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. - The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. + Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. + The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: - + Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Apple Inc. Device [106b:00e6] + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal
[Desktop-packages] [Bug 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
The above logs were taken from the first boot, hence does not have the error information. The attached tar contains the log after the failure ** Attachment added: log.tar.gz https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+attachment/3398945/+files/log.tar.gz -- 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/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot Status in “xorg” package in Ubuntu: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+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 1066883] Re: Fatal server error: Can not run in framebuffer mode on reboot
Reproducible with 20121015.2 as well, after entire disk fresh installation -- 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/1066883 Title: Fatal server error: Can not run in framebuffer mode on reboot Status in “xorg” package in Ubuntu: New Status in “xorg” source package in Quantal: New Bug description: Fatal server error: Can not run in framebuffer mode error occurs on the 2nd reboot onwards on a mac with external display. The first reboot after a fresh installation is working fine and from the second attempt the desktop fails to start on the standard graphics mode and 'Your screen, graphics card, and input device settings could not be detected correctly' error message is displayed. The logs attached are directly from the first reboot. A tar file will be added with the logs after the failure. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CurrentDmesg: Date: Mon Oct 15 14:37:01 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00e6] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64+mac (20121014) MachineType: Apple Inc. Macmini5,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=f5eb805b-ed9d-43f3-a316-9b906251e9d5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2011 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM51.88Z.0077.B0F.1110201309 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-8ED6AF5B48C039E1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini5,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-8ED6AF5B48C039E1 dmi.modalias: dmi:bvnAppleInc.:bvrMM51.88Z.0077.B0F.1110201309:bd10/20/2011:svnAppleInc.:pnMacmini5,1:pvr1.0:rvnAppleInc.:rnMac-8ED6AF5B48C039E1:rvrMacmini5,1:cvnAppleInc.:ct16:cvrMac-8ED6AF5B48C039E1: dmi.product.name: Macmini5,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1066883/+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 1066321] [NEW] 'Failed to add/activate connection' from the login screen after wubi installation
Public bug reported: On the first reboot to finish wubi installation of (both amd64 and i386) trying to connect one of the listed wifi networks failed with the following message Failed to add/activate connection: (32) insufficient privileges. It was not possible to select a network inorder to enter the wireless key. Clicking the network threw the error message before entering the wireless security password. Once logged in, it was possible to select a network and enter the keys inorder to connect. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Sat Oct 13 16:16:15 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.71 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH BTHub3-24MT 8524e471-df0c-4ca0-8e11-f07ea3fa151b 802-11-wireless 1350141362 Sat 13 Oct 2012 16:16:02 BST yes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 1bd8dc5c8-c9f5-43d8-b8f0-61afa06a2144 802-3-ethernet1350140998 Sat 13 Oct 2012 16:09:58 BST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.6.0connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 qa-manual-testing quantal rls-q-incoming running-unity ** Tags removed: q-rls-incoming ** Tags added: rls-q-incoming -- 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/1066321 Title: 'Failed to add/activate connection' from the login screen after wubi installation Status in “network-manager” package in Ubuntu: New Bug description: On the first reboot to finish wubi installation of (both amd64 and i386) trying to connect one of the listed wifi networks failed with the following message Failed to add/activate connection: (32) insufficient privileges. It was not possible to select a network inorder to enter the wireless key. Clicking the network threw the error message before entering the wireless security password. Once logged in, it was possible to select a network and enter the keys inorder to connect. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: network-manager 0.9.6.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Sat Oct 13 16:16:15 2012 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.71 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH BTHub3-24MT 8524e471-df0c-4ca0-8e11-f07ea3fa151b 802-11-wireless 1350141362 Sat 13 Oct 2012 16:16:02 BST yes no /org/freedesktop/NetworkManager/Settings/1 Wired connection 1bd8dc5c8-c9f5-43d8-b8f0-61afa06a2144 802-3-ethernet
[Desktop-packages] [Bug 751725] Re: software-center crashed with AptDaemonError in _medium_required(): org.debian.apt: Could not cancel transaction
The above occurred in s-c version-5.4.1.1, arch- i386, Uname-Linux3.5.0-17-generic i686 ** Tags added: quantal rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/751725 Title: software-center crashed with AptDaemonError in _medium_required(): org.debian.apt: Could not cancel transaction Status in “aptdaemon” package in Ubuntu: Confirmed Status in “software-center” package in Ubuntu: Confirmed Bug description: Binary package hint: software-center unexpected crash ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: software-center 3.1.25 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Tue Apr 5 09:45:39 2011 ExecutablePath: /usr/share/software-center/software-center InterpreterPath: /usr/bin/python2.7 ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/software-center'] SourcePackage: software-center Title: software-center crashed with AptDaemonError in _medium_required(): org.debian.apt: Could not cancel transaction UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/751725/+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 1065113] [NEW] Xorg crashed with SIGABRT in free()
Public bug reported: Occurred during screen reader testing for amd64 quantal 20121010 soon after the installer started 1. Start your machine with the install media in place 1.1 Wait to hear the drums 2. Press Ctrl+s to start the screen-reader 3. Press Alt+Tab to change to the installer 4. Press Up or Down arrow to select your language(default is English) 5. Press Tab once to Try Ubuntu 6. Press Enter 7. Wait for the Desktop to begin the installation. 8. Press Super+1 to begin the installation. Super is the left windows key *** The crash occurred at this point ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.327 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 10 16:00:00 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121010) MachineType: Dell Inc. Inspiron N4010 ProcCmdline: X -br -ac -noreset -nolisten tcp -background none vt7 :0 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity Signal: 6 SourcePackage: xorg-server StacktraceTop: free () from /lib/x86_64-linux-gnu/libc.so.6 SrvXkbFreeServerMap () SrvXkbFreeKeyboard () XkbFreeInfo () ?? () Title: Xorg crashed with SIGABRT in free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/19/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 021CN3 dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/19/2011:svnDellInc.:pnInspironN4010:pvrA11:rvnDellInc.:rn021CN3:rvrA11:cvnDellInc.:ct8:cvrA11: dmi.product.name: Inspiron N4010 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 q-manual-testing quantal ubuntu ** Visibility changed to: Public ** Description changed: Occurred during screen reader testing for amd64 quantal 20121010 soon after the installer started + + 1. Start your machine with the install media in place + 1.1 Wait to hear the drums + 2. Press Ctrl+s to start the screen-reader + 3. Press Alt+Tab to change to the installer + 4. Press Up or Down arrow to select your language(default is English) + 5. Press Tab once to Try Ubuntu + 6. Press Enter + 7. Wait for the Desktop to begin the installation. + 8. Press Super+1 to begin the installation. Super is the left windows key + + *** The crash occurred at this point + ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.6.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.327 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Wed Oct 10 16:00:00 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) -Subsystem: Dell Device [1028:0456] + Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) + Subsystem: Dell Device [1028:0456] LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121010) MachineType: Dell Inc. Inspiron N4010 ProcCmdline: X -br -ac -noreset -nolisten tcp -background
[Desktop-packages] [Bug 1064418] [NEW] Xorg crashed with SIGABRT in cirRefreshArea()
Public bug reported: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner 2. The workspace switcher was clicked *** at this point the vm logged out and logged in by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=396df7fe-1541-4c33-9642-1ffbcc8091c0 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 cirRefreshArea () from /usr/lib/xorg/modules/drivers/cirrus_drv.so ?? () from /usr/lib/xorg/modules/libshadowfb.so ?? () ?? () Title: Xorg crashed with SIGABRT in cirRefreshArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20121004.b2048c5e-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace qa-manual-testing quantal rls-q-incoming ubuntu ** Visibility changed to: Public ** Description changed: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner - 2. The workspace switcher was clicked *** at this point the vm logged out and logged in + 2. The workspace switcher was clicked *** at this point the vm logged out and logged in by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: - + ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: - Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) -Subsystem: Red Hat, Inc Device [1af4:1100] + Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) + Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: - + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic
[Desktop-packages] [Bug 1064418] Re: Xorg crashed with SIGABRT in cirRefreshArea()
Occurrs in an i386 vm with 20121009 on a different amd64 host as well. ** Description changed: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner - 2. The workspace switcher was clicked *** at this point the vm logged out and logged in by itself + 2. The workspace switcher was clicked *** at this point the vm logged out by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.5.0-17-generic root=UUID=396df7fe-1541-4c33-9642-1ffbcc8091c0 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 cirRefreshArea () from /usr/lib/xorg/modules/drivers/cirrus_drv.so ?? () from /usr/lib/xorg/modules/libshadowfb.so ?? () ?? () Title: Xorg crashed with SIGABRT in cirRefreshArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/01/2007 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr: dmi.product.name: Bochs dmi.sys.vendor: Bochs version.compiz: compiz 1:0.9.8.4-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20121004.b2048c5e-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1064418 Title: Xorg crashed with SIGABRT in cirRefreshArea() Status in “xorg-server” package in Ubuntu: New Bug description: Occurred on a virt-manager vm running amd64 20121009 on a quantal running 20121009. 1. A terminal window was opened and was moved to the bottom right hand corner 2. The workspace switcher was clicked *** at this point the vm logged out by itself 3. Went to the host os and did the same ops (12) 4. Then came back to the guest vm and then this crash occurred ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-core 2:1.13.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 CurrentDmesg: [ 24.768313] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. Date: Tue Oct 9 14:55:36 2012 DistUpgraded: Fresh install DistroCodename: quantal DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Cirrus Logic GD 5446 [1013:00b8] (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc Device [1af4:1100] InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121009) Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Bochs Bochs ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0
[Desktop-packages] [Bug 1063742] Re: evolution-calendar-factory crashed with SIGFPE in g_cclosure_marshal_VOID__OBJECTv()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1063742 Title: evolution-calendar-factory crashed with SIGFPE in g_cclosure_marshal_VOID__OBJECTv() Status in “evolution-data-server” package in Ubuntu: New Bug description: Occurred after quantal-quantal upgrade on 20121008. It seems a random occurrance. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: evolution-data-server 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Oct 8 13:49:06 2012 ExecutablePath: /usr/lib/evolution/evolution-calendar-factory InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64 (20121008) ProcCmdline: /usr/lib/evolution/evolution-calendar-factory ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR=set PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 Signal: 8 SourcePackage: evolution-data-server StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/evolution-data-server/calendar-backends/libecalbackendcontacts.so g_cclosure_marshal_VOID__OBJECTv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-calendar-factory crashed with SIGFPE in g_cclosure_marshal_VOID__OBJECTv() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1063742/+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 1063055] Re: colord-sane crashed with SIGABRT in raise()
** Visibility changed to: Public ** Tags added: qa-manual-testing ** Description changed: - Occurred on armhf with 20121006 desktop when terminal application was - closed + Occurred on quantal-desktop-armhf+omap4.img of 20121006 desktop when + terminal application was closed ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-212.19-omap4 3.5.4 Uname: Linux 3.5.0-212-omap4 armv7l ApportVersion: 2.6.1-0ubuntu1 Architecture: armhf Date: Sat Oct 6 19:17:57 2012 ExecutablePath: /usr/lib/arm-linux-gnueabihf/colord/colord-sane InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta armhf+omap4 (20121006) ProcCmdline: /usr/lib/arm-linux-gnueabihf/colord/colord-sane ProcEnviron: - + Signal: 6 SourcePackage: colord StacktraceTop: - ?? () from /lib/arm-linux-gnueabihf/libc.so.6 - raise () from /lib/arm-linux-gnueabihf/libc.so.6 - abort () from /lib/arm-linux-gnueabihf/libc.so.6 - ?? () from /lib/arm-linux-gnueabihf/libc.so.6 - ?? () from /lib/arm-linux-gnueabihf/libc.so.6 + ?? () from /lib/arm-linux-gnueabihf/libc.so.6 + raise () from /lib/arm-linux-gnueabihf/libc.so.6 + abort () from /lib/arm-linux-gnueabihf/libc.so.6 + ?? () from /lib/arm-linux-gnueabihf/libc.so.6 + ?? () from /lib/arm-linux-gnueabihf/libc.so.6 Title: colord-sane crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1063055 Title: colord-sane crashed with SIGABRT in raise() Status in “colord” package in Ubuntu: New Bug description: Occurred on quantal-desktop-armhf+omap4.img of 20121006 desktop when terminal application was closed ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: colord 0.1.21-1ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-212.19-omap4 3.5.4 Uname: Linux 3.5.0-212-omap4 armv7l ApportVersion: 2.6.1-0ubuntu1 Architecture: armhf Date: Sat Oct 6 19:17:57 2012 ExecutablePath: /usr/lib/arm-linux-gnueabihf/colord/colord-sane InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta armhf+omap4 (20121006) ProcCmdline: /usr/lib/arm-linux-gnueabihf/colord/colord-sane ProcEnviron: Signal: 6 SourcePackage: colord StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 ?? () from /lib/arm-linux-gnueabihf/libc.so.6 ?? () from /lib/arm-linux-gnueabihf/libc.so.6 Title: colord-sane crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1063055/+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 1062191] Re: gsettings-data-convert crashed with SIGSEGV in g_settings_backend_path_changed()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1062191 Title: gsettings-data-convert crashed with SIGSEGV in g_settings_backend_path_changed() Status in “gconf” package in Ubuntu: New Bug description: This crash occurred on a quantal to quantal upgrade and when i switch to the guest session and then came back to the installed user's session. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gconf2 3.2.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-17.26-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Fri Oct 5 11:51:53 2012 ExecutablePath: /usr/bin/gsettings-data-convert ProcCmdline: gsettings-data-convert --file=/usr/lib/compiz/migration/compiz-profile-independent-keys.convert ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe94a507cea:mov(%rax,%r14,1),%rax PC (0x7fe94a507cea) ok source (%rax,%r14,1) (0x0008) not located in a known VMA region (needed readable region)! destination %rax ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gconf StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 g_settings_backend_path_changed () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: gsettings-data-convert crashed with SIGSEGV in g_settings_backend_path_changed() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1062191/+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 1060851] [NEW] Yubikey input is wrongly read after precise to quantal upgrade
Public bug reported: The yubikey input is read as 'ccbfuiedhjbigkeeenrduuelnfefnurhkedlfvnr ' after the precise to quantal upgrades leaving the two factor authorisation impossible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: signon-ui 0.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 10:52:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120926.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: signon-ui UpgradeStatus: Upgraded to quantal on 2012-09-27 (5 days ago) ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug quantal rls-q-incoming running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1060851 Title: Yubikey input is wrongly read after precise to quantal upgrade Status in “signon-ui” package in Ubuntu: New Bug description: The yubikey input is read as 'ccbfuiedhjbigkeeenrduuelnfefnurhkedlfvnr ' after the precise to quantal upgrades leaving the two factor authorisation impossible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: signon-ui 0.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 10:52:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120926.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: signon-ui UpgradeStatus: Upgraded to quantal on 2012-09-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1060851/+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 1060851] Re: Yubikey input is wrongly read after precise to quantal upgrade
** Attachment added: dist-upgrade.tar.gz https://bugs.launchpad.net/bugs/1060851/+attachment/3367787/+files/dist-upgrade.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1060851 Title: Yubikey input is wrongly read after precise to quantal upgrade Status in “signon-ui” package in Ubuntu: New Bug description: The yubikey input is read as 'ccbfuiedhjbigkeeenrduuelnfefnurhkedlfvnr ' after the precise to quantal upgrades leaving the two factor authorisation impossible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: signon-ui 0.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 10:52:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120926.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: signon-ui UpgradeStatus: Upgraded to quantal on 2012-09-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1060851/+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 1060851] Re: Yubikey input is wrongly read after precise to quantal upgrade
Apparently this issue is not about quantal upgrade. I must have been pressing it during either shorter or longer not in the middle. Closing the bug since. ** Changed in: signon-ui (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1060851 Title: Yubikey input is wrongly read after precise to quantal upgrade Status in “signon-ui” package in Ubuntu: Invalid Bug description: The yubikey input is read as 'ccbfuiedhjbigkeeenrduuelnfefnurhkedlfvnr ' after the precise to quantal upgrades leaving the two factor authorisation impossible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: signon-ui 0.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 10:52:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120926.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: signon-ui UpgradeStatus: Upgraded to quantal on 2012-09-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1060851/+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 1060851] Re: Yubikey input is wrongly read after precise to quantal upgrade
** Tags removed: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1060851 Title: Yubikey input is wrongly read after precise to quantal upgrade Status in “signon-ui” package in Ubuntu: Invalid Bug description: The yubikey input is read as 'ccbfuiedhjbigkeeenrduuelnfefnurhkedlfvnr ' after the precise to quantal upgrades leaving the two factor authorisation impossible. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: signon-ui 0.11-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Wed Oct 3 10:52:24 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120926.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: signon-ui UpgradeStatus: Upgraded to quantal on 2012-09-27 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1060851/+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 1058118] [NEW] gvfs fuse deamon crash during Lucid to Precise desktop upgrade
Public bug reported: This crash occurs consistently during the upgrade from Lucid to precise. https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job /precise-upgrade-lucid-desktop/ARCH=amd64,LTS=lts,PROFILE=ubuntu,label =upgrade-test/ ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing qa-manual-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1058118 Title: gvfs fuse deamon crash during Lucid to Precise desktop upgrade Status in “gvfs” package in Ubuntu: New Bug description: This crash occurs consistently during the upgrade from Lucid to precise. https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job /precise-upgrade-lucid-desktop/ARCH=amd64,LTS=lts,PROFILE=ubuntu,label =upgrade-test/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1058118/+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 1058134] [NEW] Gnome settings daemon crash during Lucid to Precise upgrade
Public bug reported: This crash happens consistently during Lucid to Precise upgrades on amd64 https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job /precise-upgrade-lucid-main/248/ARCH=amd64,LTS=lts,PROFILE=main- all,label=upgrade-test/ ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing qa-manual-testing ** Summary changed: - Gnome settings deamon crash during Lucid to Precise upgrade + Gnome settings daemon crash during Lucid to Precise upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1058134 Title: Gnome settings daemon crash during Lucid to Precise upgrade Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: This crash happens consistently during Lucid to Precise upgrades on amd64 https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job /precise-upgrade-lucid-main/248/ARCH=amd64,LTS=lts,PROFILE=main- all,label=upgrade-test/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1058134/+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 1058118] Re: gvfs fuse daemon crash during Lucid to Precise desktop upgrade
** Summary changed: - gvfs fuse deamon crash during Lucid to Precise desktop upgrade + gvfs fuse daemon crash during Lucid to Precise desktop upgrade -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1058118 Title: gvfs fuse daemon crash during Lucid to Precise desktop upgrade Status in “gvfs” package in Ubuntu: New Bug description: This crash occurs consistently during the upgrade from Lucid to precise. https://jenkins.qa.ubuntu.com/view/Precise/view/Upgrade%20Testing%20Dashboard/job /precise-upgrade-lucid-desktop/ARCH=amd64,LTS=lts,PROFILE=ubuntu,label =upgrade-test/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1058118/+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 1056849] Re: gedit crashed with signal 5 in _XReply()
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1056849 Title: gedit crashed with signal 5 in _XReply() Status in “gedit” package in Ubuntu: New Bug description: Opening gedit 3 times caused this crash on Quantal deskto i386 with 768M Ram ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gedit 3.5.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic i686 ApportVersion: 2.5.2-0ubuntu4 Architecture: i386 Date: Wed Sep 26 14:14:21 2012 ExecutablePath: /usr/bin/gedit ProcCmdline: gedit ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6 _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6 XInternAtom () from /usr/lib/i386-linux-gnu/libX11.so.6 gdk_x11_atom_to_xatom_for_display () from /usr/lib/i386-linux-gnu/libgdk-3.so.0 Title: gedit crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1056849/+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 1057010] Re: gwibber-service crashed with OSError in makedirs(): [Errno 17] File exists: '/home/username/.cache/sso'
** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gwibber in Ubuntu. https://bugs.launchpad.net/bugs/1057010 Title: gwibber-service crashed with OSError in makedirs(): [Errno 17] File exists: '/home/username/.cache/sso' Status in “gwibber” package in Ubuntu: New Bug description: occurred with 20120926 mad64+mac desktop image (beta2). ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gwibber-service 3.5.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-15.23-generic 3.5.4 Uname: Linux 3.5.0-15-generic x86_64 ApportVersion: 2.5.2-0ubuntu4 Architecture: amd64 Date: Wed Sep 26 17:15:11 2012 ExecutablePath: /usr/bin/gwibber-service InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Beta amd64+mac (20120926) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/gwibber-service ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_GB:en LANG=en_GB.UTF-8 PythonArgs: ['/usr/bin/gwibber-service'] SourcePackage: gwibber Title: gwibber-service crashed with OSError in makedirs(): [Errno 17] File exists: '/home/username/.cache/sso' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/1057010/+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 827934] Re: colord crashed with SIGABRT in raise()
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/827934 Title: colord crashed with SIGABRT in raise() Status in “colord” package in Ubuntu: Confirmed Status in “colord” source package in Precise: Confirmed Bug description: I was just trying to install a Samsung Network Printer. The error occurred during driver configuration of the printer. The printer was installed correctly. Unable to reproduce just now. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: colord 0.1.11-1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Wed Aug 17 12:46:37 2011 ExecutablePath: /usr/lib/x86_64-linux-gnu/colord/colord InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha amd64 (20110802.1) ProcCmdline: /usr/lib/x86_64-linux-gnu/colord/colord ProcEnviron: Signal: 6 SourcePackage: colord StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () Title: colord crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/827934/+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 905686] Re: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed.
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/905686 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. Status in Modular X11 Libraries: Confirmed Status in “libx11” package in Ubuntu: Triaged Status in “nautilus” package in Ubuntu: Confirmed Bug description: Here is a backtrace from Ubuntu Precise. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: nautilus 1:3.2.1-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-5.11-generic-pae 3.2.0-rc5 Uname: Linux 3.2.0-5-generic-pae i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 AssertionMessage: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. Date: Sat Dec 17 14:16:03 2011 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1324036665 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcCmdline: nautilus -n ProcCwd: / Signal: 6 SourcePackage: nautilus StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 __assert_fail () from /lib/i386-linux-gnu/libc.so.6 _XAllocID () from /usr/lib/i386-linux-gnu/libX11.so.6 Title: nautilus assert failure: nautilus: ../../src/xcb_io.c:528: _XAllocID: Assertion `ret != inval_id' failed. UpgradeStatus: Upgraded to precise on 2011-12-16 (1 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/xlibs/+bug/905686/+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 1018534] Re: Missing icons on g-c-c with High Contrast theme
** Tags added: rls-q-incoming -- 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/1018534 Title: Missing icons on g-c-c with High Contrast theme Status in “gnome-control-center” package in Ubuntu: Incomplete Bug description: Some icons are missing in gnome-control-center with the theme 'High Contrast' Screenshot attached ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu6 ProcVersionSignature: Ubuntu 3.5.0-1.1-generic 3.5.0-rc3 Uname: Linux 3.5.0-1-generic x86_64 ApportVersion: 2.2.5-0ubuntu1 Architecture: amd64 Date: Wed Jun 27 20:43:44 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-01-31 (147 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1018534/+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 1045666] Re: Style differs if ubiquity is started directly from 'Install Ubuntu' or from a Live Session
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1045666 Title: Style differs if ubiquity is started directly from 'Install Ubuntu' or from a Live Session Status in “gnome-settings-daemon” package in Ubuntu: Incomplete Status in “ubiquity” package in Ubuntu: Invalid Bug description: Quantal Desktop 20120903 The style of ubiquity is different whether it is started from a Live Session or directly from the Install menu. The differences I noted when start from 'Install Ubuntu' - Buttons have icons - It doesn't use the Ubuntu font - There is a minimize windows button on the top left. Screenshot attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1045666/+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 960649] Re: vino-server SIGABRT, buffer overflow detected in clipboard handling code
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/960649 Title: vino-server SIGABRT, buffer overflow detected in clipboard handling code Status in “vino” package in Ubuntu: Triaged Status in “vino” source package in Precise: Triaged Bug description: vino crashed in the background while I was doing unrelated tasks in the foreground. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: vino 3.3.92-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Tue Mar 20 23:49:49 2012 ExecutablePath: /usr/lib/vino/vino-server InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120315) ProcCmdline: /usr/lib/vino/vino-server --sm-disable Signal: 6 SourcePackage: vino StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 ?? () from /lib/x86_64-linux-gnu/libc.so.6 __fortify_fail () from /lib/x86_64-linux-gnu/libc.so.6 __chk_fail () from /lib/x86_64-linux-gnu/libc.so.6 Title: vino-server crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vino/+bug/960649/+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 1032172] Re: liferea crashed with signal 5 in db_item_load()
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1032172 Title: liferea crashed with signal 5 in db_item_load() Status in “liferea” package in Ubuntu: New Bug description: Liferea crashed on close ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: liferea 1.8.3-0.1ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-7.7-generic 3.5.0 Uname: Linux 3.5.0-7-generic x86_64 ApportVersion: 2.4-0ubuntu6 Architecture: amd64 Date: Thu Aug 2 07:33:56 2012 ExecutablePath: /usr/bin/liferea InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64+mac (20120328) ProcCmdline: liferea ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: liferea StacktraceTop: ?? () db_item_load () ?? () itemlist_unload () feedlist_selection_changed () Title: liferea crashed with signal 5 in db_item_load() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm kvm libvirtd lpadmin sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liferea/+bug/1032172/+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 765397] Re: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x08d86650 ***
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/765397 Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x08d86650 *** Status in “indicator-weather” package in Ubuntu: Confirmed Bug description: Binary package hint: indicator-weather Wasn't doing anything with it when it crashed. ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: indicator-weather 11.04.10+repack-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 NonfreeKernelModules: wl Architecture: i386 AssertionMessage: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x08d86650 *** Date: Mon Apr 18 20:16:27 2011 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.04 Natty Narwhal - Beta i386 (20110405) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/indicator-weather ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: indicator-weather StacktraceTop: __kernel_vsyscall () raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 ?? () from /lib/i386-linux-gnu/libc.so.6 Title: indicator-weather assert failure: *** glibc detected *** /usr/bin/python: realloc(): invalid pointer: 0x08d86650 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/765397/+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 817672] Re: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children()
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/817672 Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children() Status in “indicator-weather” package in Ubuntu: Confirmed Bug description: Description: Ubuntu oneiric (development branch) Release: 11.10 indicator-weather: Installed: 11.05.31-0ubuntu1 Candidate: 11.05.31-0ubuntu1 Version table: *** 11.05.31-0ubuntu1 0 500 http://ru.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: indicator-weather 11.05.31-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-7.8-generic 3.0.0 Uname: Linux 3.0.0-7-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Thu Jul 28 22:53:44 2011 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release amd64 (20110427.1) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/indicator-weather SegvAnalysis: Segfault happened at: 0x7f13836e78e6 dbusmenu_menuitem_get_children+22: cmp%rax,(%rdx) PC (0x7f13836e78e6) ok source %rax ok destination (%rdx) (0x70008) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: indicator-weather StacktraceTop: dbusmenu_menuitem_get_children () from /usr/lib/libdbusmenu-glib.so.4 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4 dbusmenu_menuitem_build_variant () from /usr/lib/libdbusmenu-glib.so.4 ?? () from /usr/lib/libdbusmenu-glib.so.4 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: indicator-weather crashed with SIGSEGV in dbusmenu_menuitem_get_children() UpgradeStatus: Upgraded to oneiric on 2011-07-27 (1 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/817672/+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 934531] Re: gnome-settings-daemon crashed with SIGSEGV in unpress_keys()
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/934531 Title: gnome-settings-daemon crashed with SIGSEGV in unpress_keys() Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: crashed suddenly ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.5-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Fri Feb 17 22:50:48 2012 EcryptfsInUse: Yes ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f41559e7400:movzbl 0xc(%rcx),%eax PC (0x7f41559e7400) ok source 0xc(%rcx) (0xaab6) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: ?? () from /usr/lib/libgnomekbdui.so.7 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-settings-daemon crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin libvirtd lpadmin sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/934531/+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 1041169] Re: custom keyboard shortcuts not migrated after upgrade to compiz 1:0.9.8+bzr3319-0ubuntu2
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1041169 Title: custom keyboard shortcuts not migrated after upgrade to compiz 1:0.9.8+bzr3319-0ubuntu2 Status in “compiz” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: In the keyboard shortcut preferences I had set CTRL+Fn for the actions Navigation/Switch to workspace n where n is the number of the workspace After migration to compiz 1:0.9.8+bzr3319-0ubuntu2 all the shortcuts have been reset to 'Disabled' ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: compiz 1:0.9.8+bzr3319-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Fri Aug 24 14:39:21 2012 DistUpgraded: 2012-02-01 00:15:24,616 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu DkmsStatus: virtualbox, 4.1.18, 3.5.0-10-generic, x86_64: installed virtualbox, 4.1.18, 3.5.0-11-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI Juniper [Radeon HD 5700 Series] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited Device [174b:1482] MachineType: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=cf89ba34-108b-404d-9804-32d54a1df2ea ro quiet splash vt.handoff=7 SourcePackage: compiz UpgradeStatus: Upgraded to quantal on 2012-01-31 (205 days ago) dmi.bios.date: 07/23/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FD dmi.board.name: GA-890GPA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFD:bd07/23/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-890GPA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-890GPA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-890GPA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.8+bzr3319-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.38-0ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1041169/+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 857505] Re: indicator-weather crashed with SIGABRT in raise()
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to indicator-weather in Ubuntu. https://bugs.launchpad.net/bugs/857505 Title: indicator-weather crashed with SIGABRT in raise() Status in “indicator-weather” package in Ubuntu: Triaged Bug description: it crashes ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: indicator-weather 11.05.31-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 23 17:29:36 2011 ExecutablePath: /usr/bin/indicator-weather InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64+mac (20110920.5) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/indicator-weather ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: indicator-weather StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: indicator-weather crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-weather/+bug/857505/+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 1040885] Re: gnome-terminal auto-restores its size
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1040885 Title: gnome-terminal auto-restores its size Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: Occurs on Quantal TEST CASE 1. Press CTRL+ALT+T to launch a terminal 2. Press CTRL+SHIFT+T to open a new tab 3. Make sure the second tab is active and resize the window (Alt+Middle mouse button or Windows handles) 4. Click on the desktop ACTUAL RESULT Size of the terminal is restored to its initial size. It doesn't occur if the window is resized while first tab is active. EXPECTED RESULT The terminal doesn't autoresize with the user clicks on the desktop ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-terminal 3.5.90-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu1 Architecture: amd64 Date: Thu Aug 23 23:21:07 2012 ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: Upgraded to quantal on 2012-01-31 (204 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1040885/+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 1042223] Re: test_purchase_backend.TestPurchaseBackend.test_add_license_key_backend failed with:TypeError: add_repo_add_key_and_install_app() takes at least 7 arguments (6 give
** Tags added: rls-q-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-center in Ubuntu. https://bugs.launchpad.net/bugs/1042223 Title: test_purchase_backend.TestPurchaseBackend.test_add_license_key_backend failed with:TypeError: add_repo_add_key_and_install_app() takes at least 7 arguments (6 given) Status in “software-center” package in Ubuntu: New Bug description: DEP8 test of Software-center found the the following testing is failing: # xvfb-run python -m unittest -cvvb tests.test_purchase_backend test_add_license_key_backend (tests.test_purchase_backend.TestPurchaseBackend) ... ERROR == ERROR: test_add_license_key_backend (tests.test_purchase_backend.TestPurchaseBackend) -- Traceback (most recent call last): File tests/test_purchase_backend.py, line 44, in test_add_license_key_backend self.LICENSE_KEY) File /usr/lib/python2.7/dist-packages/defer/__init__.py, line 599, in unwind_generator return _inline_callbacks(None, func(*args, **kwargs), Deferred()) TypeError: add_repo_add_key_and_install_app() takes at least 7 arguments (6 given) -- Ran 1 test in 0.031s FAILED (errors=1) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: software-center 5.3.9 ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2 Uname: Linux 3.5.0-11-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Mon Aug 27 14:51:29 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: Upgraded to quantal on 2012-01-31 (208 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1042223/+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 1049057] [NEW] Obsolete config files -gnome keyring module-left after precise to quantal upgrades
Public bug reported: quantal- i386 and amd64, /etc/pkcs11/modules/gnome-keyring-module is left after precise to quantal upgrade https://jenkins.qa.ubuntu.com/view/Quantal/view/Upgrade%20Testing%20Dashboard/job/quantal-upgrade-precise-desktop/142/ARCH=amd64,LTS=non-lts,PROFILE=desktop,label=upgrade-test/artifact/results/obsolete_conffiles.log ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Tue Sep 11 11:47:00 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120828.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to precise on 2012-09-06 (4 days ago) ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise 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/1049057 Title: Obsolete config files -gnome keyring module-left after precise to quantal upgrades Status in “gnome-keyring” package in Ubuntu: New Bug description: quantal- i386 and amd64, /etc/pkcs11/modules/gnome-keyring-module is left after precise to quantal upgrade https://jenkins.qa.ubuntu.com/view/Quantal/view/Upgrade%20Testing%20Dashboard/job/quantal-upgrade-precise-desktop/142/ARCH=amd64,LTS=non-lts,PROFILE=desktop,label=upgrade-test/artifact/results/obsolete_conffiles.log ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Tue Sep 11 11:47:00 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120828.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to precise on 2012-09-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1049057/+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 1049057] Re: Obsolete config files -gnome keyring module-left after precise to quantal upgrades
-- 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/1049057 Title: Obsolete config files -gnome keyring module-left after precise to quantal upgrades Status in “gnome-keyring” package in Ubuntu: New Bug description: quantal- i386 and amd64, /etc/pkcs11/modules/gnome-keyring-module is left after precise to quantal upgrade https://jenkins.qa.ubuntu.com/view/Quantal/view/Upgrade%20Testing%20Dashboard/job/quantal-upgrade-precise-desktop/142/ARCH=amd64,LTS=non-lts,PROFILE=desktop,label=upgrade-test/artifact/results/obsolete_conffiles.log ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-keyring 3.2.2-2ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-30.48-generic-pae 3.2.27 Uname: Linux 3.2.0-30-generic-pae i686 ApportVersion: 2.0.1-0ubuntu12 Architecture: i386 Date: Tue Sep 11 11:47:00 2012 InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release i386 (20120828.1) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to precise on 2012-09-06 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1049057/+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 971353] Re: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode
This occurred again when quantal-desktop-amd64+mac.iso of 20120905.2 during a live session. Just tried to do some settings change during the live session, such as changing the keyboard layout, timezone change. If it does not occur leave it for some time and this would occur. ALSO, reported a couple of bugs before for amd64+mac with the crash files but made invalid due to uncompatible symbol files. So may be that need to be looked at as well for live sessions not containing the correct symbol files. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/971353 Title: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode Status in Gnome Settings Daemon: New Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” source package in Precise: Confirmed Status in “gnome-settings-daemon” source package in Quantal: Confirmed Bug description: spontaneous crash at startup ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Mon Apr 2 12:11:23 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon Title: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/971353/+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 971353] Re: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode
The same again during the live session on amd64 hardware. 20120905.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/971353 Title: power : gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode Status in Gnome Settings Daemon: New Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Status in “gnome-settings-daemon” source package in Precise: Confirmed Status in “gnome-settings-daemon” source package in Quantal: Confirmed Bug description: spontaneous crash at startup ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.4.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 2.0-0ubuntu2 Architecture: amd64 CasperVersion: 1.312 Date: Mon Apr 2 12:11:23 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Xubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120328) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: LANGUAGE= TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon Title: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/971353/+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 1045773] Re: gnome-settings-daemon crashed with SIGSEGV
** Tags added: iso-testing q-manual-testing q-rls-incoming ** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1045773 Title: gnome-settings-daemon crashed with SIGSEGV Status in “gnome-settings-daemon” package in Ubuntu: Invalid Bug description: Crash occurred using the screen reader for live session testing. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu10 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic i686 ApportVersion: 2.5.1-0ubuntu4 Architecture: i386 CasperVersion: 1.321 CrashCounter: 1 Date: Tue Sep 4 11:25:18 2012 Disassembly: = 0xb776aa40: Cannot access memory at address 0xb776aa40 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120903.4) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb776aa40:Cannot access memory at address 0xb776aa40 PC (0xb776aa40) ok SP (0xbfd96710) ok Reason could not be automatically determined. Signal: 11 SourcePackage: gnome-settings-daemon Stacktrace: #0 0xb776aa40 in ?? () No symbol table info available. StacktraceTop: ?? () ThreadStacktrace: . Thread 4 (LWP 4037): #0 0xb77a3424 in ?? () No symbol table info available. Cannot access memory at address 0x5 Title: gnome-settings-daemon crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1045773/+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 1045419] Re: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode()
*** This bug is a duplicate of bug 971353 *** https://bugs.launchpad.net/bugs/971353 ** Tags added: iso-testing qa-manual-testing rls-q-incoming ** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1045419 Title: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode() Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: This occurred when attempted to do a liveusb installation of quantal amd64+mac. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu10 ProcVersionSignature: Ubuntu 3.5.0-13.14-generic 3.5.3 Uname: Linux 3.5.0-13-generic x86_64 ApportVersion: 2.5.1-0ubuntu4 Architecture: amd64 CasperVersion: 1.321 Date: Mon Sep 3 16:23:08 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-settings-daemon LiveMediaBuild: Ubuntu 12.10 Quantal Quetzal - Alpha amd64+mac (20120903.2) ProcCmdline: /usr/lib/gnome-settings-daemon/gnome-settings-daemon ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7fc8dec9b619 gnome_rr_screen_get_dpms_mode+73: mov0x18(%rdi),%rax PC (0x7fc8dec9b619) ok source 0x18(%rdi) (0x0018) not located in a known VMA region (needed readable region)! destination %rax ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-settings-daemon StacktraceTop: gnome_rr_screen_get_dpms_mode () from /usr/lib/libgnome-desktop-3.so.4 gnome_rr_screen_set_dpms_mode () from /usr/lib/libgnome-desktop-3.so.4 ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/gnome-settings-daemon-3.0/libpower.so ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: [power]: gnome-settings-daemon crashed with SIGSEGV in gnome_rr_screen_get_dpms_mode() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1045419/+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 1029000] Re: nautilus crashed with SIGABRT in raise()
** Tags added: qa-testing-manual ** Visibility changed to: Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1029000 Title: nautilus crashed with SIGABRT in raise() Status in “nautilus” package in Ubuntu: New Bug description: This occurred when ifconfig was run on a vm with Virtual Machine Manager, soon after the installation. The host machine is i386 generic -pae Precise. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: nautilus 1:3.5.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic i686 ApportVersion: 2.4-0ubuntu5 Architecture: i386 Date: Wed Jul 25 17:22:42 2012 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha i386 (20120724.2) ProcCmdline: nautilus -n ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: nautilus StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () Title: nautilus crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1029000/+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 1001211] [NEW] No preference setting is available to open messages in an existing tab
Public bug reported:
(Double) Clicking on a particular email item opens new tab for every
clicks despite the same email is already open. This leads to the
presence of multiple tabs of the same mail item cluttering the view.
It will be sensible to have an advanced preference setting to 'Open
messages in:' the existing tab.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sivatharman 1970 F pulseaudio
/dev/snd/pcmC0D0p: sivatharman 1970 F...m pulseaudio
BuildID: 20120430053815
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 44'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c166f,00100105
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Channel: release
Date: Fri May 18 12:19:50 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions:
Messaging Menu and Unity Launcher integration - ID=messagingm...@mozilla.com,
Version=0.9.3, minVersion=3.3a1pre, maxVersion=12.0a1, Location=app-global,
Type=extension, Active=Yes
EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9,
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension,
Active=Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.5 metric 2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=12.0.1/20120430053815 (Running)
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to precise on 2012-04-14 (33 days ago)
dmi.bios.date: 08/30/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 166F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.33:bd08/30/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901220471620100:rvnHewlett-Packard:rn166F:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 06901220471620100
dmi.sys.vendor: Hewlett-Packard
** Affects: thunderbird (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 precise release-channel
--
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/1001211
Title:
No preference setting is available to open messages in an existing tab
Status in “thunderbird” package in Ubuntu:
New
Bug description:
(Double) Clicking on a particular email item opens new tab for every
clicks despite the same email is already open. This leads to the
presence of multiple tabs of the same mail item cluttering the view.
It will be sensible to have an advanced preference setting to 'Open
messages in:' the existing tab.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sivatharman 1970 F pulseaudio
/dev/snd/pcmC0D0p: sivatharman 1970 F...m pulseaudio
BuildID: 20120430053815
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 44'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c166f,00100105
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Channel: release
Date: Fri May 18 12:19:50 2012
ForcedLayersAccel: False
[Desktop-packages] [Bug 1001211] Re: No preference setting is available to open messages in an existing tab
** Attachment added: Preference Settings.png
https://bugs.launchpad.net/bugs/1001211/+attachment/3152107/+files/Preference%20Settings.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/1001211
Title:
No preference setting is available to open messages in an existing tab
Status in “thunderbird” package in Ubuntu:
New
Bug description:
(Double) Clicking on a particular email item opens new tab for every
clicks despite the same email is already open. This leads to the
presence of multiple tabs of the same mail item cluttering the view.
It will be sensible to have an advanced preference setting to 'Open
messages in:' the existing tab.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sivatharman 1970 F pulseaudio
/dev/snd/pcmC0D0p: sivatharman 1970 F...m pulseaudio
BuildID: 20120430053815
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 44'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c166f,00100105
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Channel: release
Date: Fri May 18 12:19:50 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions:
Messaging Menu and Unity Launcher integration -
ID=messagingm...@mozilla.com, Version=0.9.3, minVersion=3.3a1pre,
maxVersion=12.0a1, Location=app-global, Type=extension, Active=Yes
EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9,
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension,
Active=Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.5 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=12.0.1/20120430053815 (Running)
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to precise on 2012-04-14 (33 days ago)
dmi.bios.date: 08/30/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 166F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.33:bd08/30/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901220471620100:rvnHewlett-Packard:rn166F:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 06901220471620100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1001211/+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 1001211] Re: No preference setting is available to open messages in an existing tab
** Visibility changed to: Public
--
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/1001211
Title:
No preference setting is available to open messages in an existing tab
Status in “thunderbird” package in Ubuntu:
New
Bug description:
(Double) Clicking on a particular email item opens new tab for every
clicks despite the same email is already open. This leads to the
presence of multiple tabs of the same mail item cluttering the view.
It will be sensible to have an advanced preference setting to 'Open
messages in:' the existing tab.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sivatharman 1970 F pulseaudio
/dev/snd/pcmC0D0p: sivatharman 1970 F...m pulseaudio
BuildID: 20120430053815
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 44'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c166f,00100105
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Channel: release
Date: Fri May 18 12:19:50 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions:
Messaging Menu and Unity Launcher integration -
ID=messagingm...@mozilla.com, Version=0.9.3, minVersion=3.3a1pre,
maxVersion=12.0a1, Location=app-global, Type=extension, Active=Yes
EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9,
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension,
Active=Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.5 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=12.0.1/20120430053815 (Running)
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to precise on 2012-04-14 (33 days ago)
dmi.bios.date: 08/30/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 166F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.33:bd08/30/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901220471620100:rvnHewlett-Packard:rn166F:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 06901220471620100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1001211/+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 1001211] Re: No preference setting is available in thunderbird to open messages in an existing tab
** Summary changed:
- No preference setting is available to open messages in an existing tab
+ No preference setting is available in thunderbird to open messages in an
existing tab
--
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/1001211
Title:
No preference setting is available in thunderbird to open messages in
an existing tab
Status in “thunderbird” package in Ubuntu:
New
Bug description:
(Double) Clicking on a particular email item opens new tab for every
clicks despite the same email is already open. This leads to the
presence of multiple tabs of the same mail item cluttering the view.
It will be sensible to have an advanced preference setting to 'Open
messages in:' the existing tab.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: thunderbird 12.0.1+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sivatharman 1970 F pulseaudio
/dev/snd/pcmC0D0p: sivatharman 1970 F...m pulseaudio
BuildID: 20120430053815
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc260 irq 44'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c166f,00100105
HDA:80862805,80860101,0010'
Controls : 22
Simple ctrls : 10
Channel: release
Date: Fri May 18 12:19:50 2012
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
IncompatibleExtensions:
Messaging Menu and Unity Launcher integration -
ID=messagingm...@mozilla.com, Version=0.9.3, minVersion=3.3a1pre,
maxVersion=12.0a1, Location=app-global, Type=extension, Active=Yes
EDS Contact Integration - ID=edsintegrat...@mozilla.com, Version=0.3.9,
minVersion=7.0, maxVersion=11.0a1, Location=app-global, Type=extension,
Active=Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
IpRoute:
default via 192.168.0.1 dev wlan0 proto static
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.5 metric
2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
ProcEnviron:
LANGUAGE=en_GB:en
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=12.0.1/20120430053815 (Running)
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
RunningIncompatibleAddons: True
SourcePackage: thunderbird
UpgradeStatus: Upgraded to precise on 2012-04-14 (33 days ago)
dmi.bios.date: 08/30/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 166F
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.37
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.33:bd08/30/2011:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr06901220471620100:rvnHewlett-Packard:rn166F:rvr09.37:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 06901220471620100
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1001211/+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
