[Desktop-packages] [Bug 1019395] Re: At random times NM applet menu stops responding
Has anyone observed this recently? -- 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/1019395 Title: At random times NM applet menu stops responding Status in network-manager-applet package in Ubuntu: Confirmed Bug description: At random times, Network Manager's whole menu stops working. If I'm already connected (I mainly use wifi), then network keeps working fine, however none of the items in the menu does anything. Examples, I click on Edit Networks = nothing happens. I click on Disconnect = nothing happens I click on more networks = a tiny empty submenu is shown (instead of a list of available wifi networks, and there are plenty of them here) Rebooting fixes the issue. This is almost certainly a regression in a recent update, as I never experienced this until recently. This may be happening after suspend/resume, but I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu10 Architecture: i386 Date: Fri Jun 29 21:43:29 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.67 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-17 (43 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1019395/+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 1111884] Re: nouveau fails at suspend/resume - PAGE_NOT_PRESENT
I just submitted Bug #67878 (https://bugs.freedesktop.org/show_bug.cgi?id=67878) upstream. It may be that Bug #62835 (https://bugs.freedesktop.org/show_bug.cgi?id=62835) is also a duplicate. ** Bug watch added: freedesktop.org Bugzilla #67878 https://bugs.freedesktop.org/show_bug.cgi?id=67878 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/884 Title: nouveau fails at suspend/resume - PAGE_NOT_PRESENT Status in The Linux Kernel: New Status in Accelerated Xorg driver for nVidia cards: New Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Happens when resuming from standby. Can be reproduced. Every time. nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 00449b nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: , e1c: , e20: 0011, e24: 0c03 nouveau E[ PGRAPH][:05:00.0] TRAP nouveau E[ PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d mthd 0x060c data 0x04b0 nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] magic set 0: nouveau E[ PGRAPH][:05:00.0] 0x00408904: 0x20087701 nouveau E[ PGRAPH][:05:00.0] 0x00408908: 0x00449b00 nouveau E[ PGRAPH][:05:00.0] 0x0040890c: 0x8432 nouveau E[ PGRAPH][:05:00.0] 0x00408910: 0x9b00 nouveau E[ PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 0x0003 nouveau E[ PGRAPH][:05:00.0] TRAP ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-core 2:1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 Date: Thu Jan 31 22:17:49 2013 DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2330] MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago) UserGroups: dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.name: P5WD2-Premium dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Thu Jan 31 22:30:57 2013
[Desktop-packages] [Bug 379599] Re: System shutdown on 0% for 1 of 2 batteries.
** Also affects: upower Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/379599 Title: System shutdown on 0% for 1 of 2 batteries. Status in Gnome Powermanager: In Progress Status in The Linux Kernel: Fix Released Status in Upower: New Status in “gnome-power-manager” package in Ubuntu: Triaged Bug description: Binary package hint: gnome-power-manager With two batteries, when the first battery hits low levels gnome- power-manager alerts the user of low/critical and then takes the critcially low action, even thow the other battery is still at 100%. gnome-power-manager detects and can interact with either battery. This affects at least karmic, but is believed to affect jaunty as well. gnome-power-manager version 2.26.1-0ubuntu3 I would expect that gnome-power-manager should warn, but then continue to move through the second battery. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/379599/+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 1090107] [NEW] Long compiz sessions eventually start showing new windows as empty
Public bug reported: After using a compiz session consistently for a week or so, opening a new window intermittently results in a window frame with no contents. This can be seen in the attached screenshot (the XSane window in the top left hand corner of the screen). While not all new windows will be shown as empty, the probability of this occurring certainly increases in time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 Uname: Linux 3.7.0-rc6+ x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgsvg,text,mousepoll,regex,obs,place,imgpng,animation,expo,neg,ezoom,grid,snap,resize,vpswitch,move,session,wall,unitymtgrabhandles,workarounds,fade,switcher,resizeinfo,scale,unityshell] CompositorRunning: compiz Date: Thu Dec 13 14:43:12 2012 DistUpgraded: 2012-10-09 01:03:44,450 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01fe] Subsystem: Dell Device [1028:01fe] InstallationDate: Installed on 2011-10-19 (421 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Latitude D830 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-rc6+ root=UUID=27880cc8-df42-4098-8e07-3c4fb9dba0a5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to quantal on 2012-10-09 (65 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd01/04/2010:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.8.4+bzr3412-0ubuntu0.1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption quantal running-unity ubuntu ** Attachment added: Screenshot showing issue https://bugs.launchpad.net/bugs/1090107/+attachment/3459355/+files/Screenshot%20from%202012-12-13%2014%3A45%3A40.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1090107 Title: Long compiz sessions eventually start showing new windows as empty Status in “xorg” package in Ubuntu: New Bug description: After using a compiz session consistently for a week or so, opening a new window intermittently results in a window frame with no contents. This can be seen in the attached screenshot (the XSane window in the top left hand corner of the screen). While not all new windows will be shown as empty, the probability of this occurring certainly increases in time. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: xorg 1:7.7+1ubuntu4 Uname: Linux 3.7.0-rc6+ x86_64 .tmp.unity.support.test.0: ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgsvg,text,mousepoll,regex,obs,place,imgpng,animation,expo,neg,ezoom,grid,snap,resize,vpswitch,move,session,wall,unitymtgrabhandles,workarounds,fade,switcher,resizeinfo,scale,unityshell] CompositorRunning: compiz Date: Thu Dec 13 14:43:12 2012 DistUpgraded: 2012-10-09 01:03:44,450 DEBUG enabling apt cron job DistroCodename: quantal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01fe] Subsystem: Dell Device [1028:01fe] InstallationDate: Installed on 2011-10-19 (421 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: Dell Inc. Latitude D830 MarkForUpload: True PccardctlIdent: Socket 0:
[Desktop-packages] [Bug 1040259] Re: FFE: libmessaging-menu transitions for quantal
Does libmessaging-menu have Python bindings yet? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to liferea in Ubuntu. https://bugs.launchpad.net/bugs/1040259 Title: FFE: libmessaging-menu transitions for quantal Status in Skype-wrapper: In Progress Status in “evolution-indicator” package in Ubuntu: Triaged Status in “gm-notify” package in Ubuntu: Triaged Status in “gwibber” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “libunity-webapps” package in Ubuntu: Fix Released Status in “liferea” package in Ubuntu: Triaged Status in “pidgin-libnotify” package in Ubuntu: Triaged Status in “smuxi” package in Ubuntu: Fix Released Status in “telepathy-indicator” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “unity-mail” package in Ubuntu: Fix Released Status in “xchat-indicator” package in Ubuntu: Fix Released Status in “gm-notify” source package in Quantal: Triaged Status in “gwibber” source package in Quantal: Fix Released Status in “indicator-messages” source package in Quantal: Fix Released Status in “libunity-webapps” source package in Quantal: Fix Released Status in “liferea” source package in Quantal: Triaged Status in “pidgin-libnotify” source package in Quantal: Triaged Status in “smuxi” source package in Quantal: Fix Released Status in “telepathy-indicator” source package in Quantal: Fix Released Status in “thunderbird” source package in Quantal: Fix Released Status in “unity-mail” source package in Quantal: Fix Released Status in “xchat-indicator” source package in Quantal: Fix Released Bug description: indicator-messages got updated, introducing a new libmessaging-menu api (deprecating the old libindicate library) which should make application developper's life easier. The indicator work is done and the library is ready and we started porting applications The current stack is being tested in https://launchpad.net/~ubuntu- desktop/+archive/ppa/ It includes - indicator-messages - gwibber - indicator-telepathy - thunderbird (soon, work is being finished) which is what we consider the minimal set for landing the feature for quantal we will add those soon: - pidgin - xchat-indicator - evolution-indicator To manage notifications about this bug go to: https://bugs.launchpad.net/skype-wrapper/+bug/1040259/+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 1012154] Re: NM can't connect to another, known, Wi-Fi network after resume from suspend; reboot fixes it
*** This bug is a duplicate of bug 930563 *** https://bugs.launchpad.net/bugs/930563 ** This bug is no longer a duplicate of bug 1019395 At random times NM applet menu stops responding ** This bug has been marked a duplicate of bug 930563 NM Applet menu entries not responding -- 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/1012154 Title: NM can't connect to another, known, Wi-Fi network after resume from suspend; reboot fixes it Status in “network-manager” package in Ubuntu: New Bug description: Usually I connect to wifi networks just fine. Now I suspended (while I was connected to a network) and moved the computer to another place. When I resumed, the icon in the notification area correctly displayed that it was disconnected. The network to which I was connected prior to suspend was not available and there were other networks available. When I selected one of the available newtorks (one to which I often connect and whose password is stored) nothing happened: it didn't even try to connect. I tried several times with the same result: it would just do nothing. I also tried to connect to different network, and _nothing_ happened (it should have prompted me for password). Rebooting fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu9 Architecture: i386 CRDA: country ES: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS Date: Tue Jun 12 16:19:57 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.54 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-17 (25 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1012154/+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 1019395] Re: At random times NM applet menu stops responding
*** This bug is a duplicate of bug 930563 *** https://bugs.launchpad.net/bugs/930563 ** This bug has been marked a duplicate of bug 930563 NM Applet menu entries not responding -- 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/1019395 Title: At random times NM applet menu stops responding Status in “network-manager-applet” package in Ubuntu: Confirmed Bug description: At random times, Network Manager's whole menu stops working. If I'm already connected (I mainly use wifi), then network keeps working fine, however none of the items in the menu does anything. Examples, I click on Edit Networks = nothing happens. I click on Disconnect = nothing happens I click on more networks = a tiny empty submenu is shown (instead of a list of available wifi networks, and there are plenty of them here) Rebooting fixes the issue. This is almost certainly a regression in a recent update, as I never experienced this until recently. This may be happening after suspend/resume, but I'm not sure. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.1 ProcVersionSignature: Ubuntu 3.2.0-26.41-generic 3.2.19 Uname: Linux 3.2.0-26-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu10 Architecture: i386 Date: Fri Jun 29 21:43:29 2012 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) IpRoute: default via 192.168.1.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.67 metric 2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-05-17 (43 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1019395/+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 998304] Re: Details is not a descriptive title
Details is not a descriptive name. Default Applications should either be moved to its own control-center applet or Details needs to be renamed. -- 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/998304 Title: Details is not a descriptive title Status in “gnome-control-center” package in Ubuntu: Won't Fix Bug description: The gnome-control-center 'details' program is not very descriptive. Perhaps 'System Details' or 'System Information' is better name for this program. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 12 09:32:23 2012 InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to precise on 2012-05-06 (5 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup22.0-0ubuntu2 gnome-bluetooth 3.2.2-0ubuntu5 indicator-datetime 0.3.94-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/998304/+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 930563] Re: NM Applet menu entries not responding
I also have observed this problem. `dbus-monitor --session` shows the following
when I click on a menu item,
signal sender=:1.74 - dest=com.canonical.Unity.Panel.Service serial=207627
path=/com/canonical/Unity/Panel/Service;
interface=com.canonical.Unity.Panel.Service; member=EntryActivated
string
struct {
int32 0
int32 0
uint32 0
uint32 0
}
method call sender=:1.74 - dest=:1.1485 serial=207628
path=/org/ayatana/NotificationItem/nm_applet/Menu;
interface=com.canonical.dbusmenu; member=EventGroup
array [
struct {
int32 43153
string clicked
variant int32 0
uint32 636178867
}
]
error sender=:1.1485 - dest=:1.74
error_name=org.gtk.GDBus.UnmappedGError.Quark._LIBDBUSMENU_2dGLIB.Code0
reply_serial=207628
string The IDs supplied '[43153]' do not refer to any menu items we
have
--
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/930563
Title:
NM Applet menu entries not responding
Status in “network-manager-applet” package in Ubuntu:
Confirmed
Bug description:
When i click on the NM applet, the menu appears correct but when i click eg
on disconnect or edit connection, nothing happens.
This is the behavior for all menu entries.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager-gnome 0.9.2.0+git.20120126t000800.5151959-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5
Uname: Linux 3.2.0-15-generic-pae i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sat Feb 11 09:04:44 2012
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110426)
IpRoute:
default via 192.168.178.1 dev wlan0 proto static
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
169.254.0.0/16 dev wlan0 scope link metric 1000
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.20
metric 2
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to precise on 2012-02-03 (8 days ago)
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
wlan0 802-11-wireless connected
/org/freedesktop/NetworkManager/Devices/1
eth0 802-3-ethernetunavailable
/org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE
WIFI WWAN-HARDWARE WWAN
running 0.9.3.0connected enabled enabled
enabledenabled disabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/930563/+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 135548] Re: Action on critical battery isn't triggered
Has there been a new bug filed along these lines? I still seem to be running into this in Precise. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/135548 Title: Action on critical battery isn't triggered Status in Gnome Powermanager: Fix Released Status in “gnome-power-manager” package in Ubuntu: Fix Released Status in “gnome-power-manager” source package in Hardy: Confirmed Status in “gnome-power-manager” source package in Jaunty: Invalid Status in “gnome-power-manager” source package in Karmic: Fix Released Status in “gnome-power-manager” package in Baltix: Confirmed Bug description: Binary package hint: gnome-power-manager I am using Gutsy Tribe 5. On Feisty, everything works as expected. I am using a Dell Inspiron 510m. Apparently it has two battery bays, although I have only ever had one battery in it. I have set the preference to shut down on critical and to hibernate on critical. In both cases it just runs down to nothing and powers off. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/135548/+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 1007855] [NEW] U+2329 and U+232A characters rendered too wide
Public bug reported: Both gnome-terminal and xterm render the U+2329 (〈) and U+232A (〉) characters in two cells despite the fact that most other applications render it correctly. This appears to happen with both fixed- and variable-width fonts. I apologize for the incorrect package assignment; I really have no idea where in the stack this bug is. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1007855 Title: U+2329 and U+232A characters rendered too wide Status in “gnome-terminal” package in Ubuntu: New Bug description: Both gnome-terminal and xterm render the U+2329 (〈) and U+232A (〉) characters in two cells despite the fact that most other applications render it correctly. This appears to happen with both fixed- and variable-width fonts. I apologize for the incorrect package assignment; I really have no idea where in the stack this bug is. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1007855/+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 1004099] [NEW] Closing Rhythmbox window quits even while copying files to device
Public bug reported: Closing the Rhythmbox window while copying files to a media player device causes Rhythmbox to quit if nothing is being played. Reproduction steps: 1) Open new Rhythmbox session 2) Copy files to a media player device 3) Close Rhythmbox window Expected outcome: Rhythmbox remains open until file copying has finished. Observed outcome: Rhythmbox closes immediately, killing the file copy process. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1004099 Title: Closing Rhythmbox window quits even while copying files to device Status in “rhythmbox” package in Ubuntu: New Bug description: Closing the Rhythmbox window while copying files to a media player device causes Rhythmbox to quit if nothing is being played. Reproduction steps: 1) Open new Rhythmbox session 2) Copy files to a media player device 3) Close Rhythmbox window Expected outcome: Rhythmbox remains open until file copying has finished. Observed outcome: Rhythmbox closes immediately, killing the file copy process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1004099/+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 904001] [NEW] Can't start evince over SSH tunnel X session
Public bug reported: For example, $ cat /etc/issue Ubuntu 11.10 \n \l $ ssh -X chimera Welcome to Ubuntu 11.10 (GNU/Linux 3.0.0-13-generic x86_64) * Documentation: https://help.ubuntu.com/ 35 packages can be updated. 8 updates are security updates. Last login: Tue Dec 13 18:06:12 2011 from physicsnat56.physics.umass.edu $ evince ~/hello.pdf Failed to get bus connection: Command line `dbus-launch --autolaunch=4ecb6d54129c67693bce6dc90006 --binary-syntax --close-stderr' exited with non-zero exit status 1: EOF in dbus-launch reading address from bus daemon\n In /var/log/syslog on chimera I see messages of the following form, Dec 13 18:17:35 chimera kernel: [1115999.980510] type=1400 audit(1323818255.844:124): apparmor=DENIED operation=exec parent=29637 profile=/usr/bin/evince name=/bin/dbus-daemon pid=29638 comm=dbus-launch requested_mask=x denied_mask=x fsuid=1000 ouid=0 Therefore, it seems this is likely related to bug #566207. ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release -- 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/904001 Title: Can't start evince over SSH tunnel X session Status in “evince” package in Ubuntu: New Bug description: For example, $ cat /etc/issue Ubuntu 11.10 \n \l $ ssh -X chimera Welcome to Ubuntu 11.10 (GNU/Linux 3.0.0-13-generic x86_64) * Documentation: https://help.ubuntu.com/ 35 packages can be updated. 8 updates are security updates. Last login: Tue Dec 13 18:06:12 2011 from physicsnat56.physics.umass.edu $ evince ~/hello.pdf Failed to get bus connection: Command line `dbus-launch --autolaunch=4ecb6d54129c67693bce6dc90006 --binary-syntax --close-stderr' exited with non-zero exit status 1: EOF in dbus-launch reading address from bus daemon\n In /var/log/syslog on chimera I see messages of the following form, Dec 13 18:17:35 chimera kernel: [1115999.980510] type=1400 audit(1323818255.844:124): apparmor=DENIED operation=exec parent=29637 profile=/usr/bin/evince name=/bin/dbus-daemon pid=29638 comm=dbus-launch requested_mask=x denied_mask=x fsuid=1000 ouid=0 Therefore, it seems this is likely related to bug #566207. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/904001/+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 566207] Re: apparmor blocks evince from /usr/bin/dbus-launch
I just opened #904001. Thanks for your help. -- 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/566207 Title: apparmor blocks evince from /usr/bin/dbus-launch Status in “apparmor” package in Ubuntu: Fix Released Status in “evince” package in Ubuntu: Fix Released Status in “apparmor” source package in Lucid: Fix Released Status in “evince” source package in Lucid: Fix Released Status in “apparmor” source package in Maverick: Fix Released Status in “evince” source package in Maverick: Fix Released Bug description: Whenever I start evince, I get the following warnings from the kernel: Apr 7 16:14:00 spitzer kernel: [539649.749831] type=1503 audit(1270671240.166:27): operation=exec pid=32423 parent=32419 profile=/usr/bin/evince requested_mask=::x denied_mask=::x fsuid=1000 ouid=0 name=/usr/bin/dbus-launch Apr 7 16:14:00 spitzer kernel: [539649.751333] type=1503 audit(1270671240.166:28): operation=exec pid=32424 parent=32419 profile=/usr/bin/evince requested_mask=::x denied_mask=::x fsuid=1000 ouid=0 name=/usr/bin/dbus-launch Apr 7 16:14:00 spitzer kernel: [539649.751464] type=1503 audit(1270671240.166:29): operation=exec pid=32424 parent=32419 profile=/usr/bin/evince requested_mask=::x denied_mask=::x fsuid=1000 ouid=0 name=/usr/bin/dbus-launch Apr 7 16:33:00 spitzer kernel: [540789.509776] __ratelimit: 24 callbacks suppressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/566207/+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 566207] Re: apparmor blocks evince from /usr/bin/dbus-launch
It seems this has been yet again broken in Oneiric. -- 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/566207 Title: apparmor blocks evince from /usr/bin/dbus-launch Status in “apparmor” package in Ubuntu: Fix Released Status in “evince” package in Ubuntu: Fix Released Status in “apparmor” source package in Lucid: Fix Released Status in “evince” source package in Lucid: Fix Released Status in “apparmor” source package in Maverick: Fix Released Status in “evince” source package in Maverick: Fix Released Bug description: Whenever I start evince, I get the following warnings from the kernel: Apr 7 16:14:00 spitzer kernel: [539649.749831] type=1503 audit(1270671240.166:27): operation=exec pid=32423 parent=32419 profile=/usr/bin/evince requested_mask=::x denied_mask=::x fsuid=1000 ouid=0 name=/usr/bin/dbus-launch Apr 7 16:14:00 spitzer kernel: [539649.751333] type=1503 audit(1270671240.166:28): operation=exec pid=32424 parent=32419 profile=/usr/bin/evince requested_mask=::x denied_mask=::x fsuid=1000 ouid=0 name=/usr/bin/dbus-launch Apr 7 16:14:00 spitzer kernel: [539649.751464] type=1503 audit(1270671240.166:29): operation=exec pid=32424 parent=32419 profile=/usr/bin/evince requested_mask=::x denied_mask=::x fsuid=1000 ouid=0 name=/usr/bin/dbus-launch Apr 7 16:33:00 spitzer kernel: [540789.509776] __ratelimit: 24 callbacks suppressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/566207/+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 875773] [NEW] Using media keys with Alt modifier doesn't work
Public bug reported: Setting a keyboard shortcut action, say 'Next track', to a media key with the Alt modifier, say 'Alt+Audio raise volume' doesn't work. In particular, pressing Alt+Audio raise volume will result in the volume being raised, not the track being advanced. The Super and Ctrl modifiers appear to work as expected. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/875773 Title: Using media keys with Alt modifier doesn't work Status in “gnome-settings-daemon” package in Ubuntu: New Bug description: Setting a keyboard shortcut action, say 'Next track', to a media key with the Alt modifier, say 'Alt+Audio raise volume' doesn't work. In particular, pressing Alt+Audio raise volume will result in the volume being raised, not the track being advanced. The Super and Ctrl modifiers appear to work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/875773/+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 459851] Re: can't use CTRL + C for copy'n'paste
Indeed this is still not fixed. -- 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/459851 Title: can't use CTRL + C for copy'n'paste Status in “empathy” package in Ubuntu: Fix Released Bug description: Binary package hint: empathy I didn't know I have to write something here so let's do :-) same for CTRL + A which doesn't work and CTRL + V ProblemType: Bug Architecture: i386 Date: Sat Oct 24 17:54:46 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: empathy 2.28.1-1ubuntu1 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: empathy Uname: Linux 2.6.31-14-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/459851/+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
