[Desktop-packages] [Bug 1207217] Re: Inkscape: Unable to change or select any font
Completely reinstalled Kubuntu 13.10 from scratch, and the bug seems to have disappeared. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to inkscape in Ubuntu. https://bugs.launchpad.net/bugs/1207217 Title: Inkscape: Unable to change or select any font Status in Inkscape: A Vector Drawing Tool: New Status in “inkscape” package in Ubuntu: New Bug description: Selecting any font in inkscape fails silently. Although the new font appears to be selected in the font drop-down list, the actual text never changes. To replicate: 1) Start a new document in inkscape 2) Use the Text tool and type something. 3) Select the text that was just typed. 4) In the font drop-down box, change the font to something else. 5) Observe that the name in the font drop-down box has changed, but that the actual font used in the text has not. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: inkscape 0.48.4-0.1ubuntu2 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Thu Aug 1 16:03:59 2013 InstallationDate: Installed on 2010-04-09 (1209 days ago) InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) MarkForUpload: True SourcePackage: inkscape UpgradeStatus: Upgraded to raring on 2013-04-29 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1207217/+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 1244529] [NEW] no repaint of unity at end of fullscreen chromium
Public bug reported: I use the full screen mode of the Chromium browser and toggle between maximized and full screen with F11. When leaving full screen mode the unity areas of the screen does not repaint properly until after a delay of up to tens of seconds. I've only seen this behavior with Chromium, not with Firefox or Google Chrome or other programs in full screen mode. This behavior is new with Ubuntu release 13.10. To reproduce: - start Chromium Browser - maximize Chromium window (Alt+' ' X) - enter full screen mode (F11) - leave full screen mode (F11) At this point there is garbage above and to the left of the Chromium window. See the attached screendump. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 29.0.1547.65-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Fri Oct 25 07:42:36 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2012-05-04 (538 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy ** Attachment added: "example of missing repaint" https://bugs.launchpad.net/bugs/1244529/+attachment/3890627/+files/Screenshot%20from%202013-10-25%2008%3A09%3A37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1244529 Title: no repaint of unity at end of fullscreen chromium Status in “chromium-browser” package in Ubuntu: New Bug description: I use the full screen mode of the Chromium browser and toggle between maximized and full screen with F11. When leaving full screen mode the unity areas of the screen does not repaint properly until after a delay of up to tens of seconds. I've only seen this behavior with Chromium, not with Firefox or Google Chrome or other programs in full screen mode. This behavior is new with Ubuntu release 13.10. To reproduce: - start Chromium Browser - maximize Chromium window (Alt+' ' X) - enter full screen mode (F11) - leave full screen mode (F11) At this point there is garbage above and to the left of the Chromium window. See the attached screendump. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: chromium-browser 29.0.1547.65-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Fri Oct 25 07:42:36 2013 Desktop-Session: DESKTOP_SESSION = ubuntu XDG_CONFIG_DIRS = /etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg XDG_DATA_DIRS = /usr/share/ubuntu:/usr/share/gnome:/usr/local/share/:/usr/share/ Env: MOZ_PLUGIN_PATH = None LD_LIBRARY_PATH = None InstallationDate: Installed on 2012-05-04 (538 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: chromium-browser UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) chromium-default: CHROMIUM_FLAGS="" gconf-keys: /desktop/gnome/applications/browser/exec = b'/usr/bin/chromium-browser\n'/desktop/gnome/url-handlers/https/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/https/enabled = b'true\n'/desktop/gnome/url-handlers/http/command = b'/usr/bin/chromium-browser %s\n'/desktop/gnome/url-handlers/http/enabled = b'true\n'/desktop/gnome/session/required_components/windowmanager = b''/apps/metacity/general/compositing_manager = b''/desktop/gnome/interface/icon_theme = b'gnome\n'/desktop/gnome/interface/gtk_theme = b'Clearlooks\n' To manage notifications about this
[Desktop-packages] [Bug 1244526] [NEW] RDP: sound not going through
Public bug reported: With this command I have sound connecting to a Windows guest: $ xfreerdp /sec:rdp /sound:sys:pulse +clipboard +fonts +window-drag +aero /v:"10.0.0.XX" /u:"XXX" /p:"XXX" Using Remmina and selecting "local" at sound settings, I have no sound. The sound icon in the systray has a red cross on it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: remmina 1.0.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 25 16:52:38 2013 InstallationDate: Installed on 2012-10-31 (358 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: remmina UpgradeStatus: Upgraded to saucy on 2013-10-23 (2 days ago) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1244526 Title: RDP: sound not going through Status in “remmina” package in Ubuntu: New Bug description: With this command I have sound connecting to a Windows guest: $ xfreerdp /sec:rdp /sound:sys:pulse +clipboard +fonts +window-drag +aero /v:"10.0.0.XX" /u:"XXX" /p:"XXX" Using Remmina and selecting "local" at sound settings, I have no sound. The sound icon in the systray has a red cross on it. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: remmina 1.0.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 25 16:52:38 2013 InstallationDate: Installed on 2012-10-31 (358 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: remmina UpgradeStatus: Upgraded to saucy on 2013-10-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1244526/+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 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
So when I wrote 6 months ago that: > If you can reproduce this issue, please file a new bug report against > the sysvinit-utils package with details. It is certainly unrelated to the > common issue being described here. Rather than doing this to help yourself, you switch distros, decide that upstart is to blame for a part of the system that is clearly managed by another package, and stay subscribed to the bug so that you can yell at people who are experiencing the bug that was originally reported - a bug that is unrelated to the issue that you were experiencing? This bug tracker is for helping users resolve bugs in Ubuntu. If you're not using Ubuntu, and you're not helping fix the bugs, your comments are not needed here. -- 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/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E 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.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+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 1244527] [NEW] Cursor doesn't change to use the guest cursor
Public bug reported: Connecting to a Windows guest using remmina in RDP, the cursor doesn't change, for exemple when hovering links in the browser or over a text box. It does work properly when using xfreerdp directly. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: remmina 1.0.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 25 16:58:06 2013 InstallationDate: Installed on 2012-10-31 (358 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: remmina UpgradeStatus: Upgraded to saucy on 2013-10-23 (2 days ago) ** Affects: remmina (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1244527 Title: Cursor doesn't change to use the guest cursor Status in “remmina” package in Ubuntu: New Bug description: Connecting to a Windows guest using remmina in RDP, the cursor doesn't change, for exemple when hovering links in the browser or over a text box. It does work properly when using xfreerdp directly. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: remmina 1.0.0-4ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 25 16:58:06 2013 InstallationDate: Installed on 2012-10-31 (358 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: remmina UpgradeStatus: Upgraded to saucy on 2013-10-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1244527/+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 1238620] Re: apport-retrace doesn't work with [arch=foo] in the deb line
This bug was fixed in the package apport - 2.12.6-0ubuntu1 --- apport (2.12.6-0ubuntu1) trusty; urgency=low * New upstream security/bug fix release: - SECURITY FIX: For setuid programs which drop their privileges after startup, make the report and core dumps owned by root, to avoid possible data disclosure. Also, change core dump files to permissions "0600". Thanks to Martin Carpenter for discovering this! (CVE-2013-1067, LP: #1242435) - sandboxutils.needed_runtime_packages(): Create cache directory for Contents.gz if missing. (LP: #933199) - apt/dpkg: Recognize options in apt sources.list. (LP: #1238620) * Move Vcs-Bzr to trusty branch. -- Martin PittFri, 25 Oct 2013 06:49:19 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-1067 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1238620 Title: apport-retrace doesn't work with [arch=foo] in the deb line Status in “apport” package in Ubuntu: Fix Released Bug description: I used [arch=armhf] to work around bug #1238616, but apport-retrace doesn't seem to support that syntax and chooses ddebs to download the Contents file from. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1238620/+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 933199] Re: apport-retrace crashed with IOError in _search_contents(): [Errno 2] No such file or directory: u'~/.cache/apport/retrace/Ubuntu 12.04/Contents-i386.gz'
This bug was fixed in the package apport - 2.12.6-0ubuntu1 --- apport (2.12.6-0ubuntu1) trusty; urgency=low * New upstream security/bug fix release: - SECURITY FIX: For setuid programs which drop their privileges after startup, make the report and core dumps owned by root, to avoid possible data disclosure. Also, change core dump files to permissions "0600". Thanks to Martin Carpenter for discovering this! (CVE-2013-1067, LP: #1242435) - sandboxutils.needed_runtime_packages(): Create cache directory for Contents.gz if missing. (LP: #933199) - apt/dpkg: Recognize options in apt sources.list. (LP: #1238620) * Move Vcs-Bzr to trusty branch. -- Martin PittFri, 25 Oct 2013 06:49:19 +0200 ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2013-1067 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/933199 Title: apport-retrace crashed with IOError in _search_contents(): [Errno 2] No such file or directory: u'~/.cache/apport/retrace/Ubuntu 12.04/Contents-i386.gz' Status in “apport” package in Ubuntu: Fix Released Bug description: Retracing locally a crash, I got this apport crash, detected by apport himself ;) TEST CASE: 1. On a fresh system (or remove the directory $HOME/.cache/apport/retrace/) 2. Use an existing crash file or create a new one and run the command: $ apport-cli /path/to/crash_file.crash 2.1 To the question: "Send problem report to the developers?" reply "E: Examine locally" 2.2. To the question "This will launch apport-retrace in a terminal window to examine the crash." reply "3: Update [...].crash with fully symbolic stack trace" ACTUAL RESULT: This crash EXPECTED RESULT apport proceeds with crash retracing. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: apport-retrace 1.91-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-15.24-generic-pae 3.2.5 Uname: Linux 3.2.0-15-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.91-0ubuntu1 Architecture: i386 CheckboxSubmission: c4273c0f4f2b8d26cd6bf31cadfd2912 CheckboxSystem: a871981cb5bdf4d6ebd55be46becf77e Date: Thu Feb 16 01:18:43 2012 EcryptfsInUse: Yes ExecutablePath: /usr/bin/apport-retrace InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/bin/apport-retrace -S system -C ~/.cache/apport/retrace -v --gdb /var/crash/_usr_bin_nautilus.1000.crash ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr_FR:fr:en_GB:en SHELL=/bin/bash PATH=(custom, no user) PythonArgs: ['/usr/bin/apport-retrace', '-S', 'system', '-C', '~/.cache/apport/retrace', '-v', '--gdb', '/var/crash/_usr_bin_nautilus.1000.crash'] SourcePackage: apport Title: apport-retrace crashed with IOError in _search_contents(): [Errno 2] No such file or directory: u'~/.cache/apport/retrace/Ubuntu 12.04/Contents-i386.gz' UpgradeStatus: Upgraded to precise on 2008-10-18 (1215 days ago) UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev pulse pulse-access scanner tape users video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/933199/+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 1242435] Re: Desktop setuid cores readable by non-privileged user
This bug was fixed in the package apport - 2.12.6-0ubuntu1 --- apport (2.12.6-0ubuntu1) trusty; urgency=low * New upstream security/bug fix release: - SECURITY FIX: For setuid programs which drop their privileges after startup, make the report and core dumps owned by root, to avoid possible data disclosure. Also, change core dump files to permissions "0600". Thanks to Martin Carpenter for discovering this! (CVE-2013-1067, LP: #1242435) - sandboxutils.needed_runtime_packages(): Create cache directory for Contents.gz if missing. (LP: #933199) - apt/dpkg: Recognize options in apt sources.list. (LP: #1238620) * Move Vcs-Bzr to trusty branch. -- Martin PittFri, 25 Oct 2013 06:49:19 +0200 ** Changed in: apport (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1242435 Title: Desktop setuid cores readable by non-privileged user Status in Apport crash detection/reporting: Fix Released Status in “apport” package in Ubuntu: Fix Released Status in “apport” source package in Lucid: Invalid Status in “apport” source package in Precise: Fix Released Status in “apport” source package in Quantal: Fix Released Status in “apport” source package in Raring: Fix Released Status in “apport” source package in Saucy: Fix Released Status in “apport” source package in Trusty: Fix Released Status in “apport” package in Debian: Confirmed Bug description: Elsewhere I have been working on a sensitive information leak via core dump generated by gcore(1). The sensitive information in question is read by a stock setuid root binary executed by a non-privileged user. On Ubuntu Desktop fs.suid_dumpable=2. Referencing https://www.kernel.org/doc/Documentation/sysctl/fs.txt: 2 - (suidsafe) - any binary which normally would not be dumped is dumped anyway, but only if the "core_pattern" kernel sysctl is set to either a pipe handler or a fully qualified path. (For more details on this limitation, see CVE-2006-2451.) This mode is appropriate when administrators are attempting to debug problems in a normal environment, and either have a core dump pipe handler that knows to treat privileged core dumps with care, or specific directory defined for catching core dumps. If a core dump happens without a pipe handler or fully qualifid path, a message will be emitted to syslog warning about the lack of a correct setting. NB "treat privileged core dumps with care". On a stock Desktop 12.04 LTS install: kernel.core_pattern = |/usr/share/apport/apport %p %s %c apport dutifully dumps the core and this is readable (0660, user:user) by the invoking user, whereas it should be something like 0440, root:root. I believe this to be a bug in apport. TRUNK FIX: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2723 Backports for older releases available as attachments here. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1242435/+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 1244488] Re: help
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1244488 Title: help Status in “xorg” package in Ubuntu: Incomplete Bug description: help ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 24 23:42:32 2013 DistUpgraded: 2013-10-17 16:19:13,731 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu InstallationDate: Installed on 2013-07-16 (100 days ago) InstallationMedia: Megalinux Diamante 12.04 "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 003: ID 090c:37c0 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Silicon Motion Camera Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEGAWARE SLIMBLACK MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=236cd8c2-8616-44af-be42-55dba7694668 ro splash acpi_os_name=Linux quiet acpi_osi= SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-17 (7 days ago) dmi.bios.date: 07/05/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 71R dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SLIMBLACK dmi.board.vendor: MEGAWARE dmi.board.version: EC 1.17Y dmi.chassis.asset.tag: M0626201001 dmi.chassis.type: 9 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr71R:bd07/05/2012:svnMEGAWARE:pnSLIMBLACK:pvr0.1:rvnMEGAWARE:rnSLIMBLACK:rvrEC1.17Y:cvnMEGAWARE:ct9:cvr0.1: dmi.product.name: SLIMBLACK dmi.product.version: 0.1 dmi.sys.vendor: MEGAWARE version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 24 22:10:24 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1479 vendor BOE xserver.version: 2:1.14.3-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244488/+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 1073433] Re: Ext4 corruption associated with shutdown of Ubuntu 12.10
Guys, come on! What the heck network-manager and network connections are you talking about?! This really pissed me off already! As I've said earlier, the problem is NOT in network-manager! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1073433/comments/105 because it appears even when network-manager is not installed. I can assume (or even be sure), that network-manager HAVE some bug(s) associated with this problem, but the main cause - it's not a network-manager. And I'm sure it's in upstart. Believe me, I've spent a lot of time trying to debug this problem... You can see my comments (and debug logs) about this problem above. That was the boiling point. I've moved to Debian. -- 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/1073433 Title: Ext4 corruption associated with shutdown of Ubuntu 12.10 Status in Upstart: Confirmed Status in “linux” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Triaged Status in “upstart” package in Ubuntu: Confirmed Bug description: 1. Format and label a target Ext4 partion using Ubuntu 12.04 2. Install 64bit 12.10 OS using that target without reformatting it 3. Shut down 4. Boot an alternate copy of Ubuntu 5. Restart selecting the newly installed OS 6. Login then shutdown 6. Boot an alternate copy of Ubuntu 7.Fsck the newly installed OS allowing corrections to be made Each time the the newly installed OS is executed and then shutdown, even if execution only consists of logging on, a subsequent fsck will FAIL. I used Acronis True Image Home 2013 to create an image of the newly installed 64-bit Ubuntu 12.10, so I can recreate the symptoms of Ext4 filesystem corruption 100% of the time by restoring from the image, booting, logging on and shutting down. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: linux-image-3.5.0-17-generic 3.5.0-17.28 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: aguru 1871 F pulseaudio /dev/snd/controlC0: aguru 1871 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Oct 30 22:24:54 2012 HibernationDevice: RESUME=UUID=f22e3fa5-c5c5-41f1-ae5a-49390547cb67 InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer P5Q-E ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-17-generic root=UUID=ef2c78d5-783a-422a-88f7-27ec09dda0d1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.5.0-17-generic N/A linux-backports-modules-3.5.0-17-generic N/A linux-firmware1.95 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/06/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q-E 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.:bvr2101:bd04/06/2009:svnSystemmanufacturer:pnP5Q-E:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q-E:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5Q-E dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/1073433/+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 1244157] Re: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access
** Branch linked: lp:~network-manager/network-manager/ubuntu -- 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/1244157 Title: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Fix Committed Bug description: On October 9 the NetworkManager tests started failing (https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy- adt-network-manager/?). Unfortunately the more recent saucy logs got lost, but the trusty ones have the information, like in https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job /trusty-adt-network-manager/1/ARCH=i386,label=adt/ In these, dhclient that gets called through NetworkManager and /usr/lib/NetworkManager/nm-dhcp-client.action cannot access the system D-BUS any more: --- NM log NetworkManager[24451]: Activation (eth42) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Error: could not get the system bus. Make sure the message bus daemon is running! Message: (org.freedesktop.D Bus.Error.AccessDenied) Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied --- NM log In syslog, you see this at that time: syslog - Oct 21 14:11:24 autopkgtest kernel: [ 288.320754] type=1400 audit(1382364684.505:21): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=18759 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=18760 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Oct 21 14:11:24 autopkgtest kernel: [ 288.333814] type=1400 audit(1382364684.517:22): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=18752 profile="/sbin/dhclient" name="dev/log" pid=18759 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 syslog - This gets fixed if I do "sudo /etc/init.d/apparmor teardown". But it does not seem to be a problem with the policy itself; if I do "sudo aa-complain dhclient" then dmesg changes to [ 8054.314704] type=1400 audit(1382609088.727:672): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=24451 profile="/sbin/dhclient" name="dev/log" pid=24736 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [ 8054.341409] type=1400 audit(1382609088.755:673): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=24736 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=24737 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 So this doesn't look like a problem with the policy but rather with some internal AppArmor name parsing? I found an old bug 955892 with the same error message, but that got fixed a while ago, and this does not involve ecryptfs or anythign similar. It's just a plain trusty VM with the NetworkManager autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1244157/+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 1244157] Re: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access
** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- 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/1244157 Title: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Fix Committed Bug description: On October 9 the NetworkManager tests started failing (https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy- adt-network-manager/?). Unfortunately the more recent saucy logs got lost, but the trusty ones have the information, like in https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job /trusty-adt-network-manager/1/ARCH=i386,label=adt/ In these, dhclient that gets called through NetworkManager and /usr/lib/NetworkManager/nm-dhcp-client.action cannot access the system D-BUS any more: --- NM log NetworkManager[24451]: Activation (eth42) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Error: could not get the system bus. Make sure the message bus daemon is running! Message: (org.freedesktop.D Bus.Error.AccessDenied) Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied --- NM log In syslog, you see this at that time: syslog - Oct 21 14:11:24 autopkgtest kernel: [ 288.320754] type=1400 audit(1382364684.505:21): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=18759 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=18760 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Oct 21 14:11:24 autopkgtest kernel: [ 288.333814] type=1400 audit(1382364684.517:22): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=18752 profile="/sbin/dhclient" name="dev/log" pid=18759 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 syslog - This gets fixed if I do "sudo /etc/init.d/apparmor teardown". But it does not seem to be a problem with the policy itself; if I do "sudo aa-complain dhclient" then dmesg changes to [ 8054.314704] type=1400 audit(1382609088.727:672): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=24451 profile="/sbin/dhclient" name="dev/log" pid=24736 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [ 8054.341409] type=1400 audit(1382609088.755:673): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=24736 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=24737 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 So this doesn't look like a problem with the policy but rather with some internal AppArmor name parsing? I found an old bug 955892 with the same error message, but that got fixed a while ago, and this does not involve ecryptfs or anythign similar. It's just a plain trusty VM with the NetworkManager autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1244157/+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 1244521] Re: video driver issue
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. At a minimum, we need: 1. the specific steps or actions you took that caused you to encounter the problem, 2. the behavior you expected, and 3. the behavior you actually encountered (in as much detail as possible). ** Changed in: fglrx-pxpress (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-pxpress in Ubuntu. https://bugs.launchpad.net/bugs/1244521 Title: video driver issue Status in “fglrx-pxpress” package in Ubuntu: Incomplete Bug description: I am using AMD radeon hd 7750 with intel core i5 2500K To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-pxpress/+bug/1244521/+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 1244521] [NEW] video driver issue
Public bug reported: I am using AMD radeon hd 7750 with intel core i5 2500K ** Affects: fglrx-pxpress (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-pxpress in Ubuntu. https://bugs.launchpad.net/bugs/1244521 Title: video driver issue Status in “fglrx-pxpress” package in Ubuntu: New Bug description: I am using AMD radeon hd 7750 with intel core i5 2500K To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-pxpress/+bug/1244521/+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 1244157] Re: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access
@John: Thanks a lot for the tip with "apparmor_parser -Kr ", that works perfectly! I'll add that to the NM tests. If this is supposed to work that way, please feel free to close the AppArmor task. If it's just a workaround and D-BUS access is supposed to continue to work from an unshared file system, it can be kept open. ** Changed in: network-manager (Ubuntu) Status: New => In Progress ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- 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/1244157 Title: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: In Progress Bug description: On October 9 the NetworkManager tests started failing (https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy- adt-network-manager/?). Unfortunately the more recent saucy logs got lost, but the trusty ones have the information, like in https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job /trusty-adt-network-manager/1/ARCH=i386,label=adt/ In these, dhclient that gets called through NetworkManager and /usr/lib/NetworkManager/nm-dhcp-client.action cannot access the system D-BUS any more: --- NM log NetworkManager[24451]: Activation (eth42) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Error: could not get the system bus. Make sure the message bus daemon is running! Message: (org.freedesktop.D Bus.Error.AccessDenied) Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied --- NM log In syslog, you see this at that time: syslog - Oct 21 14:11:24 autopkgtest kernel: [ 288.320754] type=1400 audit(1382364684.505:21): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=18759 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=18760 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Oct 21 14:11:24 autopkgtest kernel: [ 288.333814] type=1400 audit(1382364684.517:22): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=18752 profile="/sbin/dhclient" name="dev/log" pid=18759 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 syslog - This gets fixed if I do "sudo /etc/init.d/apparmor teardown". But it does not seem to be a problem with the policy itself; if I do "sudo aa-complain dhclient" then dmesg changes to [ 8054.314704] type=1400 audit(1382609088.727:672): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=24451 profile="/sbin/dhclient" name="dev/log" pid=24736 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [ 8054.341409] type=1400 audit(1382609088.755:673): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=24736 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=24737 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 So this doesn't look like a problem with the policy but rather with some internal AppArmor name parsing? I found an old bug 955892 with the same error message, but that got fixed a while ago, and this does not involve ecryptfs or anythign similar. It's just a plain trusty VM with the NetworkManager autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1244157/+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 1197921]
Created attachment 87925 proposed patch -- 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/1197921 Title: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled Status in Pixman: Confirmed Status in “libreoffice” package in Ubuntu: Invalid Status in “pixman” package in Ubuntu: Triaged Status in “xorg-server” package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 2) apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.3-0ubuntu6 Candidate: 2:1.13.3-0ubuntu6 Version table: *** 2:1.13.3-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status 3) 3) What is expected to happen via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1197921/+attachment/3748789/+files/plantage-mai-only-empty.ods && localc --nologo plantage-mai-only-empty.ods is that xorg does not crash. 4) What happens instead is that it crashes. Reproducible on 12.04 and 13.10 and with Libreoffice 3.5, 4.0.2,and 4.1-rc1. WORKAROUND: Open in Gnumeric. apt-cache policy gnumeric gnumeric: Installed: 1.12.1-1ubuntu1 Candidate: 1.12.1-1ubuntu1 Version table: *** 1.12.1-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.13.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 NonfreeKernelModules: ip6table_filter ip6_tables ebtable_nat ebtables xt_state ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter fglrx ipt_MASQUERADE iptable_nat kvm_amd nf_nat nf_conntrack_ipv4 kvm nf_conntrack nf_defrag_ipv4 ip_tables x_tables bridge stp parport_pc ppdev rfcomm bnep bluetooth binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_usb_audio snd_hda_codec snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd uvcvideo videodev v4l2_compat_ioctl32 edac_core k10temp soundcore dm_multipath edac_mce_amd snd_page_alloc mac_hid sp5100_tco serio_raw i2c_piix4 hwmon_vid lp parport usbhid firewire_ohci hid r8169 pata_atiixp firewire_core crc_itu_t pata_via ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Thu Jul 4 13:58:20 2013 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-05-05 (59 days ago) InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xorg-server UpgradeStatus: Upgraded to saucy on 2013-05-14 (50 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/pixman/+bug/1197921/+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 1197921]
Created attachment 87924 test case -- 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/1197921 Title: LibreOffice spreadsheet causes full Xorg crash with Anti-Aliasing enabled Status in Pixman: Confirmed Status in “libreoffice” package in Ubuntu: Invalid Status in “pixman” package in Ubuntu: Triaged Status in “xorg-server” package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 2) apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.13.3-0ubuntu6 Candidate: 2:1.13.3-0ubuntu6 Version table: *** 2:1.13.3-0ubuntu6 0 500 http://archive.ubuntu.com/ubuntu/ raring/main i386 Packages 100 /var/lib/dpkg/status 3) 3) What is expected to happen via a terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1197921/+attachment/3748789/+files/plantage-mai-only-empty.ods && localc --nologo plantage-mai-only-empty.ods is that xorg does not crash. 4) What happens instead is that it crashes. Reproducible on 12.04 and 13.10 and with Libreoffice 3.5, 4.0.2,and 4.1-rc1. WORKAROUND: Open in Gnumeric. apt-cache policy gnumeric gnumeric: Installed: 1.12.1-1ubuntu1 Candidate: 1.12.1-1ubuntu1 Version table: *** 1.12.1-1ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ raring/universe i386 Packages 100 /var/lib/dpkg/status ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-core 2:1.13.3-0ubuntu13 ProcVersionSignature: Ubuntu 3.2.0-48.74-generic 3.2.46 Uname: Linux 3.2.0-48-generic x86_64 NonfreeKernelModules: ip6table_filter ip6_tables ebtable_nat ebtables xt_state ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter fglrx ipt_MASQUERADE iptable_nat kvm_amd nf_nat nf_conntrack_ipv4 kvm nf_conntrack nf_defrag_ipv4 ip_tables x_tables bridge stp parport_pc ppdev rfcomm bnep bluetooth binfmt_misc snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_usb_audio snd_hda_codec snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd uvcvideo videodev v4l2_compat_ioctl32 edac_core k10temp soundcore dm_multipath edac_mce_amd snd_page_alloc mac_hid sp5100_tco serio_raw i2c_piix4 hwmon_vid lp parport usbhid firewire_ohci hid r8169 pata_atiixp firewire_core crc_itu_t pata_via ApportVersion: 2.10.2-0ubuntu3 Architecture: amd64 Date: Thu Jul 4 13:58:20 2013 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2013-05-05 (59 days ago) InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True ProcCmdline: /usr/bin/X -core :0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: xorg-server UpgradeStatus: Upgraded to saucy on 2013-05-14 (50 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/pixman/+bug/1197921/+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 887331] Re: file-roller cannot open filetypes with derived mimetypes (e.g. epub and ods files)
I have both File Roller and Engrampa Archive Manager installed, as I have both the Unity and Mate desktops installed. File Roller dos not open ePubs, Engrampa does. Maybe you should talk to the people at Mate. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/887331 Title: file-roller cannot open filetypes with derived mimetypes (e.g. epub and ods files) Status in “file-roller” package in Ubuntu: Confirmed Bug description: Given three files A, B and C, where A is a zip file (a.zip), B is an ePub file (b.epub) and C is an ODF Spreadsheet file (c.ods) ... All files have "Open With > Archive Manager" as a menu option in nautilus. This is likely due to the shared-mime-info database having the ePub and ODS mimetypes as . File A will open successfully, while files B and C report "Could not open 'A'" / "Archive type not supported". However, renaming B and C so they have a .zip extension will cause the files to be opened correctly. This is likely due to file-roller checking the filetype to load by extension, not magic. This is indeed the case as giving a text file a .zip extension causes file-roller to report "An error occurred while loading the archive" (End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive.) ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: file-roller 3.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu3 Architecture: amd64 CheckboxSubmission: 5434425585a31b50d9fa7c3153a37fe1 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 Date: Mon Nov 7 21:12:54 2011 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318) ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: file-roller UpgradeStatus: Upgraded to oneiric on 2011-09-24 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/887331/+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 1242435] Re: Desktop setuid cores readable by non-privileged user
Fixed in upstream release 2.12.6: https://launchpad.net/apport/trunk/2.12.6 ** Description changed: Elsewhere I have been working on a sensitive information leak via core dump generated by gcore(1). The sensitive information in question is read by a stock setuid root binary executed by a non-privileged user. On Ubuntu Desktop fs.suid_dumpable=2. Referencing https://www.kernel.org/doc/Documentation/sysctl/fs.txt: 2 - (suidsafe) - any binary which normally would not be dumped is dumped - anyway, but only if the "core_pattern" kernel sysctl is set to - either a pipe handler or a fully qualified path. (For more details - on this limitation, see CVE-2006-2451.) This mode is appropriate - when administrators are attempting to debug problems in a normal - environment, and either have a core dump pipe handler that knows - to treat privileged core dumps with care, or specific directory - defined for catching core dumps. If a core dump happens without - a pipe handler or fully qualifid path, a message will be emitted - to syslog warning about the lack of a correct setting. + anyway, but only if the "core_pattern" kernel sysctl is set to + either a pipe handler or a fully qualified path. (For more details + on this limitation, see CVE-2006-2451.) This mode is appropriate + when administrators are attempting to debug problems in a normal + environment, and either have a core dump pipe handler that knows + to treat privileged core dumps with care, or specific directory + defined for catching core dumps. If a core dump happens without + a pipe handler or fully qualifid path, a message will be emitted + to syslog warning about the lack of a correct setting. NB "treat privileged core dumps with care". On a stock Desktop 12.04 LTS install: - kernel.core_pattern = |/usr/share/apport/apport %p %s %c + kernel.core_pattern = |/usr/share/apport/apport %p %s %c apport dutifully dumps the core and this is readable (0660, user:user) by the invoking user, whereas it should be something like 0440, root:root. I believe this to be a bug in apport. + + TRUNK FIX: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2723 + Backports for older releases available as attachments here. ** Changed in: apport Status: In Progress => Fix Committed ** Changed in: apport Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1242435 Title: Desktop setuid cores readable by non-privileged user Status in Apport crash detection/reporting: Fix Released Status in “apport” package in Ubuntu: Triaged Status in “apport” source package in Lucid: Invalid Status in “apport” source package in Precise: Fix Released Status in “apport” source package in Quantal: Fix Released Status in “apport” source package in Raring: Fix Released Status in “apport” source package in Saucy: Fix Released Status in “apport” source package in Trusty: Triaged Bug description: Elsewhere I have been working on a sensitive information leak via core dump generated by gcore(1). The sensitive information in question is read by a stock setuid root binary executed by a non-privileged user. On Ubuntu Desktop fs.suid_dumpable=2. Referencing https://www.kernel.org/doc/Documentation/sysctl/fs.txt: 2 - (suidsafe) - any binary which normally would not be dumped is dumped anyway, but only if the "core_pattern" kernel sysctl is set to either a pipe handler or a fully qualified path. (For more details on this limitation, see CVE-2006-2451.) This mode is appropriate when administrators are attempting to debug problems in a normal environment, and either have a core dump pipe handler that knows to treat privileged core dumps with care, or specific directory defined for catching core dumps. If a core dump happens without a pipe handler or fully qualifid path, a message will be emitted to syslog warning about the lack of a correct setting. NB "treat privileged core dumps with care". On a stock Desktop 12.04 LTS install: kernel.core_pattern = |/usr/share/apport/apport %p %s %c apport dutifully dumps the core and this is readable (0660, user:user) by the invoking user, whereas it should be something like 0440, root:root. I believe this to be a bug in apport. TRUNK FIX: http://bazaar.launchpad.net/~apport-hackers/apport/trunk/revision/2723 Backports for older releases available as attachments here. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1242435/+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 1208183] Re: [HP G62 Notebook PC, ATI RS690/780 HDMI, Digital Out, HDMI] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1208183
Title:
[HP G62 Notebook PC, ATI RS690/780 HDMI, Digital Out, HDMI] No sound
at all
Status in “alsa-driver” package in Ubuntu:
Expired
Bug description:
no sound in HP laptop
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.5.0-37.58~precise1-generic 3.5.7.16
Uname: Linux 3.5.0-37-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC270 Analog [ALC270 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ignacio1767 F pulseaudio
/dev/snd/pcmC1D3p: ignacio1767 F...m pulseaudio
/dev/snd/controlC0: ignacio1767 F pulseaudio
Card0.Amixer.info:
Card hw:0 'SB'/'HDA ATI SB at 0xd230 irq 16'
Mixer name : 'Realtek ALC270'
Components : 'HDA:10ec0270,103c143b,00100100'
Controls : 22
Simple ctrls : 11
Card1.Amixer.info:
Card hw:1 'HDMI'/'HDA ATI HDMI at 0xd221 irq 19'
Mixer name : 'ATI RS690/780 HDMI'
Components : 'HDA:1002791a,00791a00,0010'
Controls : 4
Simple ctrls : 1
Card1.Amixer.values:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Sun Aug 4 15:38:47 2013
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386
(20130213)
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
Symptom_Card: RS880 HDMI Audio [Radeon HD 4200 Series] - HDA ATI HDMI
Symptom_DevicesInUse:
1767 1767 1767 ignacio F pulseaudio
/dev/snd/pcmC1D3p: ignacio F...m pulseaudio
/dev/snd/controlC0: ignacio F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [HP G62 Notebook PC, ATI RS690/780 HDMI, Digital Out, HDMI] No sound
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.2B
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 143B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 62.3E
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnHewlett-Packard:bvrF.2B:bd12/05/2011:svnHewlett-Packard:pnHPG62NotebookPC:pvr04971025271000102:rvnHewlett-Packard:rn143B:rvr62.3E:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP G62 Notebook PC
dmi.product.version: 04971025271000102
dmi.sys.vendor: Hewlett-Packard
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1208183/+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 1216639] Re: [7515A47, Realtek ALC662 rev1, Speaker, Internal] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1216639
Title:
[7515A47, Realtek ALC662 rev1, Speaker, Internal] No sound at all
Status in “alsa-driver” package in Ubuntu:
Expired
Bug description:
bug report
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
ProcVersionSignature: Ubuntu 3.2.0-52.78-generic-pae 3.2.48
Uname: Linux 3.2.0-52-generic-pae i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: Intel [HDA Intel], device 0: ALC662 rev1 Analog [ALC662 rev1 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu17.4
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cyberthrone 2443 F pulseaudio
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xfeaf8000 irq 44'
Mixer name : 'Realtek ALC662 rev1'
Components : 'HDA:10ec0662,17aa304f,00100101'
Controls : 29
Simple ctrls : 15
Date: Sat Aug 24 05:28:32 2013
InstallationMedia: Zorin 6 - Release i386
MarkForUpload: True
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
Symptom_Card: Built-in Audio - HDA Intel
Symptom_DevicesInUse:
(gksu:31101): Gtk-WARNING **: Theme directory of theme Azenis Red Icons has
no size field
2443 2443 cyberthrone F pulseaudio
/dev/snd/pcmC0D0p: cyberthrone F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [7515A47, Realtek ALC662 rev1, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 5HKT39AUS
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: LENOVO
dmi.board.version: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnLENOVO:bvr5HKT39AUS:bd06/17/2009:svnLENOVO:pn7515A47:pvrThinkCentreA58:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: 7515A47
dmi.product.version: ThinkCentre A58
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1216639/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
well, that was bad formatting, let's try this 13.04 i386 fresh install eclipse ubuntu package: good eclipse kepler sr1: good 13.10 i386 upgraded from 13.04 eclipse ubuntu package: bad eclipse kepler sr1: bad 13.10 x86_64 upgraded from 13.0 eclipse ubuntu package: ? eclipse kepler sr1: bad 13.10 i386 fresh install eclipse ubuntu package: bad eclipse kepler sr1: bad 13.10 x86_64 fresh install eclipse ubuntu package: good eclipse kepler sr1: bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) Expected: The content of the submenus show up Actual: Only the top-level headers seem to be available. Nothing happens when I click on them either. They don't show up in the HUD either. It worked fine on 13.04, so I'm not sure what changed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
"Are you experiencing this bug after updating your system?" Here is what I tested: eclipse ubuntu package eclipse kepler sr1 13.04 i386 fresh good good 13.10 i386 upgrade badbad 13.10 x86_64 upgrade ? bad 13.10 i386 fresh bad bad 13.10 x86_64 fresh good bad -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) Expected: The content of the submenus show up Actual: Only the top-level headers seem to be available. Nothing happens when I click on them either. They don't show up in the HUD either. It worked fine on 13.04, so I'm not sure what changed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+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 1219677] Re: if empathy start hidden it will fail to work with indicator-messages
Same problem. Ubuntu 13.10 x64, empathy 3.8.4-1ubuntu1 -- 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/1219677 Title: if empathy start hidden it will fail to work with indicator-messages Status in “empathy” package in Ubuntu: Confirmed Bug description: if empathy start hidden it will fail to work with indicator-messages. Simple test: run empathy -h in command line then try to open it from indicator-messages. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu4.1 Uname: Linux 3.11.0-999-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Mon Sep 2 09:32:45 2013 InstallationDate: Installed on 2013-08-31 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1219677/+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 1219677] Re: if empathy start hidden it will fail to work with indicator-messages
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: empathy (Ubuntu) Status: New => Confirmed -- 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/1219677 Title: if empathy start hidden it will fail to work with indicator-messages Status in “empathy” package in Ubuntu: Confirmed Bug description: if empathy start hidden it will fail to work with indicator-messages. Simple test: run empathy -h in command line then try to open it from indicator-messages. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: empathy 3.6.4-0ubuntu4.1 Uname: Linux 3.11.0-999-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Mon Sep 2 09:32:45 2013 InstallationDate: Installed on 2013-08-31 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: empathy UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1219677/+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 1242767] Re: computer freeze trying to exit "gnome-control-center"
running Mint 14 Cinnamon DE with exact same graphics card as VMC & using Nouveau driver & same AMD Athlon K8 X 2 Dual Core CPU same problem occurs..screen freezes & computer locks up have to do CTRL-ALT-F1 to get to terminal to reboot this doesn't always work...only way to get back up is to do hard power down and then restart also seen using Ubuntu 14.04 have NOT seen this using Ubuntu 12.04...yet -- 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/1242767 Title: computer freeze trying to exit "gnome-control-center" Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 13.10 Release: 13.10 === 2) gnome-control-center: Installed: 1:3.6.3-0ubuntu44 Candidate: 1:3.6.3-0ubuntu44 Version table: *** 1:3.6.3-0ubuntu44 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status 3) I expect to be able to exit System Settings (gnome-control-center), without freezing the computer 4) Clicking on the "X" to exit System Settings, the computer froze. No response whatsoever. A power cycle was needed. This happens using NOUVEAU driver only. If I install NVIDIA driver, then this problem does not occur. Hardware: VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) AMD Athlon(tm) II X2 250 Processor 4GB ram 650GB hard drive ProblemType: Bug DistroRelease: Ubuntu 13.10 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 21 08:51:15 2013 InstallationDate: Installed on 2013-10-19 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1242767/+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 1242767] Re: computer freeze trying to exit "gnome-control-center"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-nouveau (Ubuntu) Status: New => Confirmed -- 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/1242767 Title: computer freeze trying to exit "gnome-control-center" Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: 1) Description: Ubuntu 13.10 Release: 13.10 === 2) gnome-control-center: Installed: 1:3.6.3-0ubuntu44 Candidate: 1:3.6.3-0ubuntu44 Version table: *** 1:3.6.3-0ubuntu44 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status 3) I expect to be able to exit System Settings (gnome-control-center), without freezing the computer 4) Clicking on the "X" to exit System Settings, the computer froze. No response whatsoever. A power cycle was needed. This happens using NOUVEAU driver only. If I install NVIDIA driver, then this problem does not occur. Hardware: VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) AMD Athlon(tm) II X2 250 Processor 4GB ram 650GB hard drive ProblemType: Bug DistroRelease: Ubuntu 13.10 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 21 08:51:15 2013 InstallationDate: Installed on 2013-10-19 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1242767/+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 1244503] [NEW] clicking hyperlink in firefox logs out of gnome
Public bug reported:
Clicking a hyperlink in Firefox sometimes logs me out of GNOME (Classic,
i.e. gnome-panel). There is no warning or prompt asking me whether I
want to log out or not. I briefly see a black screen with white text
similar to the ones you see when shutting down from the command line,
then I am shown the typical Ubuntu login manager. I can then log in
again.
This problem occurs infrequently, and because I am immediately logged
out without warning, I cannot view the problematic code in a debugger.
Nor does the white text appear long enough for me to read what it says.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 24.0+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.5.0-42.65~precise1-generic 3.5.7.21
Uname: Linux 3.5.0-42-generic x86_64
NonfreeKernelModules: fglrx
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob3392 F pulseaudio
/dev/snd/pcmC0D0p: bob3392 F...m pulseaudio
BuildID: 20130911164256
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc360 irq 47'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103c1672,00100105
HDA:80862805,80860101,0010'
Controls : 24
Simple ctrls : 11
Channel: Unavailable
Date: Thu Oct 24 22:21:37 2013
ForcedLayersAccel: False
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64
(20130213)
IpRoute:
default via 192.168.4.40 dev eth0 proto static
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.119 metric 1
MarkForUpload: True
PrefSources: prefs.js
ProcEnviron:
LANGUAGE=en_CA:en
TERM=xterm
PATH=(custom, no user)
LANG=en_CA.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=24.0/20130911164256 (In use)
RelatedPackageVersions:
rhythmbox-mozilla 2.96-0ubuntu4.3
totem-mozilla 3.0.1-0ubuntu21.1
gnome-shell 3.4.1-0ubuntu2
RunningIncompatibleAddons: False
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2012
dmi.bios.vendor: Insyde
dmi.bios.version: F.63
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1672
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 09.4B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.63:bd03/22/2012:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1672:rvr09.4B:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion g7 Notebook PC
dmi.product.version: 05931120461620100
dmi.sys.vendor: Hewlett-Packard
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1244503
Title:
clicking hyperlink in firefox logs out of gnome
Status in “firefox” package in Ubuntu:
New
Bug description:
Clicking a hyperlink in Firefox sometimes logs me out of GNOME
(Classic, i.e. gnome-panel). There is no warning or prompt asking me
whether I want to log out or not. I briefly see a black screen with
white text similar to the ones you see when shutting down from the
command line, then I am shown the typical Ubuntu login manager. I can
then log in again.
This problem occurs infrequently, and because I am immediately logged
out without warning, I cannot view the problematic code in a debugger.
Nor does the white text appear long enough for me to read what it
says.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: firefox 24.0+build1-0ubuntu0.12.04.1
ProcVersionSignature: Ubuntu 3.5.0-42.65~precise1-generic 3.5.7.21
Uname: Linux 3.5.0-42-generic x86_64
NonfreeKernelModules: fglrx
AddonCompatCheckDisabled: False
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.25.
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: STAC92xx Analog [STAC92xx Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bob3392 F pulseaudio
/dev/snd/pcmC0D0p: bob3392 F...m pulseaudio
BuildID: 20130911164256
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xc360 irq 47'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:111d7605,103
[Desktop-packages] [Bug 1244499] Re: Minor inconsistency in UI under Appearance with regard to the suto-hide functionality
** Attachment added: "normalbehavior.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+attachment/3890560/+files/normalbehavior.png -- 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/1244499 Title: Minor inconsistency in UI under Appearance with regards to the auto- hide functionality in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under "Appearance" and under the "Behavior" tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto-hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto- hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+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 1244499] [NEW] Minor inconsistency in UI under Appearance with regards to the auto-hide functionality in Saucy
Public bug reported: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under "Appearance" and under the "Behavior" tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto- hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto-hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed saucy -- 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/1244499 Title: Minor inconsistency in UI under Appearance with regards to the auto- hide functionality in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under "Appearance" and under the "Behavior" tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto-hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto- hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+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 1244499] Re: Minor inconsistency in UI under Appearance with regard to the suto-hide functionality
** Attachment added: "aftertwotoggles.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+attachment/3890561/+files/aftertwotoggles.png ** Summary changed: - Minor inconsistency in UI under Appearance with regard to the suto-hide functionality + Minor inconsistency in UI under Appearance with regard to the auto-hide functionality in Saucy ** Summary changed: - Minor inconsistency in UI under Appearance with regard to the auto-hide functionality in Saucy + Minor inconsistency in UI under Appearance with regards to the auto-hide functionality in Saucy -- 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/1244499 Title: Minor inconsistency in UI under Appearance with regards to the auto- hide functionality in Saucy Status in “gnome-control-center” package in Ubuntu: New Bug description: Minor bug. I've noticed that when I toggle on auto hide and toggle it off under "Appearance" and under the "Behavior" tab, I can still adjust the reveal location and reveal sensitivity even with the option to auto-hide the launcher toggled off again. Only happens after a toggle on and off. The behavior should be to grey out the options once disabled again and not allow the user to select them until the auto- hide option is enabled again. Running the latest updates on 64 bit Saucy. Screenshots coming up. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-control-center 1:3.6.3-0ubuntu45 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 24 22:15:55 2013 InstallationDate: Installed on 2013-10-17 (7 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager 0.9.7-0ubuntu4 deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1244499/+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 246701] Re: Change Scroll Region and display glitch
** Changed in: vte Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte in Ubuntu. https://bugs.launchpad.net/bugs/246701 Title: Change Scroll Region and display glitch Status in Gnome Virtual Terminal Emulator: Confirmed Status in “vte” package in Ubuntu: Fix Released Bug description: Please describe the problem: After sending CSR so that the final line in the terminal is excluded from the scroll region, glitches can occur when interspersing writes to the bottom line with scrolls of the upper region. Steps to reproduce: I will attach a script (scr-fix-min) that produces the problem for me. NOTE: This script expects LINES and COLUMNS to be exported and refer to the number of lines and columns in your terminal. These must be accurate or the bug won't be shown. If they are unset, you will get a ton of errors, rather than the simulation. If one is running bash, then $ export COLUMNS LINES $ ./scr-fix-min will probably work. Otherwise, COLUMNS and LINES may need to be set explicitly before running the script. Actual results: What I currently see: one or both of "foo" and "bar" are missing. Or, on at least one system, the bar will be black/empty when it ought to be reversed/have-text. Actually, when I _should_ see "foo" and "bar", but don't, I will sometimes actually see an effect such that it looks like the top one or two pixel-rows of the bottom line update and switch back, but not the rest of the line. So a masking problem or incorrect information about what portions of the display to update seem likely. Expected results: What you ought to see: the bottom bar flash between "x", "foo", "x", and "bar". Does this happen every time? This reproduces reliably for me on gnome-terminal. xfce4-terminal sometimes shows both "foo" and "bar" as it ought to, and sometimes doesn't (same app, same instance, different runs of script). Other information: This behavior was discovered while I was using screen, which can use the final line as a "status" line. I was playing with screen's "autoaka" feature, which allows the current screen window's name to change based on the currently-running command: I found that everything worked as it should until the prompt reached the bottom, so that hitting enter caused scrolling. At that point, the window title would stop updating. To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/246701/+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 1242767] Re: computer freeze trying to exit "gnome-control-center"
I also have a freezing problem with Ubuntu 13.10 Here is what I posted this morning in the "General" forum: Hello, my system randomly freezes when I login with the Ubuntu (default) desktop but does not when I use the Gnome flashback (no effects) desktop. I haven't login using the regular Gnome flashback desktop. The freezes happen doing simple things. It did also happen with Ubuntu 13.04 I have an Nvidia GeForce GT 240 (GT 215) video card I did a system test and what got tested passed Memory 7.8 GiB Processor Intel Pentium(R) D CPU 3.20GHz x 2 Graphics Gallium 0.4 on NVA3 OS type 64-bit Disk 23.6 GB -- 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/1242767 Title: computer freeze trying to exit "gnome-control-center" Status in “xserver-xorg-video-nouveau” package in Ubuntu: New Bug description: 1) Description: Ubuntu 13.10 Release: 13.10 === 2) gnome-control-center: Installed: 1:3.6.3-0ubuntu44 Candidate: 1:3.6.3-0ubuntu44 Version table: *** 1:3.6.3-0ubuntu44 0 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status 3) I expect to be able to exit System Settings (gnome-control-center), without freezing the computer 4) Clicking on the "X" to exit System Settings, the computer froze. No response whatsoever. A power cycle was needed. This happens using NOUVEAU driver only. If I install NVIDIA driver, then this problem does not occur. Hardware: VGA compatible controller: NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) AMD Athlon(tm) II X2 250 Processor 4GB ram 650GB hard drive ProblemType: Bug DistroRelease: Ubuntu 13.10 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Mon Oct 21 08:51:15 2013 InstallationDate: Installed on 2013-10-19 (2 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 27.3.1-0ubuntu1 gnome-control-center-datetime 13.10.0+13.10.20131016.2-0ubuntu1 gnome-control-center-signon 0.1.7~+13.10.20130724.1-0ubuntu1 gnome-control-center-unity1.3+13.10.20131004-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1242767/+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 1037357] Re: at-spi2-registryd crashed with SIGSEGV in register_client()
** Description changed: + Impact: + Users occasionally experience crashes from at-spi2-registryd on their system, even though they may not be using any applications that use at-spi. + + Regression potential: + Minimal to nonexistant. The proposed patch adds extra checks to make sure there is an error mesage. + . ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: at-spi2-core 2.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Wed Aug 15 20:21:02 2012 ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1) ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb77305bf : mov0x8(%eax),%eax PC (0xb77305bf) ok source "0x8(%eax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: at-spi2-core Stacktrace: #0 0xb77305bf in main () No symbol table info available. StacktraceTop: main () Title: at-spi2-registryd crashed with SIGSEGV in main() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo ** Also affects: at-spi2-core (Ubuntu Saucy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1037357 Title: at-spi2-registryd crashed with SIGSEGV in register_client() Status in Assistive Technology Service Provider Interface: Fix Released Status in “at-spi2-core” package in Ubuntu: Fix Released Status in “at-spi2-core” source package in Saucy: New Bug description: Impact: Users occasionally experience crashes from at-spi2-registryd on their system, even though they may not be using any applications that use at-spi. Regression potential: Minimal to nonexistant. The proposed patch adds extra checks to make sure there is an error mesage. . ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: at-spi2-core 2.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Wed Aug 15 20:21:02 2012 ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1) ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb77305bf : mov0x8(%eax),%eax PC (0xb77305bf) ok source "0x8(%eax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: at-spi2-core Stacktrace: #0 0xb77305bf in main () No symbol table info available. StacktraceTop: main () Title: at-spi2-registryd crashed with SIGSEGV in main() 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/at-spi/+bug/1037357/+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 1244498] [NEW] Installing opencl causes intel glx module to fail loading
Public bug reported: I installed libopencl-dev on my laptop with an i915 chipset. This in turn caused the libopencv-ocl2.4 dependency to be installed, which in turn caused the nvidia-304 packages to be installed to satisfy the libopencl1 virtual package dependency. Afterwards, when I restarted my computer, unity wouldn't load and I found an error message in Xorg.log stating that the *Nvidia* glx module had failed to load. The workaround was to: apt-get remove nvidia-304 nvidia-304-updates apt-get install libopencl-dev ocl-icd-libopencl1 I will post the exact log contents tomorrow. ** Affects: xserver-xorg-video-intel (Ubuntu) Importance: Undecided Status: New ** Tags: saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1244498 Title: Installing opencl causes intel glx module to fail loading Status in “xserver-xorg-video-intel” package in Ubuntu: New Bug description: I installed libopencl-dev on my laptop with an i915 chipset. This in turn caused the libopencv-ocl2.4 dependency to be installed, which in turn caused the nvidia-304 packages to be installed to satisfy the libopencl1 virtual package dependency. Afterwards, when I restarted my computer, unity wouldn't load and I found an error message in Xorg.log stating that the *Nvidia* glx module had failed to load. The workaround was to: apt-get remove nvidia-304 nvidia-304-updates apt-get install libopencl-dev ocl-icd-libopencl1 I will post the exact log contents tomorrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1244498/+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 1236346] Re: at-spi2-registryd.conf upstart script missing closing ']'
** Also affects: at-spi2-core (Ubuntu Saucy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1236346 Title: at-spi2-registryd.conf upstart script missing closing ']' Status in “at-spi2-core” package in Ubuntu: Fix Released Status in “at-spi2-core” source package in Saucy: New Bug description: Impact At-spi2 does run, but the missing closing bracket in the upstart config file may be causing the gsettings check to fail. In addition, the following is shown in the user's local upstart logs for at-spi2-registryd: /proc/self/fd/9: 2: [: missing ] Regression potential: Little to none at all given that this was a typo. Hi, I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at- spi2-registryd.log. It seems this is because the 'pre-start' stanza is missing a closing ']' as shown below: pre-start script [ "$(gsettings get org.gnome.desktop.interface toolkit-accessibility)" \ = "true" || exit 0 end script It seems like an easy fix but I can't seem to find which LP branch to create a merge proposal against. Regards, Haw --- ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: at-spi2-core 2.10.0-0ubuntu2 [modified: usr/share/upstart/sessions/at-spi2-registryd.conf] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified] mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 2013-07-24T01:24:45.829666 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+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 1222873] Re: No sound at all in Saucy
The fix is the same as the fix for the sound issues in Skype: sudo sed -i 's/^Exec=.*/Exec=env PULSE_LATENCY_MSEC=30 audacity %U/' /usr/share/applications/audacity.desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1222873 Title: No sound at all in Saucy Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi, I upgraded to Saucy Salamander the last week. Sound output was working normally until today. Today I had to use Mumble to talk to my team, but sound input was not working, so I tried switching from PulseAudio to Alsa in the Mumble configuration, and that made my whole sound (input and output) go away. I can't hear anything anymore, neither in Mumble, or in the sound test from system settings, or in Rhythmbox, or anything else. No sound at all. Can you guys help me sort this out, please? Extra info: $ ▶lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch:security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch Distributor ID: Ubuntu Description: Ubuntu Saucy Salamander (development branch) Release: 13.10 Codename: saucy $ ▶apt-cache policy pulseaudio pulseaudio: Instalado: 1:4.0-0ubuntu2+build1 Candidato: 1:4.0-0ubuntu2+build1 Tabela de versão: *** 1:4.0-0ubuntu2+build1 0 500 http://br.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages 100 /var/lib/dpkg/status Thanks, Diogo ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: pulseaudio 1:4.0-0ubuntu2+build1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: diogobaeder 3039 F pulseaudio /dev/snd/controlC1: diogobaeder 3039 F pulseaudio /dev/snd/controlC0: diogobaeder 3039 F pulseaudio Date: Mon Sep 9 11:57:20 2013 InstallationDate: Installed on 2012-12-02 (280 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) MarkForUpload: True SourcePackage: pulseaudio UpgradeStatus: Upgraded to saucy on 2013-09-05 (3 days ago) dmi.bios.date: 03/10/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8P67 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.:bvr1503:bd03/10/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8P67:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1222873/+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 1244488] [NEW] help
Public bug reported: help ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 24 23:42:32 2013 DistUpgraded: 2013-10-17 16:19:13,731 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu InstallationDate: Installed on 2013-07-16 (100 days ago) InstallationMedia: Megalinux Diamante 12.04 "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 003: ID 090c:37c0 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Silicon Motion Camera Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEGAWARE SLIMBLACK MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=236cd8c2-8616-44af-be42-55dba7694668 ro splash acpi_os_name=Linux quiet acpi_osi= SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-17 (7 days ago) dmi.bios.date: 07/05/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 71R dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SLIMBLACK dmi.board.vendor: MEGAWARE dmi.board.version: EC 1.17Y dmi.chassis.asset.tag: M0626201001 dmi.chassis.type: 9 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr71R:bd07/05/2012:svnMEGAWARE:pnSLIMBLACK:pvr0.1:rvnMEGAWARE:rnSLIMBLACK:rvrEC1.17Y:cvnMEGAWARE:ct9:cvr0.1: dmi.product.name: SLIMBLACK dmi.product.version: 0.1 dmi.sys.vendor: MEGAWARE version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 24 22:10:24 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1479 vendor BOE xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 saucy ubuntu -- 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/1244488 Title: help Status in “xorg” package in Ubuntu: New Bug description: help ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic i686 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 Date: Thu Oct 24 23:42:32 2013 DistUpgraded: 2013-10-17 16:19:13,731 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu InstallationDate: Installed on 2013-07-16 (100 days ago) InstallationMedia: Megalinux Diamante 12.04 "Precise Pangolin" - Release i386 (20120423) Lsusb: Bus 002 Device 003: ID 090c:37c0 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Silicon Motion Camera Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEGAWARE SLIMBLACK MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-13-generic root=UUID=236cd8c2-8616-44af-be42-55dba7694668 ro splash acpi_os_name=Linux quiet acpi_osi= SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-17 (7 days ago) dmi.bios.date: 07/05/2012 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: 71R dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SLIMBLACK dmi.board.vendor: MEGAWARE dmi.board.version: EC 1.17Y dmi.chassis.asset.tag: M0626201001 dmi.chassis.type: 9 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvr71R:bd07/05/2012:svnMEGAWARE:pnSLIMBLACK:pvr0.1:rvnMEGAWARE:rnSLIMBLACK:rvrEC1.17Y:cvnMEGAWARE:ct9:cvr0.1: dmi.product.name: SLIMBLACK dmi.product.version: 0.1 dmi.sys.vendor: MEGAWARE version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.46-
[Desktop-packages] [Bug 1236346] Re: at-spi2-registryd.conf upstart script missing closing ']'
** Description changed: Impact - At-spi2 does run, but the missing closing bracket in the upstart config file may be causing the gsettings check to fail. In additino, the following is shown in the user's local upstart logs for at-spi2-registryd: + At-spi2 does run, but the missing closing bracket in the upstart config file may be causing the gsettings check to fail. In addition, the following is shown in the user's local upstart logs for at-spi2-registryd: /proc/self/fd/9: 2: [: missing ] Regression potential: Little to none at all given that this was a typo. Hi, I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at- spi2-registryd.log. It seems this is because the 'pre-start' stanza is missing a closing ']' as shown below: pre-start script [ "$(gsettings get org.gnome.desktop.interface toolkit-accessibility)" \ = "true" || exit 0 end script It seems like an easy fix but I can't seem to find which LP branch to create a merge proposal against. Regards, Haw --- ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: at-spi2-core 2.10.0-0ubuntu2 [modified: usr/share/upstart/sessions/at-spi2-registryd.conf] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified] mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 2013-07-24T01:24:45.829666 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1236346 Title: at-spi2-registryd.conf upstart script missing closing ']' Status in “at-spi2-core” package in Ubuntu: Fix Released Bug description: Impact At-spi2 does run, but the missing closing bracket in the upstart config file may be causing the gsettings check to fail. In addition, the following is shown in the user's local upstart logs for at-spi2-registryd: /proc/self/fd/9: 2: [: missing ] Regression potential: Little to none at all given that this was a typo. Hi, I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at- spi2-registryd.log. It seems this is because the 'pre-start' stanza is missing a closing ']' as shown below: pre-start script [ "$(gsettings get org.gnome.desktop.interface toolkit-accessibility)" \ = "true" || exit 0 end script It seems like an easy fix but I can't seem to find which LP branch to create a merge proposal against. Regards, Haw --- ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: at-spi2-core 2.10.0-0ubuntu2 [modified: usr/share/upstart/sessions/at-spi2-registryd.conf] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified] mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 2013-07-24T01:24:45.829666 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1184262] Re: [logind] stuck in PrepareForSleep, causing network and other services to not resume
This does work for me, every time: sudo nmcli nm sleep false On 10/24/2013 06:14 PM, Alexander List wrote: > I observed the same bug with current Saucy. Hardware is Lenovo TP x201 > using iwlwifi. > > After resume from suspend, networking is disabled. Enabling it in nm- > applet has no effect. > -- 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 1226861] Re: [snb mesa] False GPU lockup IPEHR: 0x7a000002
*** This bug is a duplicate of bug 1223332 *** https://bugs.launchpad.net/bugs/1223332 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xserver-xorg-video-intel (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1226861 Title: [snb mesa] False GPU lockup IPEHR: 0x7a02 Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: This error pop-ups periodically, perhaps every time updates manager checks for new updates available. It's started today after latest updates installed for Ubuntu 13.10 Beta. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu4 Architecture: amd64 Chipset: sandybridge-gt1 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Sep 17 17:13:53 2013 DistUpgraded: 2013-09-15 00:31:25,960 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu DuplicateSignature: [sandybridge-gt1] GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 Ubuntu 13.10 ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2002] InstallationDate: Installed on 2012-03-27 (539 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) InterpreterPath: /usr/bin/python3.3 MarkForUpload: True ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=4671f462-9fab-4e72-8455-9cf78335dffc ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu5 libdrm2 2.4.46-1 xserver-xorg-video-intel 2:2.21.14-4ubuntu4 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-gt1] False GPU lockup IPEHR: 0x7a02 IPEHR: 0x0100 UpgradeStatus: Upgraded to saucy on 2013-09-14 (3 days ago) UserGroups: dmi.bios.date: 12/22/2011 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0146.2011.1222.1415 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67BL dmi.board.vendor: Intel Corporation dmi.board.version: AAG10189-211 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0146.2011.1222.1415:bd12/22/2011:svn:pn:pvr:rvnIntelCorporation:rnDH67BL:rvrAAG10189-211:cvn:ct3:cvr: version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Wed Sep 18 08:27:45 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17410 vendor SNY xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1226861/+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 1172639] Re: package cups 1.6.1-0ubuntu11.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1172639 Title: package cups 1.6.1-0ubuntu11.3 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 Status in “cups” package in Ubuntu: Confirmed Bug description: Cups doesn't start after install because cups is not configured and return an error. After moved the default conf file (cupsd.conf.default) to cupsd.conf, cups start. ProblemType: Package DistroRelease: Ubuntu 12.10 Package: cups 1.6.1-0ubuntu11.3 ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7 Uname: Linux 3.5.0-27-generic i686 ApportVersion: 2.6.1-0ubuntu10 AptOrdering: cups: Install printer-driver-gutenprint: Install cups: Configure printer-driver-gutenprint: Configure Architecture: i386 CupsErrorLog: C [25/Apr/2013:11:27:01 +0200] Unable to open /etc/cups/cupsd.conf: No such file or directory C [25/Apr/2013:11:27:04 +0200] Unable to open /etc/cups/cupsd.conf: No such file or directory C [25/Apr/2013:11:27:07 +0200] Unable to open /etc/cups/cupsd.conf: No such file or directory C [25/Apr/2013:11:27:10 +0200] Unable to open /etc/cups/cupsd.conf: No such file or directory Date: Thu Apr 25 11:27:10 2013 ErrorMessage: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 InstallationDate: Installed on 2012-12-17 (128 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Transport endpoint is not connected MachineType: System manufacturer System Product Name MarkForUpload: True Papersize: a4 PpdFiles: hp_LaserJet_9040_MFP: HP LaserJet 9040 MFP hpijs pcl3, 3.12.6 Hewlett-Packard-HP-Color-LaserJet-CP4520-Series: HP Color LaserJet CP4020-CP4520 Series Postscript (recommended) hp_LaserJet_4345_mfp: HP LaserJet 4345 MFP pcl3, hpcups 3.12.6 Hewlett-Packard-hp-LaserJet-9040-MFP: HP LaserJet 9040 9050 MFP Postscript (recommended) Hewlett-Packard-hp-color-LaserJet-9500: HP Color LaserJet 9500 Postscript (recommended) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic root=UUID=9f599e5a-223b-454c-a5ac-20a372d76ec4 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-27-generic root=UUID=9f599e5a-223b-454c-a5ac-20a372d76ec4 ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups 1.6.1-0ubuntu11.3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0316 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: V-P5G43 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: R1.04G dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0316:bd02/25/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnV-P5G43:rvrR1.04G:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.cups.cupsd.conf: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1172639/+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
I observed the same bug with current Saucy. Hardware is Lenovo TP x201 using iwlwifi. After resume from suspend, networking is disabled. Enabling it in nm- applet has no effect. -- 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 1236012]
Removing comma from whiteboard (please use a space to delimit values in this field) https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Whiteboard#Getting_Started -- 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/1236012 Title: [KUBUNTU] Calc freezes screen when using drag-and-drop on cells Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Dragging selected cells causes screen to freeze in KDE Steps to reproduce: Open a spreadsheet with Calk. Select a group of cells with mouse. Drag selected cells. Outcome: Screen freezes, cells not moved. Mouse is still responsive, but typing/clicking does not work. Usually, switching to a vt then back will clear this freeze. Reproducibility: 100% Using the right-click context menu or keyboard shortcuts for moving selected cells works as expected. Removal of the package libreoffice-kde fixes this at the expense of the look-and-feel the package provides. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice-calc 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Oct 6 12:24:45 2013 InstallationDate: Installed on 2013-08-10 (56 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to saucy on 2013-09-06 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1236012/+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 1236012]
This is also happening to me. -Kubuntu 13.10, KDE 4.11.2, LibreOffice 4.1.2.3 410m0(Build:3), kernel 3.11.0-12-generic #19-Ubuntu. I also confirm that removing libreoffice-kde-4.1.2~rc3-0ubuntu1 does fix the problem. I've also tried to switch off hardware acceleration and anti-aliasing with no success. -- 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/1236012 Title: [KUBUNTU] Calc freezes screen when using drag-and-drop on cells Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Dragging selected cells causes screen to freeze in KDE Steps to reproduce: Open a spreadsheet with Calk. Select a group of cells with mouse. Drag selected cells. Outcome: Screen freezes, cells not moved. Mouse is still responsive, but typing/clicking does not work. Usually, switching to a vt then back will clear this freeze. Reproducibility: 100% Using the right-click context menu or keyboard shortcuts for moving selected cells works as expected. Removal of the package libreoffice-kde fixes this at the expense of the look-and-feel the package provides. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice-calc 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Oct 6 12:24:45 2013 InstallationDate: Installed on 2013-08-10 (56 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to saucy on 2013-09-06 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1236012/+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 1236012]
*** Bug 70614 has been marked as a duplicate of this bug. *** -- 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/1236012 Title: [KUBUNTU] Calc freezes screen when using drag-and-drop on cells Status in LibreOffice Productivity Suite: Confirmed Status in “libreoffice” package in Ubuntu: Confirmed Bug description: Dragging selected cells causes screen to freeze in KDE Steps to reproduce: Open a spreadsheet with Calk. Select a group of cells with mouse. Drag selected cells. Outcome: Screen freezes, cells not moved. Mouse is still responsive, but typing/clicking does not work. Usually, switching to a vt then back will clear this freeze. Reproducibility: 100% Using the right-click context menu or keyboard shortcuts for moving selected cells works as expected. Removal of the package libreoffice-kde fixes this at the expense of the look-and-feel the package provides. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libreoffice-calc 1:4.1.2~rc3-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Sun Oct 6 12:24:45 2013 InstallationDate: Installed on 2013-08-10 (56 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to saucy on 2013-09-06 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1236012/+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 1242118] Re: no more subwoofer test sound very weak sound since 13.10
** Description changed: There is no subwoofer TEST sound since 13.10. I feel subwoofer moving - slightly. + slightly when I play loud music loudly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1242118 Title: no more subwoofer test sound very weak sound since 13.10 Status in “ubuntu-sounds” package in Ubuntu: New Bug description: There is no subwoofer TEST sound since 13.10. I feel subwoofer moving slightly when I play loud music loudly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-sounds/+bug/1242118/+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 1244477] [NEW] Cheese-cabina de camara web
Public bug reported: Cuando instalé skaype aparece el mensaje "no hay camara conectada" . Luego no mantaniendo el lanzador de skype, la camara sigue sin funcionar. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.88 Wed Mar 27 14:31:12 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.1 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Oct 24 17:57:09 2013 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.88, 3.11.0-12-generic, i686: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C51 [GeForce Go 6150] [10de:0244] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Presario V6133CL [103c:30b7] InstallationDate: Installed on 2013-10-18 (6 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) Lsusb: Bus 001 Device 002: ID 05e3:0715 Genesys Logic, Inc. USB 2.0 microSD Reader Bus 001 Device 005: ID 046d:09a1 Logitech, Inc. QuickCam Communicate MP/S5500 Bus 001 Device 004: ID 19d2:0031 ZTE WCDMA Technologies MSM MF110/MF627/MF636 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Hewlett-Packard HP Pavilion dv6000 (RG253UA#ABA) MarkForUpload: True ProcEnviron: LANGUAGE=es_SV:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_SV.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=4c37a56c-c562-4682-848b-81e57b7a1224 ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.40 dmi.board.name: 30B7 dmi.board.vendor: Quanta dmi.board.version: 65.2C dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.40:bd08/01/2008:svnHewlett-Packard:pnHPPaviliondv6000(RG253UA#ABA):pvrRev1:rvnQuanta:rn30B7:rvr65.2C:cvnQuanta:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6000 (RG253UA#ABA) dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.14.3-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Oct 24 17:01:34 2013 xserver.configfile: default xserver.errors: Failed to load /usr/lib/xorg/modules/libglamoregl.so: /usr/lib/xorg/modules/libglamoregl.so: undefined symbol: _glapi_tls_Context Failed to load module "glamoregl" (loader failed, 7) open /dev/dri/card0: No such file or directory open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.3-3ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 saucy ubuntu -- 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/1244477 Title: Cheese-cabina de camara web Status in “xorg” package in Ubuntu: New Bug description: Cuando instalé skaype aparece el mensaje "no hay camara conectada" . Luego no mantaniendo el lanzador de skype, la camara sigue sin funcionar. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.88 Wed Mar 27 14:31:12 PDT 2013 GCC version: gcc version 4.8.1 (Ubuntu/Linaro 4.8.1-10ubuntu8) .tmp.unity.support.
[Desktop-packages] [Bug 1134028] Re: [Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for Radeon HD 7600M Series
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fglrx-installer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1134028 Title: [Dell Vostro 3560, Inspiron 5520] fglrx does not provide glx for Radeon HD 7600M Series Status in “fglrx-installer” package in Ubuntu: Confirmed Bug description: cid:201202-10402, 201201-10378 There are no glx support with fglrx_experimental_9 for Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] [1002:6840]. Checking unity compatibility by following command: $ /usr/lib/nux/unity_support_test -c -p X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 Pacakages that installed by jockey: ii fglrx-amdcccle-experimental-92:9.010-0ubuntu0.3 Catalyst Control Center for the AMD graphics accelerators ii fglrx-experimental-9 2:9.010-0ubuntu0.3 Experimental AMD binary Xorg driver and kernel module rc fglrx-updates2:9.000-0ubuntu0.3 Video driver for the AMD graphics accelerators However it can be fix by using latest stable driver[0] from amd website[1], following this guide: https://help.ubuntu.com/community/BinaryDriverHowto/ATI GLX will be loaded without error. [0]http://www2.ati.com/drivers/linux/amd-driver-installer-catalyst-13.1-linux-x86.x86_64.zip [1]http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: fglrx (not installed) ProcVersionSignature: Ubuntu 3.5.0-23.35~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-23-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: None Date: Wed Feb 27 01:37:19 2013 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-experimental-9, 9.010, 3.5.0-23-generic, x86_64: installed GraphicsCard: Intel Corporation Ivy Bridge Graphics Controller [8086:0166] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] Advanced Micro Devices [AMD] nee ATI Thames XT/GL [Radeon HD 7600M Series] [1002:6840] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:056e] InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) JockeyStatus: xorg:fglrx_experimental_9 - ATI/AMD proprietary FGLRX graphics driver (**experimental** beta) (Proprietary, Enabled, Not in use) xorg:fglrx_updates - ATI/AMD proprietary FGLRX graphics driver (post-release updates) (Proprietary, Disabled, Not in use) MachineType: Dell Inc. Vostro 3560 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-23-generic root=UUID=644b13de-02c4-40f5-afa6-3b8cbcf262c9 ro quiet splash initcall_debug vt.handoff=7 SourcePackage: fglrx-installer UnitySupportTest: Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 19 (X_GLXQueryServerString) Serial number of failed request: 22 Current serial number in output stream: 22 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: X44 dmi.board.name: 0C05GV dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X44 dmi.modalias: dmi:bvnDellInc.:bvrX44:bd08/03/2012:svnDellInc.:pnVostro3560:pvrX44:rvnDellInc.:rn0C05GV:rvrX01:cvnDellInc.:ct8:cvrX44: dmi.product.name: Vostro 3560 dmi.product.version: X44 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.39-0ubuntu0.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A
[Desktop-packages] [Bug 1243904] Re: keyboard doesn't work in 13.10
hi, does anything work - e.g. mouse move? Does an external usb keyboard work? ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1243904 Title: keyboard doesn't work in 13.10 Status in “ibus” package in Ubuntu: Incomplete Bug description: Hello. I updated from 13.04 to 13.10 but the keyboard did not work. I tried doing a fresh install but the keyboard did not work with the live cd. In 13.04 all works correctly My laptop is a lg p1 express dual Thank you very much To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1243904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
> > sudo apt-get update > sudo apt-get upgrade > > should update the packages affected Yup, that should do it! But for people looking to upgrade this single package only, and not their whole system, or others like Austin, the package name is: network-manager-gnome Odd. I know. Caught me off-guard when I first set out too. -- 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/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: New Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 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.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1231447] Re: Alt+Print Screen only takes picture of launcher
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-screenshot (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1231447 Title: Alt+Print Screen only takes picture of launcher Status in “gnome-screenshot” package in Ubuntu: Confirmed Bug description: In 13.10, pressing "Alt+Print Screen" always takes a screenshot of the launcher and not of the active window. This was fixed in 13.04, ref. bug number 1072199. To replicate: 1. Start a program such as "gedit". 2. Press Alt+PrintScreen * What happens: gnome-screenshot takes a screenshot of the Launcher (due to the Dash that gets invoked). * What should happen: gnome-screenshot should take a screenshot of just the "gedit" window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1231447/+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 1176415] Re: Unable to enable IPv6 Privacy Extensions on eth0
Still seeing this bug (ie. no automatic file creation in /etc/NetworkManager/system-connections/) in 13.10 however it has morphed slightly. After performing a fresh install, the system creates an IPv6 address consisting of the network prefix followed by an arbitrary number (well...I'm sure there's an algorithm/mechanism for generating it) for the last octet (eg. 2001:0DB8:DEAD:BEEF::123/128) and proceeds to prefer this address instead of the Modified EUI-64 address. After following steps 6-9 above, NetworkManager starts generating and preferring privacy addresses even though the /128 still lingers. This is all likely due to the revision bump to 0.9.8.0-0ubuntu22. It's also worth noting that my router runs a recent trunk build of OpenWrt utilizing 6relayd. -- 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/1176415 Title: Unable to enable IPv6 Privacy Extensions on eth0 Status in “network-manager” package in Ubuntu: Confirmed Bug description: This is on a fresh install of 13.04. Network Manager keeps defaulting net.ipv6.conf.all.use_tempaddr back to 0. I'm fairly confident this problem did not exist in 12.10, but feel free to squash this ticket if it is indeed a duplicate of #990011. Confirmed net.ipv6.conf.all.use_tempaddr is also set to 0 on my laptop running 13.04. Luckily I use eth1 (wifi in this case) which seems unaffected. $ ls /proc/sys/net/ipv6/conf/ all default eth0 lo $ cat /proc/sys/net/ipv6/conf/*/use_tempaddr 2 2 0 2 $ sudo sysctl net.ipv6.conf.all.use_tempaddr=0 net.ipv6.conf.all.use_tempaddr = 0 $ cat /proc/sys/net/ipv6/conf/*/use_tempaddr 0 0 0 0 $ sudo sysctl net.ipv6.conf.all.use_tempaddr=2 net.ipv6.conf.all.use_tempaddr = 2 $ cat /proc/sys/net/ipv6/conf/*/use_tempaddr 2 2 0 2 $ sudo sysctl net.ipv6.conf.eth0.use_tempaddr=2 net.ipv6.conf.eth0.use_tempaddr = 2 $ cat /proc/sys/net/ipv6/conf/eth0/use_tempaddr 0 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.8.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.8.0-19.30-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Sat May 4 12:25:29 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-04-27 (7 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev eth0 proto static 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.213 metric 1 IwConfig: eth0 no wireless extensions. lono wireless extensions. MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Wired connection 1ddad2c33-3c6c-44c6-aa1a-51a13560b698 802-3-ethernet1367695468 Sat 04 May 2013 12:24:28 PM PDTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1176415/+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 1241258] Re: wallpaper doesn't span across multiple monitors, white background shows instead
I get the issue in whatever session I open first. If I log out and log back in, the problem vanishes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1241258 Title: wallpaper doesn't span across multiple monitors, white background shows instead Status in “nautilus” package in Ubuntu: Incomplete Bug description: Wallpaper should span across my two monitors (it worked in ubuntu 13.04). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 17 19:38:59 2013 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1263x880+655+24'" b'org.gnome.nautilus.window-state' b'sidebar-width' b'236' InstallationDate: Installed on 2013-10-17 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1241258/+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 1101903] Re: Constantly rising memory usage by gnome-panel
** Tags added: raring saucy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1101903 Title: Constantly rising memory usage by gnome-panel Status in Desktop panel for GNOME: Unknown Status in “gnome-panel” package in Ubuntu: Confirmed Bug description: At login, gnome-panel uses about 1% of my system memory (5973600kb) as determined by "ps u". This rises at the rate of 1-2% per hour that I am logged on. Simultaneously, free swap memory starts to decrease from its initial value of 5858300kb. If I stay logged in long enough (3-4 days), there is little free memory, and trying to launch applications results in a window stating: Could not launch 'package name' Failed to fork (Cannot allocate memory) Though they can be started on the command line from an open xterm. Logging out and logging in releases memory. killall -9 gnome-panel releases almost all memory -- some swap memory is still used. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-panel 1:3.6.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-22.34-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Sat Jan 19 15:57:26 2013 ExecutablePath: /usr/bin/gnome-panel GsettingsChanges: b'org.gnome.gnome-panel.run-dialog' b'show-program-list' b'true' InstallationDate: Installed on 2011-05-29 (600 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) MarkForUpload: True SourcePackage: gnome-panel UpgradeStatus: Upgraded to quantal on 2012-11-12 (68 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-panel/+bug/1101903/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
I can verify that the -proposed packages restore the ability to use Alt+Shift and, more importantly, Shift+Shift. Some combinations, however, still do not work. Alt+Alt is still broken (as it has been for years now, unfortunately). Trying to use that shortcut gets misinterpreted. Any chance for a full fix? -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in One Hundred Papercuts: Invalid Status in Indicator keyboard: Invalid Status in Ubuntu GNOME: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “indicator-keyboard” package in Ubuntu: Invalid Status in “gnome-control-center” source package in Saucy: Fix Committed Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Status in “indicator-keyboard” source package in Saucy: Invalid Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1218322/+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
I have the same problem as #33 (julo), where my laptop automatically goes back to suspend after waking up. I can reproduce this as follows: I start up my laptop, suspend it the first time, wake it up again and I can work on it just fine (except for this bug causing me to have no internet connection). The second time I then suspend and wake up, my laptop will automatically go back to suspend within 30 seconds (whether I log in or not). This cycle then continues and I'm forced to reboot in order to fix it. Note that this happens whether I do or do not use temporary internet connection fix 'sudo nmcli nm sleep false'. Is this bug related, or should I (and julo) start a new bug report? -- 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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Still failed for me. I always used Right Ctrl to switch layouts. Now UI let's me set it to "Control R", but it does not switch layout at all. It does not let me set Alt+Shift displaying this shortcut as "Shift+Alt+Next Group". Does not let set two shifts. Ctrl+Alt does not switch layout if set. Super+Space does not switch layout and type space in the editor. Caps Lock does not switch layout if set. Only Ctrl+Space works. gnome-settings-daemon: Installed: 3.8.5-0ubuntu11.1 gnome-control-center: Installed: 1:3.6.3-0ubuntu45 -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in One Hundred Papercuts: Invalid Status in Indicator keyboard: Invalid Status in Ubuntu GNOME: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “indicator-keyboard” package in Ubuntu: Invalid Status in “gnome-control-center” source package in Saucy: Fix Committed Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Status in “indicator-keyboard” source package in Saucy: Invalid Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1218322/+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 1244413] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
That worked by the way thank you Raymond:D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1244413 Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all Status in “pulseaudio” package in Ubuntu: New Bug description: There is no sound coming from my speakers but there is perfect sound coming from the headphones I'm currently Dualbooting windows 7 and Ubuntu 12.04 and the windows works fine with sound Ubuntu has none ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15.4 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: theherobilly 2113 F pulseaudio /dev/snd/pcmC0D0p: theherobilly 2113 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 46' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402' Controls : 43 Simple ctrls : 19 Date: Thu Oct 24 16:33:59 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: 2113 2113/dev/snd/controlC0: theherobilly F pulseaudio /dev/snd/pcmC0D0p: theherobilly F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1244413/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
@Austin DeWolfe Try using: sudo apt-get update sudo apt-get upgrade should update the packages affected -- 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/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: New Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 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.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1242118] Re: no more subwoofer test sound very weak sound since 13.10
** Summary changed: - no more subwoofer test sound since 13.10 + no more subwoofer test sound very weak sound since 13.10 ** Description changed: There is no subwoofer TEST sound since 13.10. I feel subwoofer moving - somewhat so it may be only test sound problem. + slightly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-sounds in Ubuntu. https://bugs.launchpad.net/bugs/1242118 Title: no more subwoofer test sound very weak sound since 13.10 Status in “ubuntu-sounds” package in Ubuntu: New Bug description: There is no subwoofer TEST sound since 13.10. I feel subwoofer moving slightly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-sounds/+bug/1242118/+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 1244413] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
Here is the output of alsa info http://www.alsa-project.org/db/?f=630cad9b03bc995cb7cb7a516cc3f026bc6cf8ec -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1244413 Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all Status in “pulseaudio” package in Ubuntu: New Bug description: There is no sound coming from my speakers but there is perfect sound coming from the headphones I'm currently Dualbooting windows 7 and Ubuntu 12.04 and the windows works fine with sound Ubuntu has none ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15.4 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: theherobilly 2113 F pulseaudio /dev/snd/pcmC0D0p: theherobilly 2113 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 46' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402' Controls : 43 Simple ctrls : 19 Date: Thu Oct 24 16:33:59 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: 2113 2113/dev/snd/controlC0: theherobilly F pulseaudio /dev/snd/pcmC0D0p: theherobilly F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1244413/+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 1236346] Re: at-spi2-registryd.conf upstart script missing closing ']'
This bug was fixed in the package at-spi2-core - 2.10.1-0ubuntu1 --- at-spi2-core (2.10.1-0ubuntu1) trusty; urgency=low * New upstream bugfix release (LP: #1241308) - Fix a leak introduced in 2.9.92 that adversely affected performance (BGO#709625). * debian/patches/revert-message-flow-optimization.patch: Drop, properly fixed upstream. * Add missing closing bracket to upstart file (LP: #1236346) * debian/patches/fix_crash.patch: - Fix crash in register_client (LP: #1037357) -- Luke YelavichFri, 25 Oct 2013 08:58:55 +1100 ** Changed in: at-spi2-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1236346 Title: at-spi2-registryd.conf upstart script missing closing ']' Status in “at-spi2-core” package in Ubuntu: Fix Released Bug description: Impact At-spi2 does run, but the missing closing bracket in the upstart config file may be causing the gsettings check to fail. In additino, the following is shown in the user's local upstart logs for at-spi2-registryd: /proc/self/fd/9: 2: [: missing ] Regression potential: Little to none at all given that this was a typo. Hi, I'm seeing a bunch of missing ']' errors in ~/.cache/upstart/at- spi2-registryd.log. It seems this is because the 'pre-start' stanza is missing a closing ']' as shown below: pre-start script [ "$(gsettings get org.gnome.desktop.interface toolkit-accessibility)" \ = "true" || exit 0 end script It seems like an easy fix but I can't seem to find which LP branch to create a merge proposal against. Regards, Haw --- ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 13.10 MarkForUpload: True Package: at-spi2-core 2.10.0-0ubuntu2 [modified: usr/share/upstart/sessions/at-spi2-registryd.conf] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Tags: saucy Uname: Linux 3.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin audio cdrom dialout libvirtd lpadmin netdev plugdev sambashare users video modified.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: [modified] mtime.conffile..etc.xdg.autostart.at.spi.dbus.bus.desktop: 2013-07-24T01:24:45.829666 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1236346/+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 1037357] Re: at-spi2-registryd crashed with SIGSEGV in register_client()
This bug was fixed in the package at-spi2-core - 2.10.1-0ubuntu1 --- at-spi2-core (2.10.1-0ubuntu1) trusty; urgency=low * New upstream bugfix release (LP: #1241308) - Fix a leak introduced in 2.9.92 that adversely affected performance (BGO#709625). * debian/patches/revert-message-flow-optimization.patch: Drop, properly fixed upstream. * Add missing closing bracket to upstart file (LP: #1236346) * debian/patches/fix_crash.patch: - Fix crash in register_client (LP: #1037357) -- Luke YelavichFri, 25 Oct 2013 08:58:55 +1100 ** Changed in: at-spi2-core (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1037357 Title: at-spi2-registryd crashed with SIGSEGV in register_client() Status in Assistive Technology Service Provider Interface: Fix Released Status in “at-spi2-core” package in Ubuntu: Fix Released Bug description: . ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: at-spi2-core 2.5.5-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic i686 ApportVersion: 2.4-0ubuntu6 Architecture: i386 Date: Wed Aug 15 20:21:02 2012 ExecutablePath: /usr/lib/at-spi2-core/at-spi2-registryd InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120803.1) ProcCmdline: /usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0xb77305bf : mov0x8(%eax),%eax PC (0xb77305bf) ok source "0x8(%eax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: at-spi2-core Stacktrace: #0 0xb77305bf in main () No symbol table info available. StacktraceTop: main () Title: at-spi2-registryd crashed with SIGSEGV in main() 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/at-spi/+bug/1037357/+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 1241308] Re: Please consider the update to at-spi2-core 2.10.1.
This bug was fixed in the package at-spi2-core - 2.10.1-0ubuntu1 --- at-spi2-core (2.10.1-0ubuntu1) trusty; urgency=low * New upstream bugfix release (LP: #1241308) - Fix a leak introduced in 2.9.92 that adversely affected performance (BGO#709625). * debian/patches/revert-message-flow-optimization.patch: Drop, properly fixed upstream. * Add missing closing bracket to upstart file (LP: #1236346) * debian/patches/fix_crash.patch: - Fix crash in register_client (LP: #1037357) -- Luke YelavichFri, 25 Oct 2013 08:58:55 +1100 ** Changed in: at-spi2-core (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1241308 Title: Please consider the update to at-spi2-core 2.10.1. Status in “at-spi2-core” package in Ubuntu: Fix Released Bug description: affects ubuntu/at-spi2-core subscribe ubuntu-sru Please consider the update to at-spi2-core 2.10.1. THis should fall under the GNOME upstream exception criteria, changelog from upstream is as follows: * Fix a leak introduced in 2.9.92 that adversely affected performance (BGO#709625). Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1241308/+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 1040873] Re: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all: Subwoofer not working
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?id=ee81abb623cb5e03c182d16871bb4fb34fdc9b4f
do you need a new mapping
map = { SNDRV_CHMAP_FL, SNDRV_CHMAP_FR,
+ SNDRV_CHMAP_NA, SNDRV_CHMAP_LFE
or use the default 2.1
+/* default channel maps for 2.1 speakers;
+ * since HD-audio supports only stereo, odd number channels are omitted
+ */
+const struct snd_pcm_chmap_elem snd_pcm_2_1_chmaps[] = {
+ { .channels = 2,
+ .map = { SNDRV_CHMAP_FL, SNDRV_CHMAP_FR } },
+ { .channels = 4,
+ .map = { SNDRV_CHMAP_FL, SNDRV_CHMAP_FR,
+ SNDRV_CHMAP_LFE, SNDRV_CHMAP_LFE } },
+ { }
+};
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1040873
Title:
[N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all:
Subwoofer not working
Status in “alsa-driver” package in Ubuntu:
Confirmed
Bug description:
Hi,
this bug is a fork of https://bugs.launchpad.net/ubuntu/+source/alsa-
driver/+bug/871808 because #871808 stands for a different hardware
with a different solution, so people may get confused.
Here is a summary (see post #48 to #54 of #871808):
The subwoofer of Asus N56VZ laptop doesn't work "out of the box".
#sudo hda-jack-sense-test -a :
*** Without subwoofer:
Pin 0x1e (Black SPDIF Out): present = No
*** With subwoofer:
Pin 0x1e (Black SPDIF Out): present = Yes
http://www.alsa-
project.org/db/?f=2778e7f430aa95ae219d0b2bc3cb5e46abd0a33a
--> There are two ways of making it work:
#1
a. Add to rc.local :
echo 0x1e 0x99130112 > /sys/class/sound/hwC0D0/user_pin_configs
echo 1 > /sys/class/sound/hwC0D0/reconfig
b. Add options snd-hda-intel model=asus-mode4 in
/etc/modprobe.d/alsa-base.conf
c. Reboot
d. Set the mode to "Analog Stereo Output" and then to "Analog Surround 5.1
output" in the sound settings panel. You have to do this each time you reboot!!!
#2
a. Add to rc.local :
echo 0x16 0x99130111 > /sys/class/sound/hwC0D0/user_pin_configs
echo 0x1e 0x99130112 > /sys/class/sound/hwC0D0/user_pin_configs
echo 1 > /sys/class/sound/hwC0D0/reconfig
b. Reboot
c. Set the mode to "Analog Stereo Output" and then to "Analog Surround 5.1
output" in the sound settings panel. You have to do this each time you reboot!!!
Both give the same results and fix the bug.
--> Can you make it work out of the box?
There is still two other bugs on this laptop :
- crackling audio when playing with sound volume: see
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1040867
- When I put the omputer in sleep mode, there is no way to get sound working
on resume: should I open a new bug to investigate this?
Regards
Sam
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: alsa-base 1.0.25+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
List of PLAYBACK Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC663 Analog [ALC663 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: sam1898 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7a1 irq 47'
Mixer name : 'Realtek ALC663'
Components : 'HDA:10ec0663,10431477,0012'
Controls : 23
Simple ctrls : 13
CheckboxSubmission: 54021779511d0213081a2b1707bf951c
CheckboxSystem: 4c773cd91921f9618cc2f1893bc1a87a
Date: Thu Aug 23 22:38:00 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
PackageArchitecture: all
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
1898 sam F pulseaudio
PID ACCESS COMMAND
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [N56VZ, Realtek ALC663, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
[Desktop-packages] [Bug 1184451] Re: Ubuntu 13.10 random screen freeze while Normal OS activites
I don't use Firefox as my standard browser, so I didn't notice it myself. When other people use my computer, they have to use firefox, as I don't want them to use 'my' browser (chromium). It only seems to happen when Firefox is in use and I've seen it happening. It's quite annoying. Screen freezes for ~30 sec or even longer. Only sysreq-keystrokes still work. Cannot find anything in logs (or maybe I haven't checked the right logs). I am not entirely sure, but in all cases an instance of Libre Office had been used as well, which is also something I never do (use gedit or google docs...). But I haven't been able to recreate the problem. It seems completely random... -- 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/1184451 Title: Ubuntu 13.10 random screen freeze while Normal OS activites Status in “xorg-server” package in Ubuntu: Confirmed Bug description: I have recently, re-installed fresh ubuntu 13.10 distribution release. But everything worked fine. until recently i had strange problem of my display screen getting freezed randomly; but no response to either mouse/keyboard. But i want to point it out; it happens randomly and is not specific ? Other day, i had music player playing in background, but screen freezed. but my music was still running. Kindly note, i used multiple monitor setup and same issue of screen freeze also cropped up. I,am not sure, whether it is bug ? thanks for the expertise support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1184451/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
** Changed in: hundredpapercuts Importance: Undecided => Medium -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in One Hundred Papercuts: Invalid Status in Indicator keyboard: Invalid Status in Ubuntu GNOME: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “indicator-keyboard” package in Ubuntu: Invalid Status in “gnome-control-center” source package in Saucy: Fix Committed Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Status in “indicator-keyboard” source package in Saucy: Invalid Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1218322/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
I'm unable to reproduce this bug using two different computers. Are you experiencing this bug after updating your system? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) Expected: The content of the submenus show up Actual: Only the top-level headers seem to be available. Nothing happens when I click on them either. They don't show up in the HUD either. It worked fine on 13.04, so I'm not sure what changed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+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 868886] Re: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache'
*** This bug is a duplicate of bug 864368 *** https://bugs.launchpad.net/bugs/864368 Neal, I've opened the other bug; sadly, not much detail there, either, probably because it was kept private for so long. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pitivi in Ubuntu. https://bugs.launchpad.net/bugs/868886 Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' Status in “pitivi” package in Ubuntu: Confirmed Bug description: se cuelga cuando trato de importar un video, para editarlo. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: pitivi 0.15.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Thu Oct 6 01:40:25 2011 ExecutablePath: /usr/bin/pitivi InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110922) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: python /usr/bin/pitivi PythonArgs: ['/usr/bin/pitivi'] SourcePackage: pitivi Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' 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/pitivi/+bug/868886/+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 864368] Re: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache'
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pitivi in Ubuntu. https://bugs.launchpad.net/bugs/864368 Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' Status in “pitivi” package in Ubuntu: Confirmed Bug description: I just loaded an .mkv movie and then pitivi crashed. Couldn't reproduce the error. But maybe the error could help you find a small or big bug. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: pitivi 0.15.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportVersion: 1.23-0ubuntu2 Architecture: amd64 Date: Sun Oct 2 00:42:43 2011 ExecutablePath: /usr/bin/pitivi InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64+mac (20110921.2) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: python /usr/bin/pitivi ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash PythonArgs: ['/usr/bin/pitivi'] SourcePackage: pitivi Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' 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/pitivi/+bug/864368/+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 1093582] Re: gnome-system-monitor display without grid
@Sebastian: I have checked from the system monitor git repo log what would be worth porting, and there's not much worth porting, basically the fix for this bug and another one for a wording change in bug #1156238. The other ones, some performance improvements and memory leak fixes are also interesting, but as these happened after serious refactorings, they can not be easily ported. With the ones I have mentioned I have created a branch with new patches for it in /debian/patches, unfortunately bzr builddeb fails with some strange error, looks like it wants to revert the fix for the graph grid rendering issue based on the upstream 3.8.2.1. I would appreciate if you could take a look into that branch, based on ubuntu:gnome-system-monitor, see it at lp:~evfool/gnome-system-monitor/stableupdates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1093582 Title: gnome-system-monitor display without grid Status in The GNOME System Monitor: Fix Released Status in “gnome-system-monitor” package in Ubuntu: Fix Committed Bug description: gnome-system-monitor display without grid lines after refreshing or starting the application (cf. attached screenshot) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-system-monitor 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Dec 25 09:26:55 2012 InstallationDate: Installed on 2012-05-16 (222 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to quantal on 2012-10-20 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1093582/+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 1238433] Re: ibus-ui-gtk3 crashed with SIGABRT
*** This bug is a duplicate of bug 1224496 *** https://bugs.launchpad.net/bugs/1224496 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1238433 Title: ibus-ui-gtk3 crashed with SIGABRT Status in “ibus” package in Ubuntu: Confirmed Bug description: Ibus crashed after login. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Oct 11 08:03:56 2013 Disassembly: => 0x7fd17a089f77: Cannot access memory at address 0x7fd17a089f77 ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3 InstallationDate: Installed on 2013-08-30 (41 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130829) MarkForUpload: True ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3 Signal: 6 SourcePackage: ibus StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: ibus-ui-gtk3 crashed with SIGABRT 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/ibus/+bug/1238433/+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 1244413] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
Default sample spec: s16le 2ch 44100Hz Default channel map: front-left,front-right Default sink name: alsa_output.pci-_00_1b.0.analog-surround-40 Default source name: alsa_input.pci-_00_1b.0.analog-stereo pin-ctls of speaker node should be OUT instead of zero when both headphone are unplugged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1244413 Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all Status in “pulseaudio” package in Ubuntu: New Bug description: There is no sound coming from my speakers but there is perfect sound coming from the headphones I'm currently Dualbooting windows 7 and Ubuntu 12.04 and the windows works fine with sound Ubuntu has none ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15.4 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: theherobilly 2113 F pulseaudio /dev/snd/pcmC0D0p: theherobilly 2113 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 46' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402' Controls : 43 Simple ctrls : 19 Date: Thu Oct 24 16:33:59 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: 2113 2113/dev/snd/controlC0: theherobilly F pulseaudio /dev/snd/pcmC0D0p: theherobilly F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1244413/+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 1244413] Re: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all
does the notebook support 5.1 by retasking Mic Jack as output ? if headphone and speaker are connected to same audio output, the volume control at node 0x02 should not be named as headphone playback volume/switch try latest alsa driver https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS post the output of alsa-info.sh https://wiki.ubuntu.com/Audio/AlsaInfo headphone node 0x0a should be connected to node 0x03 so that speaker playback volume at node 0x02 and headphone volume at node 0x03 node 0x02 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Control: name="Headphone Playback Volume", index=1, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=63 Control: name="Headphone Playback Switch", index=1, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: N/A Amp-Out vals: [0x7f 0x7f] Converter: stream=8, channel=2 Power states: Power: setting=D0, actual=D0 Delay: 13 samples Node 0x03 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Converter: stream=0, channel=0 Power states: Power: setting=D3, actual=D3 Delay: 13 samples Node 0x04 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Amp-Out caps: N/A Amp-Out vals: [0xff 0xff] Converter: stream=0, channel=0 Power states: Power: setting=D3, actual=D3 Delay: 13 samples Node 0x05 [Audio Output] wcaps 0xd0c05: Stereo Amp-Out R/L Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=63 Control: name="Headphone Playback Switch", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="STAC92xx Analog", type="Audio", device=0 Amp-Out caps: N/A Amp-Out vals: [0x7f 0x7f] Converter: stream=8, channel=0 Power states: Power: setting=D0, actual=D0 Delay: 13 samples Node 0x0a [Pin Complex] wcaps 0x400181: Stereo Pincap 0x173f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 Pin Default 0x0221101f: [Jack] HP Out at Ext Front Conn = 1/8, Color = Black DefAssociation = 0x1, Sequence = 0xf Pin-ctls: 0xc0: OUT HP VREF_HIZ Unsolicited: tag=01, enabled=1 Connection: 2 0x02* 0x03 Node 0x0d [Pin Complex] wcaps 0x400181: Stereo Control: name="Speaker Phantom Jack", index=0, device=0 Pincap 0x173f: IN OUT HP Detect Trigger ImpSense Vref caps: HIZ 50 GRD 80 Pin Default 0x90170110: [Fixed] Speaker at Int N/A Conn = Analog, Color = Unknown DefAssociation = 0x1, Sequence = 0x0 Misc = NO_PRESENCE Pin-ctls: 0x00: VREF_HIZ Unsolicited: tag=00, enabled=0 Connection: 1 0x02 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1244413 Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all Status in “pulseaudio” package in Ubuntu: New Bug description: There is no sound coming from my speakers but there is perfect sound coming from the headphones I'm currently Dualbooting windows 7 and Ubuntu 12.04 and the windows works fine with sound Ubuntu has none ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15.4 ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10 Uname: Linux 3.8.0-32-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-32-generic. ApportVersion: 2.0.1-0ubuntu17.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: theherobilly 2113 F pulseaudio /dev/snd/pcmC0D0p: theherobilly 2113 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 46' Mixer name : 'SigmaTel STAC9228' Components : 'HDA:14f12c06,14f1000f,0010 HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402' Controls : 43 Simple ctrls : 19 Date: Thu Oct 24 16:33:59 2013 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: 2113 2113/dev/snd/controlC0: theherobilly F pulseaudio /dev/snd/pcmC0D0p: theherobilly F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Inspiron 1525, SigmaTel STAC9228, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDell
[Desktop-packages] [Bug 870874] Re: LDAP user with automounted nfs homedir cannot login
Confirming this is a bug as well.
Ubuntu 12.04 with LDAP auth and NFS home directory mounts.
Only seems to affect GNOME Classic and GNOME Classic (No Effects)
logins. Hangs after entering credentials.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to at-spi2-core in Ubuntu.
https://bugs.launchpad.net/bugs/870874
Title:
LDAP user with automounted nfs homedir cannot login
Status in “at-spi2-core” package in Ubuntu:
Confirmed
Bug description:
After installing Ubuntu (Oneiric, development branch) I followed two
guides to setup LDAP authentication and automounting of home
directories using autofs-ldap. This setup was working properly for
older Ubuntu releases (just to be sure I also tried with a fresh, up
to date 11.04 installation).
The following steps were executed to setup LDAP authentication:
https://help.ubuntu.com/11.04/serverguide/C/openldap-server.html (section:
LDAP Authentication)
These steps were executed to setup Autofs-ldap:
https://help.ubuntu.com/community/AutofsLDAP
LDAP users properly login from the terminal (Ctrl-Alt-F1), in that
case they can browse their automounted homedirs etc.
When I try to login using LightDM the user seems to be logged in
properly; the login widget disappears from the screen but other than
that nothing is happening (the login screen background is still
visible, but the login widget is gone). I still can move the mouse
pointer but the user is not logged on. When taking a look at the
user's .xsession-errors file there is not much to see, nothing that
seems worrying to me. I can't find anything that obviously looks like
an error in /var/log/*.
I tried several things:
- removed all files/directories starting with a . (dot) in the user's home
directory
- using LightDM and the default Ubuntu window manager
- using LightDM with Gnome
- using GDM with Gnome
In all cases the same behavior was observed.
Logging in with a local user works like a charm.
This is what /var/log/lightdm/lightdm.log says:
[+2.83s] DEBUG: Read 8 bytes from greeter
[+2.83s] DEBUG: Read 15 bytes from greeter
[+2.83s] DEBUG: Greeter start authentication for test_user
[+2.83s] DEBUG: pam_authenticate(0x169e340, 0) -> 10 (User not known to the
underlying authentication module)
[+2.83s] DEBUG: pam_start("lightdm", "test_user") -> (0x7f1ae4011570, 0)
[+2.85s] DEBUG: Prompt greeter with 1 message(s)
[+2.85s] DEBUG: Wrote 45 bytes to greeter
[+16.20s] DEBUG: Read 8 bytes from greeter
[+16.20s] DEBUG: Read 16 bytes from greeter
[+16.20s] DEBUG: Continue authentication
[+16.22s] DEBUG: pam_authenticate(0x7f1ae4011570, 0) -> 0 (Success)
[+16.22s] DEBUG: pam_acct_mgmt(0x7f1ae4011570, 0) -> 0 (Success)
[+16.22s] DEBUG: Authenticate result for user test_user: Success
[+16.22s] DEBUG: User test_user authorized
[+16.22s] DEBUG: Wrote 27 bytes to greeter
[+16.24s] DEBUG: Read 8 bytes from greeter
[+16.24s] DEBUG: Read 15 bytes from greeter
[+16.24s] DEBUG: Greeter requests session gnome-shell
[+16.25s] DEBUG: Stopping greeter
[+16.25s] DEBUG: Dropping privileges to uid 104
[+16.25s] DEBUG: Removing session authority from /var/lib/lightdm/.Xauthority
[+16.28s] DEBUG: Restoring privileges
[+16.28s] DEBUG: Sending signal 15 to process 7950
[+16.28s] DEBUG: Process 7950 exited with return value 0
[+16.28s] DEBUG: pam_close_session(0x167f300) -> 0 (Success)
[+16.28s] DEBUG: pam_setcred(0x167f300, PAM_DELETE_CRED) -> 0 (Success)
[+16.28s] DEBUG: pam_end(0x167f300) -> 0
[+16.28s] DEBUG: Ending ConsoleKit session
6e3a694924188906d4093c6702696be1-1318095483.743254-1770205889
[+16.31s] DEBUG: Greeter quit
[+16.31s] DEBUG: Starting user session
[+16.38s] DEBUG: Dropping privileges to uid 1049
[+16.38s] DEBUG: Writing /srv/home/test_user/.dmrc
[+17.48s] DEBUG: Restoring privileges
[+17.51s] DEBUG: Starting session gnome-shell as user test_user logging to
/srv/home/test_user/.xsession-errors
[+17.51s] DEBUG: Launching session
[+17.51s] DEBUG: pam_set_item(0x7f1ae4011570, 3, ":0") -> 0 (Success)
[+17.55s] DEBUG: pam_open_session(0x7f1ae4011570, 0) -> 0 (Success)
[+17.58s] DEBUG: Opened ConsoleKit session
6e3a694924188906d4093c6702696be1-1318095500.694488-13642418
[+17.58s] DEBUG: Dropping privileges to uid 1049
[+17.58s] DEBUG: Adding session authority to /srv/home/test_user/.Xauthority
[+17.82s] DEBUG: Restoring privileges
[+17.82s] DEBUG: Launching process 8053: /usr/sbin/lightdm-session
'gnome-session --session=gnome'
[+17.82s] DEBUG: Registering session with bus path
/org/freedesktop/DisplayManager/Session0
[+17.92s] DEBUG: pam_setcred(0x7f1ae4011570, PAM_ESTABLISH_CRED) -> 0
(Success)
[+17.92s] DEBUG: PAM returns environment
'GNOME_KEYRING_CONTROL=/tmp/keyring-6wgIZV GNOME_KEYRING_PID=8044
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8'
The user's .xsessio
[Desktop-packages] [Bug 1223436] Re: telepathy-gabble 0.18 does not work with jabberd2
Attached is the log for 0.16. What I find interesting is that 0.18 is logging twice. Eg: gabbleauthentication-DEBUG: 10/21/2013 16:13:21.904870: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:836): Starting authentication gabbleauthentication-DEBUG: 10/21/2013 16:13:21.904870: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:836): Starting authentication gabbleauthentication-DEBUG: 10/21/2013 16:13:22.139523: gabble_server_sasl_channel_start_mechanism_with_data (server-sasl-channel.c:548): Starting X-TELEPATHY-PASSWORD authentication with 16 bytes of initial data gabbleauthentication-DEBUG: 10/21/2013 16:13:22.139523: gabble_server_sasl_channel_start_mechanism_with_data (server-sasl-channel.c:548): Starting X-TELEPATHY-PASSWORD authentication with 16 bytes of initial data but 0.16 is only logging once: gabbleauthentication-DEBUG: 10/24/2013 21:24:57.750232: gabble_server_sasl_channel_start_auth_async (server-sasl-channel.c:814): Starting authentication gabbleauthentication-DEBUG: 10/24/2013 21:24:58.174243: gabble_server_sasl_channel_start_mechanism_with_data (server-sasl-channel.c:520): Starting X-TELEPATHY-PASSWORD authentication with 16 bytes of initial data Don't know if this is related or not. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1223436 Title: telepathy-gabble 0.18 does not work with jabberd2 Status in “telepathy-gabble” package in Ubuntu: New Status in “telepathy-gabble” source package in Saucy: New Bug description: If I upgrade to telepathy-gabble 0.18.0-1 or 0.18.1-1, I can no longer connect to a jabberd2 server. The jabberd2 c2s.log simply has: Tue Sep 10 11:13:14 2013 [notice] [12] [xxx, port=43155] connect Tue Sep 10 11:13:14 2013 [notice] [12] [xxx, port=43155] disconnect jid=unbound, packets: 0 If I downgrade to 0.16.6-1ubuntu1, it starts working again: Tue Sep 10 11:14:01 2013 [notice] [13] [xxx, port=37786] connect Tue Sep 10 11:14:01 2013 [notice] [13] [xxx, port=37786] disconnect jid=unbound, packets: 0 Tue Sep 10 11:14:01 2013 [notice] [12] SASL authentication succeeded: mechanism=DIGEST-MD5; authzid=xxx, TLS negotiated Tue Sep 10 11:14:01 2013 [notice] [12] bound: jid=xxx/xxx I can see this by trying to connect with empathy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1223436/+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 1223436] Re: telepathy-gabble 0.18 does not work with jabberd2
** Attachment added: "gabble (jabber)-24-10-13_16-25-10.log" https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1223436/+attachment/3890335/+files/gabble%20%28jabber%29-24-10-13_16-25-10.log ** Changed in: telepathy-gabble (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-gabble in Ubuntu. https://bugs.launchpad.net/bugs/1223436 Title: telepathy-gabble 0.18 does not work with jabberd2 Status in “telepathy-gabble” package in Ubuntu: New Status in “telepathy-gabble” source package in Saucy: New Bug description: If I upgrade to telepathy-gabble 0.18.0-1 or 0.18.1-1, I can no longer connect to a jabberd2 server. The jabberd2 c2s.log simply has: Tue Sep 10 11:13:14 2013 [notice] [12] [xxx, port=43155] connect Tue Sep 10 11:13:14 2013 [notice] [12] [xxx, port=43155] disconnect jid=unbound, packets: 0 If I downgrade to 0.16.6-1ubuntu1, it starts working again: Tue Sep 10 11:14:01 2013 [notice] [13] [xxx, port=37786] connect Tue Sep 10 11:14:01 2013 [notice] [13] [xxx, port=37786] disconnect jid=unbound, packets: 0 Tue Sep 10 11:14:01 2013 [notice] [12] SASL authentication succeeded: mechanism=DIGEST-MD5; authzid=xxx, TLS negotiated Tue Sep 10 11:14:01 2013 [notice] [12] bound: jid=xxx/xxx I can see this by trying to connect with empathy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-gabble/+bug/1223436/+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 1180665] Re: gedit SIGSEGV in gedit_multi_notebook_get_active_tab()
** Changed in: hundredpapercuts Importance: High => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1180665 Title: gedit SIGSEGV in gedit_multi_notebook_get_active_tab() Status in Light-Weight Text Editor for Gnome: New Status in One Hundred Papercuts: Triaged Status in “gedit” package in Ubuntu: Triaged Bug description: crashed with about 5 tabs open ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: gedit 3.8.0-0ubuntu1~raring1 [origin: LP-PPA-gnome3-team-gnome3] ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.10.1-0ubuntu1 Architecture: amd64 Date: Thu May 16 12:26:21 2013 ExecutablePath: /usr/bin/gedit ExecutableTimestamp: 1367295250 InstallationDate: Installed on 2012-09-23 (235 days ago) InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Alpha amd64(20120922) MarkForUpload: True ProcCmdline: gedit ProcCwd: /home/darkness ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x460076 : cmp%rax,(%rdx) PC (0x00460076) ok source "%rax" ok destination "(%rdx)" (0x) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: gedit StacktraceTop: gedit_multi_notebook_get_active_tab () ?? () selection_received (widget=0x1e09dd0, selection_data=0x7fffd9d55a70, time=) at /build/buildd/gtk+3.0-3.8.2/./gtk/gtkclipboard.c:939 g_closure_invoke (closure=0x1fbe0e0, return_value=0x0, n_param_values=3, param_values=0x7fffd9d55720, invocation_hint=0x7fffd9d556c0) at /build/buildd/glib2.0-2.37.0/./gobject/gclosure.c:777 signal_emit_unlocked_R (node=node@entry=0x19c8db0, detail=detail@entry=0, instance=instance@entry=0x1e09dd0, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffd9d55720) at /build/buildd/glib2.0-2.37.0/./gobject/gsignal.c:3584 Title: gedit crashed with SIGSEGV in gedit_multi_notebook_get_active_tab() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1180665/+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 1205087] Re: Gnome-system-monitor needs translation item 19 "Sent" to read "Sending" instead.
*** This bug is a duplicate of bug 1156328 *** https://bugs.launchpad.net/bugs/1156328 ** This bug has been marked a duplicate of bug 1156328 'Sent' instead of 'Transmitting'/'Sending' field -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1205087 Title: Gnome-system-monitor needs translation item 19 "Sent" to read "Sending" instead. Status in “gnome-system-monitor” package in Ubuntu: Triaged Bug description: In the program "System Monitor", under "Network history" (see screen dump), it says "Receiving/Total Received" and "Sent/Total Sent" This really gets on my nerves :-) For consistency it should be "Receiving/Total Received" and "Sending/Total Sent" (i.e. replace the first Sent with Sending) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1205087/+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 1231778] Re: wifi not working on Saucy Salamander
This is most likely due to the apparmor_parser errors. They are caused by having a new apparmor_parser, new policy (which now includes dbus rules), and old kernel. The parser should be checking to see if the kernel supports dbus rules. Looking at the mount rule support in the parser, * in parser/parser_main.c:get_match_string(): - if apparmorfs/features/mount exists, the kernel_supports_mount global is set to 1 * in parser/parser_regex.c:post_process_mnt_ents(): - mount rule entries are only processed if kernel_supports_mount is not 0 - if kernel_supports_mount is 0, then a warning is emitted and the mount rule is ignored The dbus rule support in the parser needs similar logic. ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: apparmor (Ubuntu) Status: New => Triaged ** Changed in: apparmor (Ubuntu) Importance: Undecided => Medium ** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Tyler Hicks (tyhicks) -- 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/1231778 Title: wifi not working on Saucy Salamander Status in Enablement project for the Toshiba AC100 NetBook: New Status in “apparmor” package in Ubuntu: Triaged Status in “network-manager” package in Ubuntu: Confirmed Bug description: Lubuntu 13.10 installed from daily image have wifi not working, even with BT disabled. confirmed by stuw on IRC at Sun Sep 22 15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1231778/+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 1227338] Re: gnome -system-monitor - 'Resources' background information graph not being rendered sometimes
*** This bug is a duplicate of bug 1093582 *** https://bugs.launchpad.net/bugs/1093582 ** This bug has been marked a duplicate of bug 1093582 gnome-system-monitor display without grid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1227338 Title: gnome -system-monitor - 'Resources' background information graph not being rendered sometimes Status in The GNOME System Monitor: Fix Released Status in “gnome-system-monitor” package in Ubuntu: Triaged Bug description: Under the 'Resources' tab. The individual information background graphs are not being rendered sometimes. See supplied screenshot. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-system-monitor 3.8.2.1-2 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.2-0ubuntu1 Architecture: amd64 Date: Wed Sep 18 20:38:37 2013 InstallationDate: Installed on 2013-09-12 (6 days ago) InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to saucy on 2013-09-12 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1227338/+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 1240740] Re: The search for "monitor" in system configuration returns a wrong text
** Package changed: gnome-system-monitor (Ubuntu) => gnome-control- center (Ubuntu) -- 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/1240740 Title: The search for "monitor" in system configuration returns a wrong text Status in “gnome-control-center” package in Ubuntu: New Bug description: Im using 12.04. when I search the word "monitor" in the search box is filtered correctly but displays the text option of ubuntu one. It's just a cosmetic bug. The image explains better than i can. Sorry for my bad english. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1240740/+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 1239122] Re: System-monitor: graph backgrounds disappear sometimes (gnome3 dark theme via gnome-tweak-tool)
*** This bug is a duplicate of bug 1093582 *** https://bugs.launchpad.net/bugs/1093582 ** This bug has been marked a duplicate of bug 1093582 gnome-system-monitor display without grid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1239122 Title: System-monitor: graph backgrounds disappear sometimes (gnome3 dark theme via gnome-tweak-tool) Status in “gnome-system-monitor” package in Ubuntu: New Bug description: I have Gnome3 dark theme activated in gnome-tweak-tool. If I change to another window and back to gnome-system-monitor or if i change from the Resources tab to another and back, the graph backgrounds (white with dotted lines) just disappear. It also happened that only 2 of the 3 backgrounds disappeared. I'm using GNOME Shell 3.8.3. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-system-monitor 3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-30.44-generic 3.8.13.6 Uname: Linux 3.8.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Sat Oct 12 14:13:37 2013 ExecutablePath: /usr/bin/gnome-system-monitor InstallationDate: Installed on 2013-09-05 (36 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MarkForUpload: True SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to raring on 2013-09-05 (36 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1239122/+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 924278] Re: xscreensaver doesn't enable DPMS
I think the root of the problem is that if xscreensaver is built with DPMS support, there doesn't seem to be any setting to make it just leave DPMS alone. Also, we probably need the DPMS support because it allows xscreensaver to conserve resources when DPMS turns off the monitor. So as it stands now, if you are using xscreensaver you must use the DPMS settings provided within xscreensaver. Any attempt to use other tools (xset) will fail because xscreensaver will override the other tool. Within xscreensaver preferences under the Advanced tab you can change DPMS settings. Works for me on Saucy, xscreensaver Version: 5.15-3ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xscreensaver in Ubuntu. https://bugs.launchpad.net/bugs/924278 Title: xscreensaver doesn't enable DPMS Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 12.04 dev with xscreensaver 5.15-2ubuntu1. The configuration menu xscreensaver-demo provides under the register Advanced the option "Power Management Enable". But this option doesn't enable DPMS (xset -q says "DPMS is Disabled") so the screen can never go in the standby mode. The only way to get it work is to call xset +dpms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/924278/+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 1244437] [NEW] unable to click, select, mark or copy url in app description
Public bug reported: as the description says: the text in the app description should be selectable and copyable and links therein (like the homepage of a project) should be clickable. ** Affects: software-center (Ubuntu) Importance: Undecided Status: New ** Description changed: as the description says: - the text in the app description should be selectable and copyable and links therein should be clickable. + the text in the app description should be selectable and copyable and links therein (like the homepage of a project) should be clickable. -- 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/1244437 Title: unable to click, select, mark or copy url in app description Status in “software-center” package in Ubuntu: New Bug description: as the description says: the text in the app description should be selectable and copyable and links therein (like the homepage of a project) should be clickable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1244437/+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
@Catalin you're right, it happened again. That is one in five resumes that the network fails to resume though, rather than every time like it did before, but still annoying. -- 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 1244157] Re: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access
So yes this is because of the unshare of the file system namespace. Currently the only work around is the use of the attach_disconnected flag. Alternate solutions are coming as part of the work to support lxc Martin: The only way to temporarily add the attach_disconnected flag is to manually replace the profile with a version that has the flag added. The manually loaded profile can be from anywhere apparmor_parser -Kr -- 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/1244157 Title: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Bug description: On October 9 the NetworkManager tests started failing (https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy- adt-network-manager/?). Unfortunately the more recent saucy logs got lost, but the trusty ones have the information, like in https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job /trusty-adt-network-manager/1/ARCH=i386,label=adt/ In these, dhclient that gets called through NetworkManager and /usr/lib/NetworkManager/nm-dhcp-client.action cannot access the system D-BUS any more: --- NM log NetworkManager[24451]: Activation (eth42) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Error: could not get the system bus. Make sure the message bus daemon is running! Message: (org.freedesktop.D Bus.Error.AccessDenied) Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied --- NM log In syslog, you see this at that time: syslog - Oct 21 14:11:24 autopkgtest kernel: [ 288.320754] type=1400 audit(1382364684.505:21): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=18759 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=18760 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Oct 21 14:11:24 autopkgtest kernel: [ 288.333814] type=1400 audit(1382364684.517:22): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=18752 profile="/sbin/dhclient" name="dev/log" pid=18759 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 syslog - This gets fixed if I do "sudo /etc/init.d/apparmor teardown". But it does not seem to be a problem with the policy itself; if I do "sudo aa-complain dhclient" then dmesg changes to [ 8054.314704] type=1400 audit(1382609088.727:672): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=24451 profile="/sbin/dhclient" name="dev/log" pid=24736 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [ 8054.341409] type=1400 audit(1382609088.755:673): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=24736 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=24737 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 So this doesn't look like a problem with the policy but rather with some internal AppArmor name parsing? I found an old bug 955892 with the same error message, but that got fixed a while ago, and this does not involve ecryptfs or anythign similar. It's just a plain trusty VM with the NetworkManager autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1244157/+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 1208019] Re: Eclipse menus doesn't show up in Saucy
I think Eclipse used to be black-listed in raring in /usr/lib/x86_64-linux-gnu/gtk-2.0/2.10.0/menuproxies/libappmenu.so but now in Saucy it's in /usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libunity-gtk-module.so Maybe it's not getting picked up because it's in a different .so? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eclipse in Ubuntu. https://bugs.launchpad.net/bugs/1208019 Title: Eclipse menus doesn't show up in Saucy Status in “eclipse” package in Ubuntu: Incomplete Status in “unity-gtk-module” package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Run Eclipse. 2. Move the cursor to the top of the screen. 3. Click on any of the menu items (File, Edit, Navigate, ...) Expected: The content of the submenus show up Actual: Only the top-level headers seem to be available. Nothing happens when I click on them either. They don't show up in the HUD either. It worked fine on 13.04, so I'm not sure what changed. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eclipse 3.8.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-6.17-generic 3.10.3 Uname: Linux 3.10.0-6-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 Date: Sat Aug 3 17:03:55 2013 InstallationDate: Installed on 2013-07-08 (25 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130708) MarkForUpload: True PackageArchitecture: all SourcePackage: eclipse UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/1208019/+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 1093582] Re: gnome-system-monitor display without grid
@Sebastian: Yes, System Monitor has been updated along with the other applications to fit in the GNOME ecosystem with headerbars, which is a 3.10 feature, and requires gtk 3.10. I have been looking at what could be easily backported, but system monitor has undergone some refactorings this cycle too, so changes are not too easily backported. I will take some more time and to pick the best bugfixes and the ones which also appear in launchpad and can be ported easily, and come up with a system monitor ubuntu package update featuring those ones. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1093582 Title: gnome-system-monitor display without grid Status in The GNOME System Monitor: Fix Released Status in “gnome-system-monitor” package in Ubuntu: Fix Committed Bug description: gnome-system-monitor display without grid lines after refreshing or starting the application (cf. attached screenshot) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-system-monitor 3.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.6.1-0ubuntu9 Architecture: amd64 Date: Tue Dec 25 09:26:55 2012 InstallationDate: Installed on 2012-05-16 (222 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to quantal on 2012-10-20 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-system-monitor/+bug/1093582/+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 1104476] Re: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate
@Chhatoi Pritam Baral Thanks for building a fix for this issue, I know I appreciate it. I do have a question though. I can't seem to get the package through apt-get. I put the ppa into my repositories, but when I do sudo apt-get install network-manager-applet it can't find it (am I using the wrong package name?) I feel so close to finally being able to getting wifi working that it really sucks not to be able to get the package. -- 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/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate Status in NetworkManager: New Status in Release Notes for Ubuntu: Fix Released Status in “network-manager” package in Ubuntu: Triaged Bug description: === Release Notes Text === When connecting to MPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate network manager may incorrectly mark the CA certificate as needing verification and fail that verification. See the bug for workarounds. === I can connect to Eduroam in 12.10 and any other previous release, but not in 13.04. I checked, my name and password are correct, all settings are the same as in 12.10. Network properties: security: WPA - WPA2 enterprise authentication: protected EAP (PEAP) CA certificate: none PEAP version: automatic inner autentication: MSCHAPv2 username: (required) password: (required) ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.6.0+git201301021750.e78c3e8-0ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic i686 ApportVersion: 2.8-0ubuntu2 Architecture: i386 CasperVersion: 1.330 Date: Thu Jan 24 21:32:25 2013 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.43.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.43.0/24 dev wlan0 proto kernel scope link src 192.168.43.149 metric 9 LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha i386 (20130123) MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH AndroidAP 978da457-563b-4c59-a894-45eb0f74fcb7 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/2 Wired connection 16703fabc-9519-49bd-a4af-45fbfb7d660e 802-3-ethernet1359062570 Thu 24 Jan 2013 09:22:50 PM UTCyes no /org/freedesktop/NetworkManager/Settings/1 eduroam 00f69a95-4a1b-436c-b462-a284f45fbaa1 802-11-wireless 1359063171 Thu 24 Jan 2013 09:32:51 PM UTCyes no /org/freedesktop/NetworkManager/Settings/0 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.7.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+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 1244425] [NEW] Log Out menu option maxes out CPU
Public bug reported: When selecting the "Log Out..." menu option in Xubuntu 13.10, xorg goes to max cpu and ties up the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.11.5-031105-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 24 14:03:36 2013 InstallationDate: Installed on 2013-09-02 (52 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- 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/1244425 Title: Log Out menu option maxes out CPU Status in “xorg” package in Ubuntu: New Bug description: When selecting the "Log Out..." menu option in Xubuntu 13.10, xorg goes to max cpu and ties up the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 Uname: Linux 3.11.5-031105-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Thu Oct 24 14:03:36 2013 InstallationDate: Installed on 2013-09-02 (52 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1) MarkForUpload: True SourcePackage: xorg UpgradeStatus: Upgraded to saucy on 2013-10-18 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1244425/+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 1231778] Re: wifi not working on Saucy Salamander
Can you please provide the contents of sudo aa-status /etc/apparmor.d/cache/.features /etc/apparmor.d/cache/sbin.dhclient ls -a /sys/kernel/security/apparmor/ if present (and dependent on whether its a dir or file) ls -a /sys/kernel/security/apparmor/features or cat -s /sys/kernel/security/apparmor/features -- 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/1231778 Title: wifi not working on Saucy Salamander Status in Enablement project for the Toshiba AC100 NetBook: New Status in “network-manager” package in Ubuntu: Confirmed Bug description: Lubuntu 13.10 installed from daily image have wifi not working, even with BT disabled. confirmed by stuw on IRC at Sun Sep 22 15:40 < stuw> iz1glg, I saw similar problem, but I don't know the reason and solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ac100/+bug/1231778/+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 868886] Re: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache'
*** This bug is a duplicate of bug 864368 *** https://bugs.launchpad.net/bugs/864368 I just got the same crash, simply having started pitivi and imported a 1 simple 1 hour youtube video, Lecture_13_Bayes_Nets-VfyxPtlqZh4.mp4. The bug this is a dup of, #864368, is private. Is any information available on the status, or are there other bugs that are also dups where there's more information? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pitivi in Ubuntu. https://bugs.launchpad.net/bugs/868886 Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' Status in “pitivi” package in Ubuntu: Confirmed Bug description: se cuelga cuando trato de importar un video, para editarlo. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: pitivi 0.15.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Thu Oct 6 01:40:25 2011 ExecutablePath: /usr/bin/pitivi InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110922) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: python /usr/bin/pitivi PythonArgs: ['/usr/bin/pitivi'] SourcePackage: pitivi Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' 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/pitivi/+bug/868886/+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 868886] Re: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache'
*** This bug is a duplicate of bug 864368 *** https://bugs.launchpad.net/bugs/864368 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pitivi (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pitivi in Ubuntu. https://bugs.launchpad.net/bugs/868886 Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' Status in “pitivi” package in Ubuntu: Confirmed Bug description: se cuelga cuando trato de importar un video, para editarlo. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: pitivi 0.15.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 NonfreeKernelModules: wl fglrx ApportVersion: 1.23-0ubuntu2 Architecture: i386 Date: Thu Oct 6 01:40:25 2011 ExecutablePath: /usr/bin/pitivi InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110922) InterpreterPath: /usr/bin/python2.7 PackageArchitecture: all ProcCmdline: python /usr/bin/pitivi PythonArgs: ['/usr/bin/pitivi'] SourcePackage: pitivi Title: pitivi crashed with AttributeError in _update_preview_cb(): 'PreviewWidget' object has no attribute 'preview_cache' 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/pitivi/+bug/868886/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Hello Dmitriy, or anyone else affected, Accepted gnome-settings-daemon into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- settings-daemon/3.8.5-0ubuntu11.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags removed: verification-done ** Tags added: verification-needed -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in One Hundred Papercuts: Invalid Status in Indicator keyboard: Invalid Status in Ubuntu GNOME: Fix Committed Status in “gnome-control-center” package in Ubuntu: Fix Committed Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “indicator-keyboard” package in Ubuntu: Invalid Status in “gnome-control-center” source package in Saucy: Fix Committed Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Status in “indicator-keyboard” source package in Saucy: Invalid Bug description: A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/1218322. There still remain issues regarding keyboard shortcuts though. To install: sudo add-apt-repository ppa:attente/1218322 sudo apt-get update sudo apt-get upgrade === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a key combinaison (e.g ctrl-space) -> the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source "['Shift_L']" - press and release ctrl+left shift -> the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Can't set keyboard layout change to ctrl+shift, Caps Lock, alt+shift etc. "Shift", "CapsLock" keys are just ignored in settings. Also the default shortcut was set to "Super+Space" that is inconveniently, because Dash is opening when you swich your keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1218322/+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 1227920] Re: after suspend/resume, the Unity HUD is always open when I unlock the screen
Hello Steve, or anyone else affected, Accepted gnome-settings-daemon into saucy-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/gnome- settings-daemon/3.8.5-0ubuntu11.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: gnome-settings-daemon (Ubuntu Saucy) Status: Triaged => Fix Committed ** Tags added: verification-needed -- 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/1227920 Title: after suspend/resume, the Unity HUD is always open when I unlock the screen Status in Gnome Settings Daemon: Won't Fix Status in Unity: Invalid Status in “gnome-settings-daemon” package in Ubuntu: Fix Committed Status in “unity” package in Ubuntu: Invalid Status in “gnome-settings-daemon” source package in Saucy: Fix Committed Bug description: Impact: hud is opened after resume Test case: suspend/resume your computer Regression potential: the new code is doing a tapping on the "shift" key, check that there is no input side effect due to that - Traveling at a conference, so I'm doing a lot of suspending and resuming of my laptop. Every time I open my laptop back up after resume and unlock the desktop, the Unity dash is open. This does not happen if I lock my screen using the "lock screen" hotkey, and does not happen if my screen is locked by a lid close event; only when the system suspends and resumes. But it is 100% reproducible. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130903.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-7.14-generic 3.11.1 Uname: Linux 3.11.0-7-generic x86_64 ApportVersion: 2.12.2-0ubuntu1 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,imgpng,snap,place,grid,resize,regex,mousepoll,gnomecompat,unitymtgrabhandles,vpswitch,move,animation,expo,session,wall,ezoom,staticswitcher,workarounds,fade,scale,unityshell] Date: Thu Sep 19 17:51:29 2013 InstallationDate: Installed on 2010-09-24 (1091 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-05-06 (136 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1227920/+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 1244157] Re: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access
For adding the attach_disconnected flag, unfortunately there isn't a convenient way to apply attach_disconnected without modifying the profile directly. -- 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/1244157 Title: [3.11.0-12.18 regression] "Failed name lookup - disconnected path" in dhclient D-BUS access Status in “apparmor” package in Ubuntu: New Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: New Bug description: On October 9 the NetworkManager tests started failing (https://jenkins.qa.ubuntu.com/view/Saucy/view/AutoPkgTest/job/saucy- adt-network-manager/?). Unfortunately the more recent saucy logs got lost, but the trusty ones have the information, like in https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job /trusty-adt-network-manager/1/ARCH=i386,label=adt/ In these, dhclient that gets called through NetworkManager and /usr/lib/NetworkManager/nm-dhcp-client.action cannot access the system D-BUS any more: --- NM log NetworkManager[24451]: Activation (eth42) Stage 3 of 5 (IP Configure Start) complete. Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Error: could not get the system bus. Make sure the message bus daemon is running! Message: (org.freedesktop.D Bus.Error.AccessDenied) Failed to connect to socket /var/run/dbus/system_bus_socket: Permission denied --- NM log In syslog, you see this at that time: syslog - Oct 21 14:11:24 autopkgtest kernel: [ 288.320754] type=1400 audit(1382364684.505:21): apparmor="DENIED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=18759 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=18760 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 Oct 21 14:11:24 autopkgtest kernel: [ 288.333814] type=1400 audit(1382364684.517:22): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=18752 profile="/sbin/dhclient" name="dev/log" pid=18759 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 syslog - This gets fixed if I do "sudo /etc/init.d/apparmor teardown". But it does not seem to be a problem with the policy itself; if I do "sudo aa-complain dhclient" then dmesg changes to [ 8054.314704] type=1400 audit(1382609088.727:672): apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 parent=24451 profile="/sbin/dhclient" name="dev/log" pid=24736 comm="dhclient" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 [ 8054.341409] type=1400 audit(1382609088.755:673): apparmor="ALLOWED" operation="connect" info="Failed name lookup - disconnected path" error=-13 parent=24736 profile="/usr/lib/NetworkManager/nm-dhcp-client.action" name="run/dbus/system_bus_socket" pid=24737 comm="nm-dhcp-client." requested_mask="rw" denied_mask="rw" fsuid=0 ouid=0 So this doesn't look like a problem with the policy but rather with some internal AppArmor name parsing? I found an old bug 955892 with the same error message, but that got fixed a while ago, and this does not involve ecryptfs or anythign similar. It's just a plain trusty VM with the NetworkManager autopkgtest. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1244157/+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 1067876] Re: Missing "Safely Remove Drive" option from Quicklists. Only have "Eject".
** Changed in: nautilus (Gentoo Linux) Status: Unknown => New ** Changed in: nautilus (Gentoo Linux) Importance: Unknown => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1067876 Title: Missing "Safely Remove Drive" option from Quicklists. Only have "Eject". Status in GVFS: New Status in The Linux Mint Distribution: New Status in Nautilus: New Status in abstraction for enumerating and managing block devices: Won't Fix Status in Unity: Invalid Status in “gvfs” package in Ubuntu: Fix Released Status in “udisks2” package in Ubuntu: Fix Released Status in “udisks2” package in ALT Linux: Unknown Status in Fedora: Unknown Status in “nautilus” package in Gentoo Linux: New Status in “nautilus” package in Mandriva: Confirmed Status in openSUSE: Confirmed Bug description: In Ubuntu 12.04, I could right-click on my usb-external-harddrive's Unity-Task-Bar icon (launcher icon) and select "Safely Remove". Upon doing this, the icon would disappear and I would proceed in unplugging my external hard drive. However, since upgrading to Ubuntu 12.10, this option is no longer available in the context menus (Quicklists) for external drives. Instead, all I see is "Unmount", and after clicking "Unmount" the icon remains on the task-bar (launcher) and no indication is given that would imply that the unmount occurred successfully. The intent of this report is to bring back the "Safely Remove" option which (by making the icon disappear after selected) indicates that you may now safely removal your USB external hard drive (by unplugging its usb connector). ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.8.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] Date: Wed Oct 17 14:55:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-04 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1067876/+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 1244416] [NEW] libgnome-desktop-3-7/check_gl_texture_size crashes on login
Public bug reported: After upgrade from Ubuntu 13.04 to 13.10, logging in takes a long time, showing a black screen (mouse pointer active). Unity then loads, but hardware OpenGL acceleration seems disabled. After logging in, /usr/lib /libgnome-desktop-3-7/check_gl_texture_size reports 8192. Hardware: Acer C7, Intel HD Graphics DistroRelease: Ubuntu 13.10 Package: libgnome-desktop-3-7 3.8.4-0ubuntu1 UpgradeStatus: Upgraded to saucy on 2013-10-22 (2 days ago) AssertionMessage: check_gl_texture_size: ../../../../../src/mesa/main/context.c:1501: _mesa_make_current: Assertion `newCtx->Version > 0' failed. - lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) - /usr/lib/nux/unity_support_test -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) OpenGL version string: 2.1 Mesa 9.2.1 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: no ** Affects: gnome-desktop3 (Ubuntu) Importance: Undecided Status: New ** Tags: 13.10 opengl software unity -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop3 in Ubuntu. https://bugs.launchpad.net/bugs/1244416 Title: libgnome-desktop-3-7/check_gl_texture_size crashes on login Status in “gnome-desktop3” package in Ubuntu: New Bug description: After upgrade from Ubuntu 13.04 to 13.10, logging in takes a long time, showing a black screen (mouse pointer active). Unity then loads, but hardware OpenGL acceleration seems disabled. After logging in, /usr/lib/libgnome-desktop-3-7/check_gl_texture_size reports 8192. Hardware: Acer C7, Intel HD Graphics DistroRelease: Ubuntu 13.10 Package: libgnome-desktop-3-7 3.8.4-0ubuntu1 UpgradeStatus: Upgraded to saucy on 2013-10-22 (2 days ago) AssertionMessage: check_gl_texture_size: ../../../../../src/mesa/main/context.c:1501: _mesa_make_current: Assertion `newCtx->Version > 0' failed. - lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) - /usr/lib/nux/unity_support_test -p OpenGL vendor string: VMware, Inc. OpenGL renderer string: Gallium 0.4 on llvmpipe (LLVM 3.3, 128 bits) OpenGL version string: 2.1 Mesa 9.2.1 Not software rendered:no Not blacklisted: yes GLX fbconfig: yes GLX texture from pixmap: yes GL npot or rect textures: yes GL vertex program:yes GL fragment program: yes GL vertex buffer object: yes GL framebuffer object:yes GL version is 1.4+: yes Unity 3D supported: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/1244416/+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
