[Desktop-packages] [Bug 578460] Re: [Karmic, Lucid] 82G33/G31 Card Fails to detect proper resolutions
I haven't had that hardware in a couple of years, so this can expire unless anybody else is still experiencing it. -- 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/578460 Title: [Karmic,Lucid] 82G33/G31 Card Fails to detect proper resolutions Status in “xorg-server” package in Ubuntu: Incomplete Bug description: Binary package hint: xorg Started at Jaunty, everything worked great. Upgraded to Karmic yesterday, saw the issue. Upgraded to lucid today, the issue persists. The monitor should be at 1680x1050. The PreferencesMonitors dialog reports the current resolution as 1360x768, but the monitor itself reports it as 1280x768. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+5ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 Date: Mon May 10 15:55:42 2010 DkmsStatus: virtualbox-ose, 3.1.6, 2.6.31-21-generic, x86_64: built virtualbox-ose, 3.1.6, 2.6.32-22-generic, x86_64: installed MachineType: Dell Inc. Vostro 200 ProcCmdLine: root=UUID=612943a2-c964-401b-95b5-5de3264a6a64 ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg Symptom: display dmi.bios.date: 06/23/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.15 dmi.board.name: 0CU409 dmi.board.vendor: Dell Inc. dmi.board.version: ��� dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.15:bd06/23/2008:svnDellInc.:pnVostro200:pvr:rvnDellInc.:rn0CU409:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Vostro 200 dmi.sys.vendor: Dell Inc. system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-22-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/578460/+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 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
Martin, I am seeing this regularly under Unity. Smells like a race condition to me. -- 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/1184262 Title: [logind] stuck in PrepareForSleep, causing network and other services to not resume Status in “network-manager” package in Ubuntu: Confirmed Status in “systemd” package in Ubuntu: Incomplete Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
What component is *supposed* to be sending it that signal? I have noticed that in cases where this bug appears, other power management options also fail - trying to suspend again from the gear menu does nothing, I have to run pm-suspend from the cli. This indicates to me that some whole underlying subsystem is getting confused, and that other components may also need to be kicked - NetworkManager is just the most obvious one people notice right away. -- 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/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
Yes, looks like a dupe. -- 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/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
First I ran sudo stop network-manager then ran sudo NetworkManager --no-daemon --log-level=DEBUG nm.log 21 and then I reproduced the issue. I have attached the complete log output of network-manager from the initial receive of the suspend signal to the point I ctrl-C'ed it after experiencing this bug. For context, this system has two ethernet ports (eth0, eth1) that had no attached cable during the experiment, and one atheros wifi card (wlan0) which was connected. Hopefully something in here (or the lack of something in here) will be helpful. ** Attachment added: Network Manager Log Output https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+attachment/3855681/+files/nm.log -- 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/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
Interesting, so it's not even a NetworkManager bug - whatever is supposed to be sending that signal to nm isn't sending it sometimes, or is sending it before nm can receive it or something? -- 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/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1184262] Re: network-manager has decided that networking is disabled, cannot be re-enabled from lightdm
I still see this fairly frequently, and it is strictly a network-manager problem. sudo restart network-manager causes it to reconnect gracefully without any problems or kernel magic. I suspect a race condition, since it only happens about 1/3 of the time I suspend. FWIW, I have a totally different network card (atheros). -- 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/1184262 Title: network-manager has decided that networking is disabled, cannot be re- enabled from lightdm Status in “network-manager” package in Ubuntu: Confirmed Bug description: After a suspend/resume, network-manager claimed that wireless was not available and would not let me reconnect to the wireless here. 'iwlist wlan1 scan' would also not work; so thinking that it was a driver problem, I rebooted the system. When it came back up, nm- applet in lightdm claimed that networking was disabled, and the option to enable it was greyed out. It could also not be enabled by nmcli. I ended up stopping network-manager, bringing up the interface via /etc/network/interfaces, and logging in... at which point, restarting network-manager *did* let me enable networking from my logged-in session. So there are several problems here: - after a reboot, network-manager claimed networking was disabled. - nm-applet is not letting me enable networking from the lightdm session. - the networking was failing after a suspend/resume cycle, and could not be enabled even from inside the user session. The last issue probably *was* a kernel driver problem; but the first two issues are network-manager problems of some kind. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: network-manager 0.9.8.0-0ubuntu8 ProcVersionSignature: Ubuntu 3.9.0-2.7-generic 3.9.3 Uname: Linux 3.9.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu1 Architecture: amd64 Date: Sat May 25 21:38:31 2013 InstallationDate: Installed on 2010-09-24 (974 days ago) InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) IpRoute: default via 192.168.1.1 dev wlan1 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.106 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=false WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to saucy on 2013-05-06 (19 days ago) WifiSyslog: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 9: ** (process:11977): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: The name org.freedesktop.NetworkManager was not provided by any .service files Error: nmcli (0.9.8.0) and NetworkManager (unknown) versions don't match. Force execution using --nocheck, but the results are unpredictable. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN not running unknownunknown unknown unknown unknownunknown unknown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1184262/+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 1045353] Re: Commands are not displayed in the HUD
Still exists on latest Raring, for what it's worth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1045353 Title: Commands are not displayed in the HUD Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Ubuntu Release: Ubuntu 12.10 Quantal Quetzal beta1 Package version: libreoffice-gtk Package version: 1:3.6.1~rc2-1ubuntu3 Expected behavior: It should be possible to launch LO actions from the HUD. Actual behavior: Libreoffice commands are not shown in the HUD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1045353/+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 965895] Re: After boot, NetworkManager indicator menu only shows four entries
The similar (identical?) dropbox bug has just been fixed in the latest stable dropbox [1]. Perhaps it's worth pinging them to ask what they changed? [1] https://www.dropbox.com/release_notes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/965895 Title: After boot, NetworkManager indicator menu only shows four entries Status in “network-manager-applet” package in Ubuntu: In Progress Status in “network-manager-applet” source package in Precise: In Progress Status in “network-manager-applet” source package in Quantal: In Progress Bug description: After I boot in to the LiveCD environment for Ubuntu 12.04, I click on the NetworkManager icon in the top-right of the screen and it's only showing four items: -- | ✓ Enable Networking | ✓ Enable Wireless | -- | | Connection Information | Edit Connections... -- If I then select the Enable Networking or Enable Wireless option to disable that interface and then re-enable it, then the NetworkManager populates with all the normal menu items (listing of all WiFi SSID, VPN connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 03:23:48 2012 IfupdownConfig: auto lo iface lo inet loopback LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/965895/+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 965895] Re: After boot, NetworkManager indicator menu only shows four entries
Hi Kevin, please don't change the status of the bug without providing an explanation, and please don't assign the bug to yourself unless you plan to provide a fix. Thanks, Evan ** Changed in: libindicate (Ubuntu) Status: Incomplete = Confirmed ** Changed in: libindicate (Ubuntu) Assignee: kevin roussel (kroussel2) = (unassigned) ** Changed in: network-manager (Ubuntu) Status: Incomplete = Confirmed ** Changed in: network-manager (Ubuntu) Assignee: kevin roussel (kroussel2) = (unassigned) -- 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/965895 Title: After boot, NetworkManager indicator menu only shows four entries Status in Libindicate: New Status in “libindicate” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: After I boot in to the LiveCD environment for Ubuntu 12.04, I click on the NetworkManager icon in the top-right of the screen and it's only showing four items: -- | ✓ Enable Networking | ✓ Enable Wireless | -- | | Connection Information | Edit Connections... -- If I then select the Enable Networking or Enable Wireless option to disable that interface and then re-enable it, then the NetworkManager populates with all the normal menu items (listing of all WiFi SSID, VPN connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 03:23:48 2012 IfupdownConfig: auto lo iface lo inet loopback LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/965895/+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 965895] Re: After boot, NetworkManager indicator menu only shows four entries
I am seeing a very similar issue with the Dropbox indicator applet, and after much experimentation I believe both issues (network-manager and dropbox) are caused by a race condition within libindicate itself. I have opened a libindicate task for this bug, hopefully someone from that project will take a look. ** Also affects: libindicate (Ubuntu) Importance: Undecided Status: New -- 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/965895 Title: After boot, NetworkManager indicator menu only shows four entries Status in Libindicate: New Status in “libindicate” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: After I boot in to the LiveCD environment for Ubuntu 12.04, I click on the NetworkManager icon in the top-right of the screen and it's only showing four items: -- | ✓ Enable Networking | ✓ Enable Wireless | -- | | Connection Information | Edit Connections... -- If I then select the Enable Networking or Enable Wireless option to disable that interface and then re-enable it, then the NetworkManager populates with all the normal menu items (listing of all WiFi SSID, VPN connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 03:23:48 2012 IfupdownConfig: auto lo iface lo inet loopback LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/965895/+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 965895] Re: After boot, NetworkManager indicator menu only shows four entries
** Also affects: libindicate Importance: Undecided Status: New -- 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/965895 Title: After boot, NetworkManager indicator menu only shows four entries Status in Libindicate: New Status in “libindicate” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: After I boot in to the LiveCD environment for Ubuntu 12.04, I click on the NetworkManager icon in the top-right of the screen and it's only showing four items: -- | ✓ Enable Networking | ✓ Enable Wireless | -- | | Connection Information | Edit Connections... -- If I then select the Enable Networking or Enable Wireless option to disable that interface and then re-enable it, then the NetworkManager populates with all the normal menu items (listing of all WiFi SSID, VPN connection, etc.). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.3.995+git201203152001.04b2a74-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 ApportVersion: 1.95-0ubuntu1 Architecture: amd64 CasperVersion: 1.312 Date: Tue Mar 27 03:23:48 2012 IfupdownConfig: auto lo iface lo inet loopback LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120325) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libindicate/+bug/965895/+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 981628] Re: Changing HUD key from 'Alt' to 'Alt' changes behaviour when numlock is on
With Numlock Off: --- KeyPress event, serial 36, synthetic NO, window 0x421, root 0xbd, subw 0x0, time 542002, (434,589), root:(488,641), state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0xbd, subw 0x0, time 542098, (434,589), root:(488,641), state 0x8, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False --- With Numlock On: --- KeyPress event, serial 36, synthetic NO, window 0x421, root 0xbd, subw 0x0, time 608978, (1048,476), root:(1102,528), state 0x10, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 36, synthetic NO, window 0x421, root 0xbd, subw 0x0, time 609082, (1048,476), root:(1102,528), state 0x18, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False --- The only difference I can see is the extra bit set in the value of 'state'. Just to be sure, I reran my steps, and I can still reproduce the problem on a clean reboot. My keyboard is a Dell USB model. I've attached the relevant output of lsusb in case it matters. --- Bus 005 Device 002: ID 413c:1004 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass9 Hub bDeviceSubClass 0 Unused bDeviceProtocol 0 Full speed (or root) hub bMaxPacketSize0 8 idVendor 0x413c Dell Computer Corp. idProduct 0x1004 bcdDevice 48.01 iManufacturer 1 Dell iProduct2 Dell USB Keyboard Hub iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 25 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 2 Dell USB Keyboard Hub bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 Unused bInterfaceProtocol 0 Full speed (or root) hub iInterface 2 Dell USB Keyboard Hub Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0001 1x 1 bytes bInterval 24 Hub Descriptor: bLength 9 bDescriptorType 41 nNbrPorts 3 wHubCharacteristic 0x000d Per-port power switching Compound device Per-port overcurrent protection bPwrOn2PwrGood 22 * 2 milli seconds bHubContrCurrent100 milli Ampere DeviceRemovable0x02 PortPwrCtrlMask0xff Hub Port Status: Port 1: .0303 lowspeed power enable connect Port 2: .0100 power Port 3: .0100 power Device Status: 0x (Bus Powered) Bus 005 Device 003: ID 413c:2006 Dell Computer Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x413c Dell Computer Corp. idProduct 0x2006 bcdDevice 48.00 iManufacturer 1 Dell iProduct2 Dell USB Keyboard Hub iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 59 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 3 83NT6504V110 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 90mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints
[Desktop-packages] [Bug 981628] Re: Changing HUD key from 'Alt' to 'Alt' changes behaviour
** Also affects: gnome-control-center Importance: Undecided Status: New ** Project changed: gnome-control-center = gnome-control-center (Ubuntu) ** Description changed: - (This perhaps should be against gnome-control-center instead of unity?) + Problem is likely in 54_enable_alt_tap_in_shortcut.patch in gnome- + control-center. 1. Initially, note that both HUD (using left alt) and window management menu (using alt-space) work properly. The HUD shortcut in Keyboard Settings is listed as Alt L. 2. Click on the setting to change it, and tap the left alt key. 3. The shortcut now reads as Mod2 + Alt L (note the addition of the Mod2). The HUD is still assigned to left alt, but using alt-space now *also* brings up the HUD, and not the window management menu like it should. CCSM can be used to restore the correct shortcut. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 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: Sat Apr 14 10:15:00 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2011-11-26 (140 days ago) ** Changed in: unity (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/981628 Title: Changing HUD key from 'Alt' to 'Alt' changes behaviour Status in “gnome-control-center” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: Problem is likely in 54_enable_alt_tap_in_shortcut.patch in gnome- control-center. 1. Initially, note that both HUD (using left alt) and window management menu (using alt-space) work properly. The HUD shortcut in Keyboard Settings is listed as Alt L. 2. Click on the setting to change it, and tap the left alt key. 3. The shortcut now reads as Mod2 + Alt L (note the addition of the Mod2). The HUD is still assigned to left alt, but using alt-space now *also* brings up the HUD, and not the window management menu like it should. CCSM can be used to restore the correct shortcut. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 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: Sat Apr 14 10:15:00 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2011-11-26 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/981628/+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 981628] Re: Changing HUD key from 'Alt' to 'Alt' changes behaviour when numlock is on
Seems related to this: http://projects.comum.org/guake/ticket/76 ** Summary changed: - Changing HUD key from 'Alt' to 'Alt' changes behaviour + Changing HUD key from 'Alt' to 'Alt' changes behaviour when numlock is on ** Description changed: - Problem is likely in 54_enable_alt_tap_in_shortcut.patch in gnome- - control-center. - 1. Initially, note that both HUD (using left alt) and window management menu (using alt-space) work properly. The HUD shortcut in Keyboard Settings is listed as Alt L. - 2. Click on the setting to change it, and tap the left alt key. - 3. The shortcut now reads as Mod2 + Alt L (note the addition of the Mod2). The HUD is still assigned to left alt, but using alt-space now *also* brings up the HUD, and not the window management menu like it should. + 2. Make sure your keyboard's numlock is on. + 3. Click on the setting to change it, and tap the left alt key. + 4. The shortcut now reads as Mod2 + Alt L (note the addition of the Mod2). The HUD is still assigned to left alt, but using alt-space now *also* brings up the HUD, and not the window management menu like it should. CCSM can be used to restore the correct shortcut. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 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: Sat Apr 14 10:15:00 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2011-11-26 (140 days ago) ** Bug watch added: projects.comum.org/guake/ #76 http://projects.comum.org/guake/ticket/76 -- 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/981628 Title: Changing HUD key from 'Alt' to 'Alt' changes behaviour when numlock is on Status in “gnome-control-center” package in Ubuntu: New Status in “unity” package in Ubuntu: Invalid Bug description: 1. Initially, note that both HUD (using left alt) and window management menu (using alt-space) work properly. The HUD shortcut in Keyboard Settings is listed as Alt L. 2. Make sure your keyboard's numlock is on. 3. Click on the setting to change it, and tap the left alt key. 4. The shortcut now reads as Mod2 + Alt L (note the addition of the Mod2). The HUD is still assigned to left alt, but using alt-space now *also* brings up the HUD, and not the window management menu like it should. CCSM can be used to restore the correct shortcut. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: unity 5.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu2 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 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: Sat Apr 14 10:15:00 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: unity UpgradeStatus: Upgraded to precise on 2011-11-26 (140 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/981628/+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 926940] [NEW] Visio files not associated with LibreOffice Draw
Public bug reported: Since 3.5 (planned for Precise), LO has an import filter for MS Visio files (.VSD) [1]. Those files currently have no default association with any application, so it would be a major usability improvement to have them open in LO by default. Filing against LO because I'm not sure what package controls default file associations. [1] http://wiki.documentfoundation.org/ReleaseNotes/3.5#Filters ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Sat Feb 4 17:46:40 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-01-14 (21 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise running-unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/926940 Title: Visio files not associated with LibreOffice Draw Status in “libreoffice” package in Ubuntu: New Bug description: Since 3.5 (planned for Precise), LO has an import filter for MS Visio files (.VSD) [1]. Those files currently have no default association with any application, so it would be a major usability improvement to have them open in LO by default. Filing against LO because I'm not sure what package controls default file associations. [1] http://wiki.documentfoundation.org/ReleaseNotes/3.5#Filters ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Sat Feb 4 17:46:40 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-01-14 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/926940/+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 926940] Re: Visio files not associated with LibreOffice Draw
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/926940 Title: Visio files not associated with LibreOffice Draw Status in “libreoffice” package in Ubuntu: New Bug description: Since 3.5 (planned for Precise), LO has an import filter for MS Visio files (.VSD) [1]. Those files currently have no default association with any application, so it would be a major usability improvement to have them open in LO by default. Filing against LO because I'm not sure what package controls default file associations. [1] http://wiki.documentfoundation.org/ReleaseNotes/3.5#Filters ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 3.2.0-12.21-generic 3.2.2 Uname: Linux 3.2.0-12-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 CheckboxSubmission: e049aa43e015d38fc2b288a8a60db142 CheckboxSystem: 2a6f54df59af338184485e85cbcf0d32 Date: Sat Feb 4 17:46:40 2012 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-01-14 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/926940/+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 891440] Re: evince crashed with SIGSEGV in xcb_get_extension_data()
Do input devices automatically un-register and re-register on suspend/resume then? I don't have to attach or detach any devices when I reproduce the issue... -- 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/891440 Title: evince crashed with SIGSEGV in xcb_get_extension_data() Status in uTouch-geis: New Status in “evince” package in Ubuntu: Confirmed Bug description: dunno why it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.1.0-3.3-generic 3.1.0 Uname: Linux 3.1.0-3-generic x86_64 ApportVersion: 1.26-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Nov 16 16:42:49 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.1.0-3-generic root=/dev/mapper/hostname-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe18c9a65ab xcb_get_extension_data+27:mov (%rdi),%ecx PC (0x7fe18c9a65ab) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: xcb_get_extension_data () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libutouch-geis.so.1 geis_event_dispatch () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libgrip.so.0 Title: evince crashed with SIGSEGV in xcb_get_extension_data() UpgradeStatus: Upgraded to precise on 2011-11-08 (8 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/utouch-geis/+bug/891440/+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 891440] Re: evince crashed with SIGSEGV in xcb_get_extension_data()
I just reproduced this using the same method as I describe in comment #6. The system is fully up-to-date Precise as of the posting of this comment. ** Changed in: utouch-geis Status: Incomplete = New -- 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/891440 Title: evince crashed with SIGSEGV in xcb_get_extension_data() Status in uTouch-geis: New Status in “evince” package in Ubuntu: Confirmed Bug description: dunno why it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.1.0-3.3-generic 3.1.0 Uname: Linux 3.1.0-3-generic x86_64 ApportVersion: 1.26-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Nov 16 16:42:49 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.1.0-3-generic root=/dev/mapper/hostname-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe18c9a65ab xcb_get_extension_data+27:mov (%rdi),%ecx PC (0x7fe18c9a65ab) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: xcb_get_extension_data () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libutouch-geis.so.1 geis_event_dispatch () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libgrip.so.0 Title: evince crashed with SIGSEGV in xcb_get_extension_data() UpgradeStatus: Upgraded to precise on 2011-11-08 (8 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/utouch-geis/+bug/891440/+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 891440] Re: evince crashed with SIGSEGV in xcb_get_extension_data()
I reproduced the crash while running under gdb and captured a full core file. The attached file contains the test pdf I used (unlikely to be important, but better safe than sorry) and the xz-compressed core file. The problem has, to date, been %100 reproducible on demand, so if there's any other information you need just ask. ** Attachment added: Test pdf and full gdb core file. https://bugs.launchpad.net/utouch-geis/+bug/891440/+attachment/2676605/+files/evince.tar -- 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/891440 Title: evince crashed with SIGSEGV in xcb_get_extension_data() Status in uTouch-geis: New Status in “evince” package in Ubuntu: Confirmed Bug description: dunno why it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.1.0-3.3-generic 3.1.0 Uname: Linux 3.1.0-3-generic x86_64 ApportVersion: 1.26-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Nov 16 16:42:49 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.1.0-3-generic root=/dev/mapper/hostname-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe18c9a65ab xcb_get_extension_data+27:mov (%rdi),%ecx PC (0x7fe18c9a65ab) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: xcb_get_extension_data () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libutouch-geis.so.1 geis_event_dispatch () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libgrip.so.0 Title: evince crashed with SIGSEGV in xcb_get_extension_data() UpgradeStatus: Upgraded to precise on 2011-11-08 (8 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/utouch-geis/+bug/891440/+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 891440] Re: evince crashed with SIGSEGV in xcb_get_extension_data()
I experienced this bug immediately after resuming from suspend. I had two documents open in evince, one semi-maximized to the left side of the screen and one semi-maximized to the right side of the screen. Both documents crashed before I had interacted with them at all. -- 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/891440 Title: evince crashed with SIGSEGV in xcb_get_extension_data() Status in “evince” package in Ubuntu: Confirmed Bug description: dunno why it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.1.0-3.3-generic 3.1.0 Uname: Linux 3.1.0-3-generic x86_64 ApportVersion: 1.26-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Nov 16 16:42:49 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.1.0-3-generic root=/dev/mapper/hostname-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe18c9a65ab xcb_get_extension_data+27:mov (%rdi),%ecx PC (0x7fe18c9a65ab) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: xcb_get_extension_data () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libutouch-geis.so.1 geis_event_dispatch () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libgrip.so.0 Title: evince crashed with SIGSEGV in xcb_get_extension_data() UpgradeStatus: Upgraded to precise on 2011-11-08 (8 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/891440/+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 891440] Re: evince crashed with SIGSEGV in xcb_get_extension_data()
Based on an examination of the stack trace and some of the referenced code, I believe this to be a bug in libutouch-geis and not necessarily evince. I have opened a utouch-geis task for this bug so that the utouch devs can take a look. ** Also affects: utouch-geis Importance: Undecided Status: New -- 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/891440 Title: evince crashed with SIGSEGV in xcb_get_extension_data() Status in uTouch-geis: New Status in “evince” package in Ubuntu: Confirmed Bug description: dunno why it crashed. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: evince 3.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.1.0-3.3-generic 3.1.0 Uname: Linux 3.1.0-3-generic x86_64 ApportVersion: 1.26-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Nov 16 16:42:49 2011 ExecutablePath: /usr/bin/evince InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.1.0-3-generic root=/dev/mapper/hostname-root ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe18c9a65ab xcb_get_extension_data+27:mov (%rdi),%ecx PC (0x7fe18c9a65ab) ok source (%rdi) (0x0021) not located in a known VMA region (needed readable region)! destination %ecx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: evince StacktraceTop: xcb_get_extension_data () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libutouch-geis.so.1 geis_event_dispatch () from /usr/lib/libutouch-geis.so.1 ?? () from /usr/lib/libgrip.so.0 Title: evince crashed with SIGSEGV in xcb_get_extension_data() UpgradeStatus: Upgraded to precise on 2011-11-08 (8 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src To manage notifications about this bug go to: https://bugs.launchpad.net/utouch-geis/+bug/891440/+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 811049] Re: gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try()
Just experienced this on the latest Precise when unplugging (not unmounting or ejecting) an iPod with iOS 5. -- 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/811049 Title: gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try() Status in GVFS: New Status in “gvfs” package in Ubuntu: Triaged Status in “gvfs” source package in Oneiric: Triaged Bug description: no extra information ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gvfs-backends 1.9.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5 Uname: Linux 3.0-3-generic i686 Architecture: i386 Date: Fri Jul 15 16:39:13 2011 Disassembly: = 0x0: Cannot access memory at address 0x0 ExecutablePath: /usr/lib/gvfs/gvfsd-ftp InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Alpha i386 (20110705) ProcCmdline: /usr/lib/gvfs/gvfsd-ftp --spawner :1.1 /org/gtk/gvfs/exec_spaw/3 ProcEnviron: SHELL=/bin/bash LANGUAGE=ru_UA:ru LANG=ru_UA.UTF-8 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: gvfs StacktraceTop: ?? () ?? () from /usr/lib/gvfs/libgvfsdaemon.so g_vfs_job_try () from /usr/lib/gvfs/libgvfsdaemon.so g_vfs_daemon_queue_job () from /usr/lib/gvfs/libgvfsdaemon.so ?? () from /usr/lib/gvfs/libgvfsdaemon.so Title: gvfsd-ftp crashed with SIGSEGV in g_vfs_job_try() 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/gvfs/+bug/811049/+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 899974] Re: software-center crashed with SIGSEGV in PyGILState_Ensure()
*** This bug is a duplicate of bug 767361 *** https://bugs.launchpad.net/bugs/767361 ** This bug has been marked a duplicate of bug 767361 software-center crashed with SIGSEGV in PyGILState_Ensure() -- 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/899974 Title: software-center crashed with SIGSEGV in PyGILState_Ensure() Status in “software-center” package in Ubuntu: New Bug description: Crash ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: software-center 5.1.3 ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3 Uname: Linux 3.2.0-2-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 CasperVersion: 1.292 Date: Sun Dec 4 17:08:06 2011 ExecutablePath: /usr/share/software-center/software-center InterpreterPath: /usr/bin/python2.7 LiveMediaBuild: Ubuntu 12.04 LTS Precise Pangolin - Alpha i386 (20111204) PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x8119f70: mov0x4(%ebx),%edx PC (0x08119f70) ok source 0x4(%ebx) (0x0004) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: software-center StacktraceTop: ?? () PyGILState_Ensure () pyglib_gil_state_ensure () from /usr/lib/libpyglib-gi-2.0-python2.7.so.0 ?? () from /usr/lib/python2.7/dist-packages/gi/_gobject/_gobject.so g_datalist_clear () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: software-center crashed with SIGSEGV in PyGILState_Ensure() 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/software-center/+bug/899974/+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 900021] Re: software-center crashed with SIGSEGV in PyGILState_Ensure()
*** This bug is a duplicate of bug 767361 *** https://bugs.launchpad.net/bugs/767361 ** This bug has been marked a duplicate of bug 767361 software-center crashed with SIGSEGV in PyGILState_Ensure() -- 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/900021 Title: software-center crashed with SIGSEGV in PyGILState_Ensure() Status in “software-center” package in Ubuntu: Confirmed Bug description: Even when it doesn't crash, Software Center is very slow to load. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: software-center 5.1.3 ProcVersionSignature: Ubuntu 3.2.0-2.6-generic 3.2.0-rc3 Uname: Linux 3.2.0-2-generic i686 ApportVersion: 1.90-0ubuntu1 Architecture: i386 Date: Mon Dec 5 08:49:03 2011 ExecutablePath: /usr/share/software-center/software-center InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release i386 (20111011) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/software-center ProcEnviron: LANGUAGE=en_NZ:en PATH=(custom, no user) LANG=en_NZ.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x8119f70: mov0x4(%ebx),%edx PC (0x08119f70) ok source 0x4(%ebx) (0x0004) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: software-center StacktraceTop: ?? () PyGILState_Ensure () pyglib_gil_state_ensure () from /usr/lib/libpyglib-gi-2.0-python2.7.so.0 ?? () from /usr/lib/python2.7/dist-packages/gi/_gobject/_gobject.so g_datalist_clear () from /lib/i386-linux-gnu/libglib-2.0.so.0 Title: software-center crashed with SIGSEGV in PyGILState_Ensure() 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/software-center/+bug/900021/+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 869603] [NEW] Remove Profile button clickable in Color panel when no profile selected
Public bug reported: Originally reported as a crasher in bug #853349. The crasher was fixed, so opening a new bug for the UI problem as per request. Steps to reproduce: 1. Open the Color applet and select a device. 2. Click Add Profile and then Add (it doesn't matter which profile you add). The new profile should be the one whose radio button is selected. 3. Click on the new, selected profile and click Remove Profile The original, default profile should now have its radio button selected, but the element itself does not have focus. The Remove Profile button is still clickable, even though none of the profiles have focus. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Oct 6 19:23:12 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu1 indicator-datetime 0.3.0-0ubuntu3 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug oneiric running-unity -- 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/869603 Title: Remove Profile button clickable in Color panel when no profile selected Status in “gnome-control-center” package in Ubuntu: New Bug description: Originally reported as a crasher in bug #853349. The crasher was fixed, so opening a new bug for the UI problem as per request. Steps to reproduce: 1. Open the Color applet and select a device. 2. Click Add Profile and then Add (it doesn't matter which profile you add). The new profile should be the one whose radio button is selected. 3. Click on the new, selected profile and click Remove Profile The original, default profile should now have its radio button selected, but the element itself does not have focus. The Remove Profile button is still clickable, even though none of the profiles have focus. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Oct 6 19:23:12 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu1 indicator-datetime 0.3.0-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/869603/+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 869603] Re: Remove Profile button clickable in Color panel when no profile selected
-- 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/869603 Title: Remove Profile button clickable in Color panel when no profile selected Status in “gnome-control-center” package in Ubuntu: New Bug description: Originally reported as a crasher in bug #853349. The crasher was fixed, so opening a new bug for the UI problem as per request. Steps to reproduce: 1. Open the Color applet and select a device. 2. Click Add Profile and then Add (it doesn't matter which profile you add). The new profile should be the one whose radio button is selected. 3. Click on the new, selected profile and click Remove Profile The original, default profile should now have its radio button selected, but the element itself does not have focus. The Remove Profile button is still clickable, even though none of the profiles have focus. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Thu Oct 6 19:23:12 2011 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110921.2) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 20.0-0ubuntu3 gnome-bluetooth3.2.0-0ubuntu1 indicator-datetime 0.3.0-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/869603/+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 853349] Re: gnome-control-center crashed with SIGABRT in gcm_prefs_profile_remove_cb()
New bug opened as per request: bug #869603. -- 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/853349 Title: gnome-control-center crashed with SIGABRT in gcm_prefs_profile_remove_cb() Status in GNOME Control Center: New Status in “gnome-control-center” package in Ubuntu: Fix Released Bug description: Was playing around with Colour Management, and somehow the Remove Profile button ended up active even though no profile was selected. Clicking the button resulted in this crash. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sun Sep 18 12:16:04 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcCmdline: gnome-control-center ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __kernel_vsyscall () 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 ?? () from /usr/lib/control-center-1/panels/libcolor.so Title: gnome-control-center crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: Upgraded to oneiric on 2011-08-12 (36 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: deja-dup 19.92-0ubuntu1 empathy3.1.91-0ubuntu2 gnome-bluetooth3.1.4-0ubuntu2 indicator-datetime 0.2.95-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/853349/+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 853349] Re: gnome-control-center crashed with SIGABRT in gcm_prefs_profile_remove_cb()
Still partially an issue. I am able to get the Remove Profile button active even though no profile is selected, however pressing it now seems safe. Somebody added a NULL check somewhere without fixing the root cause :) Steps to reproduce: 1. Open the Color applet and select a device. 2. Click Add Profile and then Add (it doesn't matter which profile you add). The new profile should be the one whose radio button is selected. 3. Click on the new, selected profile and click Remove Profile The original, default profile should now have its radio button selected, but the element itself does not have focus. The Remove Profile button is still clickable, even though none of the profiles have focus. Importance should be Minor, as this has gone from a crasher to a minor UI inconsistency. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete = New -- 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/853349 Title: gnome-control-center crashed with SIGABRT in gcm_prefs_profile_remove_cb() Status in “gnome-control-center” package in Ubuntu: New Bug description: Was playing around with Colour Management, and somehow the Remove Profile button ended up active even though no profile was selected. Clicking the button resulted in this crash. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.91-0ubuntu8 ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Sun Sep 18 12:16:04 2011 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) ProcCmdline: gnome-control-center ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANGUAGE=en_CA:en LANG=en_CA.UTF-8 Signal: 6 SourcePackage: gnome-control-center StacktraceTop: __kernel_vsyscall () 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 ?? () from /usr/lib/control-center-1/panels/libcolor.so Title: gnome-control-center crashed with SIGABRT in __kernel_vsyscall() UpgradeStatus: Upgraded to oneiric on 2011-08-12 (36 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: deja-dup 19.92-0ubuntu1 empathy3.1.91-0ubuntu2 gnome-bluetooth3.1.4-0ubuntu2 indicator-datetime 0.2.95-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/853349/+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 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
I've scanned through a whole bunch of the duplicates for this bug. Every single one of them has ecryptfs enabled, and several of them mention being low-ram at the time of the crash. With those two requirements in mind, I'm currently creating a low-memory Natty VM that uses ecryptfs. Assuming I can easily reproduce the problem there, I'll upgrade the VM to Oneiric and try again. I'll report any progress back here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() Status in LibreOffice Productivity Suite: New Status in “libreoffice” package in Ubuntu: Confirmed Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in KDE Natty in a KDE session with the KDE integration active or GNOME is a Writer or Calc file untouched for a long period of time (ex. 1 hour+) is when one tries to edit it, the application does not crash. 4) What happens instead is it crashes. Occurs with: + Intel drivers, Compiz not enabled, Writer open only bug 745836 + binary ATI drivers, Compiz enabled, Calc open only bug 799047 WORKAROUND: Use Gnumeric. apt-cache policy gnumeric gnumeric: Installed: 1.10.13-1ubuntu1 Candidate: 1.10.13-1ubuntu1 Version table: *** 1.10.13-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Wed Mar 30 12:34:39 2011 Disassembly: = 0x10: Cannot access memory at address 0x10 EcryptfsInUse: Yes ExecutablePath: /usr/lib/libreoffice/program/soffice.bin ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer -splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x10: Cannot access memory at address 0x10 PC (0x0010) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () cppu::throwException(com::sun::star::uno::Any const) () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3 ucbhelper::cancelCommandExecution(com::sun::star::ucb::IOErrorCode, com::sun::star::uno::Sequencecom::sun::star::uno::Any const, com::sun::star::uno::Referencecom::sun::star::ucb::XCommandEnvironment const, rtl::OUString const, com::sun::star::uno::Referencecom::sun::star::ucb::XCommandProcessor const) () from /usr/lib/libreoffice/program/../basis-link/program/libucbhelper4gcc3.so ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so Title: soffice.bin crashed with SIGSEGV in cppu::throwException() UpgradeStatus: Upgraded to natty on 2011-03-29 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/745836/+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 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
Success! I can easily and quickly reproduce the problem in Natty. It isn't a time-related issue at all, simply resource-related. Setup: On Virtualbox 4.1.2, create a 32-bit Ubuntu VM with low memory (472MB in my case). Make sure your virtual hard-drive is at least 12GB so that Ubuntu allocates enough swap space to pull this off. Install 11.04 from CD and install all updates, then reboot. Vista-32 host if that makes any difference (which I doubt). Steps to reproduce: Open up LO writer, type a few words and save the file to disk. Leave the doc open, but minimized or otherwise inactive. Open up every other app you can think of. System Monitor reported 200MB swapped for me. Go back to LO and type a mis-spelled word, followed by a space. Wait until the disk stops churning. LO has crashed with this bug. Once set up, it takes me less than ten minutes to produce another instance. I stayed on the safe side and tried to replicate the most extreme of all reported conditions. It's likely that some of the steps I list are not actually required to reproduce this, but narrowing it down will take time. I am currently upgrading the VM to oneiric to determine whether or not this is still an issue there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() Status in LibreOffice Productivity Suite: New Status in “libreoffice” package in Ubuntu: Confirmed Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in a KDE Natty in a KDE session with the KDE integration active or GNOME is a Writer or Calc file untouched for a long period of time (ex. 1 hour+) is when one tries to edit it, the application does not crash. 4) What happens instead is it crashes. This is highly correlated to both EcryptfsInUse and resource constrained (Memory CPU 50%) environments. Occurs with: + Intel drivers, Compiz not enabled, Writer open only bug 745836 + binary ATI drivers, Compiz enabled, Calc open only bug 799047 WORKAROUND: Use Gnumeric. apt-cache policy gnumeric gnumeric: Installed: 1.10.13-1ubuntu1 Candidate: 1.10.13-1ubuntu1 Version table: *** 1.10.13-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Wed Mar 30 12:34:39 2011 Disassembly: = 0x10: Cannot access memory at address 0x10 EcryptfsInUse: Yes ExecutablePath: /usr/lib/libreoffice/program/soffice.bin ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer -splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x10: Cannot access memory at address 0x10 PC (0x0010) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () cppu::throwException(com::sun::star::uno::Any const) () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3 ucbhelper::cancelCommandExecution(com::sun::star::ucb::IOErrorCode, com::sun::star::uno::Sequencecom::sun::star::uno::Any const, com::sun::star::uno::Referencecom::sun::star::ucb::XCommandEnvironment const, rtl::OUString const, com::sun::star::uno::Referencecom::sun::star::ucb::XCommandProcessor const) () from /usr/lib/libreoffice/program/../basis-link/program/libucbhelper4gcc3.so ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so Title: soffice.bin crashed with SIGSEGV in
[Desktop-packages] [Bug 745836] Re: soffice.bin crashed with SIGSEGV in cppu::throwException()
Something I missed in my previous comment: I selected the encrypted home option while installing Ubuntu in the VM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/745836 Title: soffice.bin crashed with SIGSEGV in cppu::throwException() Status in LibreOffice Productivity Suite: New Status in “libreoffice” package in Ubuntu: Confirmed Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: Binary package hint: libreoffice 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-calc libreoffice-calc: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.3-1ubuntu2 Candidate: 1:3.3.3-1ubuntu2 Version table: *** 1:3.3.3-1ubuntu2 0 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in a KDE Natty in a KDE session with the KDE integration active or GNOME is a Writer or Calc file untouched for a long period of time (ex. 1 hour+) is when one tries to edit it, the application does not crash. 4) What happens instead is it crashes. This is highly correlated to both EcryptfsInUse and resource constrained (Memory CPU 50%) environments. Occurs with: + Intel drivers, Compiz not enabled, Writer open only bug 745836 + binary ATI drivers, Compiz enabled, Calc open only bug 799047 WORKAROUND: Use Gnumeric. apt-cache policy gnumeric gnumeric: Installed: 1.10.13-1ubuntu1 Candidate: 1.10.13-1ubuntu1 Version table: *** 1.10.13-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: libreoffice-core 1:3.3.2-1ubuntu2 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic i686 Architecture: i386 Date: Wed Mar 30 12:34:39 2011 Disassembly: = 0x10: Cannot access memory at address 0x10 EcryptfsInUse: Yes ExecutablePath: /usr/lib/libreoffice/program/soffice.bin ProcCmdline: /usr/lib/libreoffice/program/soffice.bin -writer -splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x10: Cannot access memory at address 0x10 PC (0x0010) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () cppu::throwException(com::sun::star::uno::Any const) () from /usr/lib/libreoffice/program/../basis-link/program/../ure-link/lib/libuno_cppuhelpergcc3.so.3 ucbhelper::cancelCommandExecution(com::sun::star::ucb::IOErrorCode, com::sun::star::uno::Sequencecom::sun::star::uno::Any const, com::sun::star::uno::Referencecom::sun::star::ucb::XCommandEnvironment const, rtl::OUString const, com::sun::star::uno::Referencecom::sun::star::ucb::XCommandProcessor const) () from /usr/lib/libreoffice/program/../basis-link/program/libucbhelper4gcc3.so ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so ?? () from /usr/lib/libreoffice/program/../basis-link/program/libucpfile1.so Title: soffice.bin crashed with SIGSEGV in cppu::throwException() UpgradeStatus: Upgraded to natty on 2011-03-29 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/745836/+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 744802] Re: empathy crashed with SIGSEGV in g_strdup()
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are very sorry that we do not always have the capacity to look at all reported bugs in a timely manner. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. --- Evan Huus Ubuntu Bug Squad Volunteer https://wiki.ubuntu.com/BugSquad ** Changed in: empathy (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to empathy in Ubuntu. https://bugs.launchpad.net/bugs/744802 Title: empathy crashed with SIGSEGV in g_strdup() Status in “empathy” package in Ubuntu: Incomplete Bug description: Binary package hint: empathy Happens to me multiple times a day with latest Ubuntu Natty installation. Latest was when Google Talk would not connect and I clicked on the edit settings in the notification bar in the main window ProblemType: Crash DistroRelease: Ubuntu 11.04 Package: empathy 2.33.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 NonfreeKernelModules: nvidia wl Architecture: amd64 Date: Tue Mar 29 09:43:53 2011 ExecutablePath: /usr/bin/empathy InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20110302) ProcCmdline: empathy -h ProcEnviron: LANGUAGE=en_US:en LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f9f31a255d1:movdqu (%rdi),%xmm1 PC (0x7f9f31a255d1) ok source (%rdi) (0x6a001e) not located in a known VMA region (needed readable region)! destination %xmm1 ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: empathy StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libc.so.6 g_strdup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/libgtk-x11-2.0.so.0 ?? () ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: empathy crashed with SIGSEGV in g_strdup() UpgradeStatus: Upgraded to natty on 2011-03-09 (19 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/744802/+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
