[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
@Uwe: please attach the following files: 1) /var/log/gpu-manager.log 2) /var/log/Xorg.0.log 3) /etc/X11/xorg.conf (the one generated by the gpu-manager) 4)/etc/X11/xorg.conf (the one generated by amdconfig) 5) the dmesg output -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1985 dmi.boar
[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update
I also tried the version in proposed, 1:0.2.91.7 and it still doesn't work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Confirmed Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1310489] Re: xorg.conf overwritten by booting system
Hi Alberto, I can confirm that the system is running without black screen and no boot error appears. It is still not possible to swith between the graphic cards with the generated xorg.conf in amdcccle frontend or over terminal! The hardware is still the same as in the intially created bug description. I tried the following to make the system switchable: 1. Install ubuntu-drivers-common and fglrx as described in the bug-fix (incl. reboot) 2. Renamne xorg.conf into xorg.conf.201409.07 3. Generate a new xorg.conf with 'sudo amdconfig --adapter=all --initial' (this would make the system switchable) 4. When I only log off and on again I can swith from one GPU to the other 4. Reboot 5. System overwrites xorg.conf and boots without any issues but switching from one GPU to the other is not possible My question is, should we now distinguish between the black screen and the switch problem? In this case I would open a new bug. Best Regards, Uwe -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b]
[Desktop-packages] [Bug 572074]
I would suggest tabs opening next to the current being the default, except for 'app tabs'. Pinned app tab order should not be disturbed by subsequent tab opening. -- 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/572074 Title: New tabs open to the right of all existing tabs instead of opening next to the current tab Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Triaged Bug description: Binary package hint: firefox As the summary says: when a user opens a new, empty tab, it opens next to the rightmost of tabs currently open in the browser. This is inconsistent with the way links in new tabs are opened, which is to have them next to the currently active tab. Steps to reproduce: 1. Open multiple tabs in the browser. 2. Select the leftmost tab. 3. Press Ctrl + T. Expected result: Have a new, empty tab next to the leftmost tab. Actual result: The new, empty tab opens next to the rightmost tab. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic x86_64 Architecture: amd64 CheckboxSubmission: 09ae689090491ca53449589269e4bfd8 CheckboxSystem: edda5d4f616ca792bf437989cb597002 Date: Fri Apr 30 09:19:58 2010 EcryptfsInUse: Yes FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: PATH=(custom, user) LANG=fi_FI.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/572074/+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 692668] Re: nonsense behaviour when dragging the "+" sign next to a folder
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/692668 Title: nonsense behaviour when dragging the "+" sign next to a folder Status in “nautilus” package in Ubuntu: Expired Bug description: Binary package hint: nautilus Steps to reproduce: 1 Open Nautilus and put it in list view. 2 Suppose you have 3 folders: A, B and C 3 Click once on folder A to _select_ it 4 Click on the [+] sign on the left of folder B (as if you wanted to expand it) and don't release the mouse button 5 Drag it somewhere, for example into folder C, and drop it. Expected result: NOTHING should happen. Dragging the [+] sign makes no sense. It shouldn't even give you any visual feedback that you are doing something, like when you try to drag a button. An other, less correct but acceptable behaviour, would be that you would be dragging folder B, the one whose [+] sign you have clicked and dragged. Observed result: folder A, not B (not the one whose [+] sign you have dragged, but the one that was previously selected when you clicked on the completely unrelated [+] sign) is moved into where you drop, in this case into C. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: nautilus 1:2.30.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11 Uname: Linux 2.6.32-26-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Mon Dec 20 18:47:05 2010 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: PATH=(custom, no user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/692668/+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 1366458] [NEW] Sync gstreamer1.0 1.4.1-1 (main) from Debian unstable (main)
Public bug reported: Please sync gstreamer1.0 1.4.1-1 (main) from Debian unstable (main) Changelog entries since current utopic version 1.4.0-1: gstreamer1.0 (1.4.1-1) unstable; urgency=medium * New upstream bugfix release. -- Sebastian Dröge Wed, 27 Aug 2014 14:27:45 +0300 ** Affects: gstreamer1.0 (Ubuntu) Importance: Wishlist Status: New ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1366458 Title: Sync gstreamer1.0 1.4.1-1 (main) from Debian unstable (main) Status in “gstreamer1.0” package in Ubuntu: New Bug description: Please sync gstreamer1.0 1.4.1-1 (main) from Debian unstable (main) Changelog entries since current utopic version 1.4.0-1: gstreamer1.0 (1.4.1-1) unstable; urgency=medium * New upstream bugfix release. -- Sebastian Dröge Wed, 27 Aug 2014 14:27:45 +0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1366458/+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 1366459] [NEW] Sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable (main)
Public bug reported: Please sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable (main) Changelog entries since current utopic version 1.4.0-1: gst-plugins-base1.0 (1.4.1-1) unstable; urgency=medium * New upstream bugfix release. -- Sebastian Dröge Wed, 27 Aug 2014 14:32:29 +0300 ** Affects: gst-plugins-base1.0 (Ubuntu) Importance: Wishlist Status: New ** Changed in: gst-plugins-base1.0 (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1366459 Title: Sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable (main) Status in “gst-plugins-base1.0” package in Ubuntu: New Bug description: Please sync gst-plugins-base1.0 1.4.1-1 (main) from Debian unstable (main) Changelog entries since current utopic version 1.4.0-1: gst-plugins-base1.0 (1.4.1-1) unstable; urgency=medium * New upstream bugfix release. -- Sebastian Dröge Wed, 27 Aug 2014 14:32:29 +0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1366459/+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 1366455] [NEW] Sync orc 1:0.4.22-1 (main) from Debian unstable (main)
Public bug reported: Please sync orc 1:0.4.22-1 (main) from Debian unstable (main) Changelog entries since current utopic version 1:0.4.21-1: orc (1:0.4.22-1) unstable; urgency=medium * New upstream bugfix release. -- Sebastian Dröge Wed, 27 Aug 2014 12:37:05 +0300 ** Affects: orc (Ubuntu) Importance: Wishlist Status: New ** Changed in: orc (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to orc in Ubuntu. https://bugs.launchpad.net/bugs/1366455 Title: Sync orc 1:0.4.22-1 (main) from Debian unstable (main) Status in “orc” package in Ubuntu: New Bug description: Please sync orc 1:0.4.22-1 (main) from Debian unstable (main) Changelog entries since current utopic version 1:0.4.21-1: orc (1:0.4.22-1) unstable; urgency=medium * New upstream bugfix release. -- Sebastian Dröge Wed, 27 Aug 2014 12:37:05 +0300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1366455/+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 1322925] Re: Copy, paste stops working randomly in Ubuntu 14.04 nautilus
I have this problem too, it's been there for a couple of months I think. It's random and intermittent, and fixed by restarting nautilus, which of course is annoying when lots of tabs have been set up. -- 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/1322925 Title: Copy, paste stops working randomly in Ubuntu 14.04 nautilus Status in “nautilus” package in Ubuntu: Confirmed Bug description: The title says it. Since upgrade to 14.04, copy / cut / paste of files among various folders I have write rights on does not work most of the times. Using the terminal to copy / move does work normally. nautilus: Installed: 1:3.10.1-0ubuntu9.1 Candidate: 1:3.10.1-0ubuntu9.1 Version table: *** 1:3.10.1-0ubuntu9.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.10.1-0ubuntu8 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1322925/+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 1319490] Re: after install Nvidia-173 driver for trusty black sreen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1319490 Title: after install Nvidia-173 driver for trusty black sreen Status in “xorg” package in Ubuntu: Confirmed Bug description: after install Nvidia-173 driver for trusty black sreen ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3 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: Wed May 14 19:18:28 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation NV34 [GeForce FX 5200] [10de:0322] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation Device [10de:01b9] InstallationDate: Installed on 2014-05-12 (2 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Dell Computer Corporation Dimension 8300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=e5a5dd2c-a210-4eae-8011-361d62ca076b ro quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2003 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A02 dmi.board.name: 0M2035 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA02:bd07/21/2003:svnDellComputerCorporation:pnDimension8300:pvr:rvnDellComputerCorp.:rn0M2035:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: Dimension 8300 dmi.sys.vendor: Dell Computer Corporation version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed May 14 18:37:39 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB OPTICAL MOUSE MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nouveau" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nouveau" (module does not exist, 0) AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2 xserver.video_driver: modesetting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1319490/+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 657738] Re: Rhythmbox podcast rating broken
** Changed in: rhythmbox Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/657738 Title: Rhythmbox podcast rating broken Status in The Rhythmbox Music Management Application: Invalid Status in “rhythmbox” package in Ubuntu: New Bug description: Binary package hint: rhythmbox Using Rhythmbox 0.12.8, Right click a podcast episode, go to properties, details, and select a rating, such as 5-star. Notice that this doesn't add it to the "My Top Rated" playlist. Only rated music shows up, no podcasts. There is no mark on the podcast episode, the only way to see it's 5-star is to go to the properties. To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/657738/+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 1223181] Re: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging
** Bug watch added: KDE Bug Tracking System #338012 https://bugs.kde.org/show_bug.cgi?id=338012 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging Status in Eclipse: Confirmed Status in GTK+ GUI Toolkit: Unknown Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: to reproduce, I open the "Variables" view in eclipse and step through the application. the eclipse jvm crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2202aa] gtk_tree_view_get_background_area+0x8a # # Core dump written. Default location: /home/juergen/core or core.11567 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid11567.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # This did not happen in ubuntu 13.04. using KDE as a desktop (installed ubuntu, installed kde packages) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 10 07:25:17 2013 InstallationDate: Installed on 2010-11-24 (1020 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1223181/+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 1223181]
(In reply to Daniel Armbrust from comment #31) > In case people aren't aware, the workaround for this bug is to go to System > Settings -> Appliation Appearance -> GTK > > And then change the GTK2 theme from 'oxygen-gtk' to something else. > > I've been using Clearlooks myself, and it completely eliminates the bug. Changing the theme also resolved the problem for me. It seems that oxygen is severly broken. The bug has been posted in the KDE bugzilla: https://bugs.kde.org/show_bug.cgi?id=338012 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1223181 Title: After upgrading to saucy, eclipse crashes in gtk_tree_view_get_background_area+0x8a while debugging Status in Eclipse: Confirmed Status in GTK+ GUI Toolkit: Unknown Status in “gtk+2.0” package in Ubuntu: Confirmed Bug description: to reproduce, I open the "Variables" view in eclipse and step through the application. the eclipse jvm crashes with: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7f3dea4082aa, pid=11567, tid=139905336198912 # # JRE version: 7.0_21-b11 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.21-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libgtk-x11-2.0.so.0+0x2202aa] gtk_tree_view_get_background_area+0x8a # # Core dump written. Default location: /home/juergen/core or core.11567 # # An error report file with more information is saved as: # /home/juergen/hs_err_pid11567.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # This did not happen in ubuntu 13.04. using KDE as a desktop (installed ubuntu, installed kde packages) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgtk2.0-0 2.24.20-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Tue Sep 10 07:25:17 2013 InstallationDate: Installed on 2010-11-24 (1020 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) MarkForUpload: True SourcePackage: gtk+2.0 UpgradeStatus: Upgraded to saucy on 2013-08-29 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/eclipse/+bug/1223181/+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 879942] Michael Heyns
http://obsesiftakinti.com/uidg/nsig.ixyuqtecufitmvqvukb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/879942 Title: Enabling on screen keyboard in GNOME Shell starts both caribou and onboard Status in Onboard on-screen keyboard: Fix Released Status in “gnome-shell” package in Ubuntu: Confirmed Status in “onboard” package in Ubuntu: Fix Released Bug description: Enabling on screen keyboard in ubuntu 11.10 with Gnome 3.2 installed starts both caribou and onboard simultaniously. In Ubuntu 11.10 there is no way to specify default on screen keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/879942/+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 675887] Re: download dialog box disturbs in firefox
** Changed in: firefox Status: Confirmed => Fix Released -- 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/675887 Title: download dialog box disturbs in firefox Status in The Mozilla Firefox Browser: Fix Released Status in “firefox” package in Ubuntu: Triaged Bug description: Binary package hint: firefox Many times i want to download a webpage in firefox. I press ctrl + s for that or go to file->save page as... But this process pops up a new 'Download' dialog box. This box gets focus on it and looses focus on main firefox window. This is irritable. When i press ctrl +s and tell firefox to download that page i know that it is now downloading that page. i dont want it to take me to that dialog box. This is inturrupting my work flow. e.g. you can consider tthe same in chromium browser. in chromium browser when i download something or save some web page it just creates new bar at the bottom and displays the download status there, so not disturbing my work flow. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.04.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Tue Nov 16 12:42:35 2010 FirefoxPackages: firefox 3.6.12+build1+nobinonly-0ubuntu0.10.04.1 firefox-gnome-support 3.6.12+build1+nobinonly-0ubuntu0.10.04.1 firefox-branding 3.6.12+build1+nobinonly-0ubuntu0.10.04.1 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=en_IN SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/675887/+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 1251054] Re: networking didn't return from suspend
$ uname -r 3.13.0-36-generic $ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status *-network description: Wireless interface product: Centrino Wireless-N 1000 [Condor Peak] vendor: Intel Corporation $ lsmod | grep wifi iwlwifi 169932 1 iwldvm cfg80211 484040 3 iwlwifi,mac80211,iwldvm sudo killall NetworkManager or sudo kill PIDofNetworkManager works for me as well. -- 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/1251054 Title: networking didn't return from suspend Status in “network-manager” package in Ubuntu: Confirmed Bug description: Wireless networking did not work when I resumed from suspend. Using the indicator/applet to "Enable Networking" didn't associate my wireless with the AP. Plugging in an Ethernet cable did not bring back networking. The hardware rfkill switch did not bring back networking. A reboot allowed me to associate as I expected. Thanks ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-12-generic 3.11.0-12.19 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2966 F pulseaudio Date: Wed Nov 13 15:03:20 2013 HibernationDevice: RESUME=UUID=81b2976f-2830-4449-9dae-e1d44a43fa78 InstallationDate: Installed on 2012-10-18 (391 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: LENOVO 2359CTO MarkForUpload: True ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=7b8c2e1b-d2e6-47d9-9030-c078e9701a1d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-12-generic N/A linux-backports-modules-3.11.0-12-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-11-06 (7 days ago) dmi.bios.date: 09/13/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G4ET62WW (2.04 ) dmi.board.asset.tag: Not Available dmi.board.name: 2359CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG4ET62WW(2.04):bd09/13/2012:svnLENOVO:pn2359CTO:pvrThinkPadT530:rvnLENOVO:rn2359CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2359CTO dmi.product.version: ThinkPad T530 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1251054/+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 41179]
In response to claims of Chrome's superior password management, I just lived through a use case where keeping the browser's passwords decoupled from the system is much easier to work with. Short version: Changing Linux distros broke Chromium's access to my saved passwords. Please don't introduce such a fragile dependency in Firefox. I don't want to be locked in to my current OS just to keep using the same cross-platform browser. Long version: I had been using Chromium on Chakra Linux for a few years. Chakra is a "half-rolling" distro built around KDE, so it gets the latest KDE stuff faster than most other distros. Then I lived somewhere with metered Internet access for a couple months, so I switched to Firefox, using the lazy tab loading on start-up to reduce bandwidth use. (off topic: It was really annoying manually importing passwords to Firefox since it doesn't have the feature. I miss Chrome's process-per- tab model that keeps the rest of the browser fast when one tab is busy. At least NoScript mostly keeps tabs from getting too busy in the first place. Also Firefox's Tree Style Tab add-on makes it much easier to keep a zillion tabs organized.) Now that I'm living somewhere with unmetered Internet again, I've decided it's about time to do some distro-hopping and see how things have changed. Switching between various distros and desktop environments/window managers, Firefox has consistently given me access to my passwords via the master password, even when Firefox's version got shuffled back and forth. Eventually, I ended up settling on OpenSUSE 13.1 using KDE, but apparently with a slightly older and incompatible version of kwallet. I just opened Chromium for the first time since July. Since all my log-ins have expired, it wants to access saved passwords. However, despite using the same browser and desktop environment I had been in July, with both within a year of the other, Chromium cannot access my saved passwords. I'm stuck with kwallet giving me an "Error code -4: Unsupported file format revision" message. So much for Chromium. Maybe it'll work again on OpenSUSE 13.2 in a couple months? I guess I'll use Chromium for all the complicated "web 2.0" stuff that Firefox's single process chokes on. Firefox still seems best for not randomly losing abilities and for being widely extensible. -- 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/41179 Title: Integrate with Gnome Keyring Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Triaged Bug description: For a really good Gnome integration, it would be great to have the ability to save passwords in the Gnome keyring. A similar thing has been proposed for Epiphany: see https://launchpad.net/malone/bugs/3467. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/41179/+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 1286552] Re: No wifi after suspend
The problem seems to occur after kernel updates. NetworkManager needs to be restarted ('sudo kill PIDforNetworkManager") after suspend. uname -r 3.13.0-36-generic apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status *-network description: Wireless interface product: Centrino Wireless-N 1000 [Condor Peak] vendor: Intel Corporation $ lsmod | grep intel snd_intel8x0m 18830 0 snd_ac97_codec130285 3 snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m snd_hda_intel 56451 3 snd_hda_codec 192906 3 snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_hda_intel snd_pcm 102099 7 snd_ac97_codec,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m snd_page_alloc 18710 5 snd_pcm,snd_hda_intel,snd_via82xx_modem,snd_atiixp_modem,snd_intel8x0m snd69322 21 snd_ac97_codec,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_hda_codec_conexant,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec,snd_hda_intel,snd_via82xx_modem,snd_seq_device,snd_atiixp_modem,snd_intel8x0m,snd_seq_midi I've found that killing "NetworkManager" (note the caps) resolves the issue and restarts the NetworkManager applet. I can then select a wifi network & continue. -- 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/1286552 Title: No wifi after suspend Status in “linux” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Confirmed Bug description: After suspending ubuntu the wifi doesn't work. The solution given here (http://askubuntu.com/questions/368671/ubuntu-13-10-wifi-not-re- connecting-after-suspend) worked for me but when I have updated my Ubuntu now it won't work. I have tried to test mainline kernel but it won't to boot with it. To reproduce the bug : just suspend the computer and then power it. There's no wifi network until you restart the computer. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-release-upgrader-core 1:0.205.4 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CrashDB: ubuntu Date: Sat Mar 1 15:20:39 2014 InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradi 1503 F pulseaudio DistroRelease: Ubuntu 13.10 HibernationDevice: RESUME=UUID=e71568e2-e875-4053-b3b7-2046540e78bf InstallationDate: Installed on 2013-12-30 (61 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 (20131017) MachineType: Hewlett-Packard HP Compaq 6830s MarkForUpload: True Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=3eaae47b-7485-4723-8b3e-9f6dac7a01e4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 RelatedPackageVersions: linux-restricted-modules-3.11.0-15-generic N/A linux-backports-modules-3.11.0-15-generic N/A linux-firmware 1.116.2 Tags: saucy Uname: Linux 3.11.0-15-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo WifiSyslog: Mar 1 15:34:33 meradi-HP-Compaq-6830s kernel: [ 4581.474196] perf samples too long (5002 > 5000), lowering kernel.perf_event_max_sample_rate to 25000 dmi.bios.date: 03/12/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZD Ver. F.0C dmi.board.name: 30E9 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 95.1C dmi.chassis.asset.tag: CNU91609Y2 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZDVer.F.0C:bd03/12/2009:svnHewlett-Packard:pnHPCompaq6830s:pvrF.0C:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP Compaq 6830s dmi.product.version: F.0C dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1286552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-pa
[Desktop-packages] [Bug 1364458] Re: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04
OK, so what can I do to make my scanner work in the distro-updated system? I did work before I did the distro-update. Janos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1364458 Title: Hewlett-Packard ScanJet 4500C/5550C not recognized in 14.04, worked in 12.04 Status in “sane-backends” package in Ubuntu: Incomplete Bug description: After distro-upgrade from 12.04 to 14.04 simple-scan does not work. This has been an issue in the past when I tried 13.04 and I reported it as a bug. This is why I stayed with 12.04. Now that the new LTS upgrade is available I'm outof luck. I tested my Acer 64-bit laptop connecting to the scanner running the same 14.04 distro upgraded system and it works on the laptop. So this bug may not be distro related, rather desktop vs. laptop hardware related. You must have all hardware info on this particular desktop. As I said before scanner works on this desktop with 12.04 (or on Fedora-3 for that matter), but not with 13.xx or 14.04 Ubuntu. - Janos ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: simple-scan 3.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: i386 CurrentDesktop: XFCE CurrentDmesg: [ 68.374923] type=1400 audit(1409670775.512:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cups-browsed" pid=1220 comm="apparmor_parser" [ 68.643709] init: plymouth-upstart-bridge main process ended, respawning [ 90.960515] type=1400 audit(1409670797.506:47): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=1784 comm="apparmor_parser" [ 90.960540] type=1400 audit(1409670797.506:48): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1784 comm="apparmor_parser" [ 90.961486] type=1400 audit(1409670797.506:49): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=1784 comm="apparmor_parser" Date: Tue Sep 2 11:17:47 2014 DriverPackageVersions: libsane 1.0.23-3ubuntu3.1 libsane-extras N/A hplip 3.14.3-0ubuntu3.2 hpoj N/A ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2013-10-25 (312 days ago) InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820) Lsusb: Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 002: ID 03f0:1205 Hewlett-Packard ScanJet 4500C/5550C Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System Manufacturer System Name ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=bb51ea36-9854-4643-ba11-4b57e040aef3 ro quiet splash vt.handoff=7 SimpleScanLog: SourcePackage: simple-scan UpgradeStatus: Upgraded to trusty on 2014-08-13 (20 days ago) dmi.bios.date: 07/26/2004 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS A7N266-VM ACPI BIOS Rev 1008 beta 002 dmi.board.name: A7N266VM dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7N266-VMACPIBIOSRev1008beta002:bd07/26/2004:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7N266VM:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System 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/sane-backends/+bug/1364458/+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 1366440] Re: compiz crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1366351 *** https://bugs.launchpad.net/bugs/1366351 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1366351, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1366440/+attachment/4197492/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1366440/+attachment/4197507/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1366440/+attachment/4197509/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1366440/+attachment/4197510/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1366440/+attachment/4197511/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1366440/+attachment/4197512/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1366351 ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1366440 Title: compiz crashed with SIGSEGV in g_closure_invoke() Status in “compiz” package in Ubuntu: New Bug description: I just turn on my PC, then "internal error". ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-12ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 7 04:01:05 2014 Disassembly: => 0x0: Cannot access memory at address 0x0 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed (WARNING! Diff between built and installed module!) bbswitch, 0.7, 3.16.0-11-generic, x86_64: installed bbswitch, 0.7, 3.16.0-12-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-12-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-04-05 (154 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) Lsusb: 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: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=55b5aa33-1238-44d3-b0b0-6799ecc4a671 ro zswap.enabled=1 quiet splash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: N68-VGS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: 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:bvnAmericanMegatrendsInc.:bvrP1.30:bd11/14/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-VGS3FX:rvr:cvnTo
[Desktop-packages] [Bug 1366440] [NEW] compiz crashed with SIGSEGV in g_closure_invoke()
Public bug reported: I just turn on my PC, then "internal error". ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.89 Tue Jul 1 13:30:18 PDT 2014 GCC version: gcc version 4.9.1 (Ubuntu 4.9.1-12ubuntu2) .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 7 04:01:05 2014 Disassembly: => 0x0:Cannot access memory at address 0x0 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed (WARNING! Diff between built and installed module!) bbswitch, 0.7, 3.16.0-11-generic, x86_64: installed bbswitch, 0.7, 3.16.0-12-generic, x86_64: installed nvidia-331, 331.89, 3.16.0-12-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-04-05 (154 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140404) Lsusb: 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: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-12-generic root=UUID=55b5aa33-1238-44d3-b0b0-6799ecc4a671 ro zswap.enabled=1 quiet splash SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: N68-VGS3 FX dmi.board.vendor: ASRock dmi.chassis.asset.tag: 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:bvnAmericanMegatrendsInc.:bvrP1.30:bd11/14/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN68-VGS3FX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Sep 7 04:00:51 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImPS/2 Generic Wheel Mouse MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu9 ** Affects: compiz (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash compiz-0.9 need-amd64-retrace ubuntu utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1366440 Title: compiz crashed with SIGSEGV in g_closure_invoke() Status in “compiz” package in Ubuntu: New Bug description
[Desktop-packages] [Bug 1366419] Re: [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal soundcard to "off"
seem no capture controls pulseaudio don't support 4 channels volume control http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa /alsa-mixer.c?id=527078523815587bfd021bc1d10782403e9b3e84 Card hw:1 'USB'/'E-MU Systems, Inc. E-MU 0404 | USB at usb-:00:1d.7-2, high speed' Mixer name: 'USB Mixer' Components: 'USB041e:3f04' Controls : 9 Simple ctrls : 5 Simple mixer control 'PCM',0 Capabilities: pvolume pswitch pswitch-joined Playback channels: Front Left - Front Right - Rear Left - Rear Right Limits: Playback 0 - 200 Mono: Front Left: Playback 160 [80%] [-20.00dB] [on] Front Right: Playback 160 [80%] [-20.00dB] [on] Rear Left: Playback 160 [80%] [-20.00dB] [on] Rear Right: Playback 160 [80%] [-20.00dB] [on] Default sink name: alsa_output.usb-E-MU_Systems__Inc._E-MU_0404___USB_E-MU-E5-3F04-07D90512-08FE3-STATION_01-00-USB.analog-stereo Default source name: alsa_output.usb-E-MU_Systems__Inc._E-MU_0404___USB_E-MU-E5-3F04-07D90512-08FE3-STATION_01-00-USB.analog-stereo.monitor -- 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/1366419 Title: [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal soundcard to "off" Status in “alsa-driver” package in Ubuntu: New Bug description: There seems to be no easy way to tell the application which soundcard to choose. Sometimes it works, sometimes it works half, but mostly it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Sep 6 16:38:49 2014 InstallationDate: Installed on 2014-07-14 (54 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB failed Symptom_Card: E-Mu 0404 - E-MU 0404 | USB Symptom_Type: None of the above Title: [USB-Audio - E-MU 0404 | USB, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.0F dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0D dmi.chassis.asset.tag: CNU9501Y74 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.0F:bd10/20/2009:svnHewlett-Packard:pnHPProBook4510s:pvrF.0F:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4510s dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1366419/+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 36812]
(In reply to comment #129) > As far as I can tell, it is already clear that XKB specifications needs to > be extended for this to be cleanly solved. While Ilya's hack works for many > people, and as much as I would like to see this fixed, I understand why it > is unacceptable to the developers. ... > there's two-ish ppl working on input at them moment, both are badly > overloaded because there's a lot of bugs and plenty new features that ppl > cry out for. so this bug has less to do with purist reasons, it's more along > the lines of "i've got so many things to do that don't break the spec, they > get priority". So I understand that this issue is currently not worked on by Xorg developers. Priorities are a good thing, and I'm currently comfortable with the pragmatic approach of the downstream distributions applying Ilya's patch in their packages (which works fine for a lot of happy users who have reported as such - I have yet to hear a report where Ilya's patch is not improving behavior for multi-language users). Still: 1) Its a good idea to have the pragmatic patch set maintained in this bug report - even if it will never be applied to upstream Xorg, simply as a central point for downstream distributors to get access to a reasonable workaround until a "correct" solution is available. 2) It will be a real shame if this issue, that is actively discussed by the community for 10 years now and is hurting a lot of users, will be ignored for another 10 years. In the mean time XKB2 - that was supposed to be the solution to all our problems - was relegated from "being worked on" to "being thought on" to "being dreamed of" (around 2010) and now appears to have fallen to the status of "it will never be important enough". -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in GNOME Control Center: Unknown Status in X.Org X server: In Progress Status in “control-center” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: Fix Released Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 1365695] Re: No longer able to use GUI after update
I can confirm now that downgrading to ubuntu-drivers-common=1:0.2.91.4 as suggested by Fabio actually seems to work, whereas ubuntu-drivers- common=1:0.2.91.5 was not enough. I also didn't have to reinstall nvidia drivers, the downgrade alone seems to be enough. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Confirmed Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1336184] Re: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes
@sumedh Where did you see that mounting a FAT32 device adds the "flush" mount option? In this moment I have both an ext4 and a ntfs external hdds mounted and running. reading from a "cat /etc/mtab" output none of them has the flush option, but I'm pretty sure that with the ext4 hdd I don't have this problem. I noticed that the NTFS device has "fuseblk" as mount type. Maybe the "problem" is inside fuse. Here is my cat /etc/mtab portion: /dev/sdd1 /media/michele/47D7D336684BC661 fuseblk rw,nosuid,nodev,allow_other,default_permissions,blksize=4096 0 0 /dev/sdc /media/michele/Backup_Server ext4 rw,nosuid,nodev,uhelper=udisks2 0 0 -- 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/1336184 Title: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes Status in “nautilus” package in Ubuntu: Confirmed Bug description: Release: Ubuntu 14.04 Nautilus version: 1:3.10.1-0ubuntu9.1 Expected: After pressing "Eject" on a flash drive (formatted with NTFS -- haven't tried with FAT yet) I expected it to return only after flushing and unmounting the drive so the drive is completely safe to remove at that point What happened: "Eject" returned after a short while. The drive still kept writing for a long time. Mount shows the drive still mounted for the period while the flash drive keeps blinking though "df" does not show the drive anymore. Removing the drive at this point results in partial file write and NTFS filesystem damage (fixable with ntfsfix but dangerous). Steps to reproduce: 1) Insert a flash drive (tried with NTFS mounted drive though I believe FAT will show similar behaviour though latter uses "flush" mount option so may not be that prominent) 2) Try copying a large file. For testing use a size that will also mostly fit into filesystem cache so that real wait for writing is during unmount: dd if=/dev/zero of=/media///test.out bs=1M count=1000 is the user name and the name where drive was mounted by nautilus as per the label. 3) "Eject" the drive from nautilus context menu after dd command above returns. 4) Eject returns shortly. However drive is still writing as seen by the blinking, or disk throughput in gkrellm, iostat. Also note that "mount" still shows the drive as mounted though "df" and other tools don't. I have confirmed the same issue exists on all similar file managers namely nemo and caja. Haven't filed bugs against those yet. For comparison, the gnome-disks system utility correctly unmounts, ejects and stops the drive (last one even powers down the drive so the LED on drive is switched off which one would expect nautilus "Eject" to also do) so it doesn't seem to be a bug in udisks2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1336184/+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 1271839] Re: ibus-ui-gtk3 big memory leak
Saw 1.8GB mem usage on 14.04 desktop 64 bit - this might help http://askubuntu.com/a/490326 -- 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/1271839 Title: ibus-ui-gtk3 big memory leak Status in “ibus” package in Ubuntu: Expired Bug description: ubuntu 13.10 64bit 2gb of memory leak Also seen on Ubuntu 14.04 64Bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+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 1336184] Re: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes
Hi, this afternoon I realized I have the same problem. I never noticed before because i often work with FAT32 or EXT filesystems, that aren't affected from this problem ** Tags added: trusty -- 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/1336184 Title: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes Status in “nautilus” package in Ubuntu: Confirmed Bug description: Release: Ubuntu 14.04 Nautilus version: 1:3.10.1-0ubuntu9.1 Expected: After pressing "Eject" on a flash drive (formatted with NTFS -- haven't tried with FAT yet) I expected it to return only after flushing and unmounting the drive so the drive is completely safe to remove at that point What happened: "Eject" returned after a short while. The drive still kept writing for a long time. Mount shows the drive still mounted for the period while the flash drive keeps blinking though "df" does not show the drive anymore. Removing the drive at this point results in partial file write and NTFS filesystem damage (fixable with ntfsfix but dangerous). Steps to reproduce: 1) Insert a flash drive (tried with NTFS mounted drive though I believe FAT will show similar behaviour though latter uses "flush" mount option so may not be that prominent) 2) Try copying a large file. For testing use a size that will also mostly fit into filesystem cache so that real wait for writing is during unmount: dd if=/dev/zero of=/media///test.out bs=1M count=1000 is the user name and the name where drive was mounted by nautilus as per the label. 3) "Eject" the drive from nautilus context menu after dd command above returns. 4) Eject returns shortly. However drive is still writing as seen by the blinking, or disk throughput in gkrellm, iostat. Also note that "mount" still shows the drive as mounted though "df" and other tools don't. I have confirmed the same issue exists on all similar file managers namely nemo and caja. Haven't filed bugs against those yet. For comparison, the gnome-disks system utility correctly unmounts, ejects and stops the drive (last one even powers down the drive so the LED on drive is switched off which one would expect nautilus "Eject" to also do) so it doesn't seem to be a bug in udisks2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1336184/+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 1336184] Re: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/1336184 Title: USB flash drive (NTFS) keeps writing for quite a while even after "Eject" completes Status in “nautilus” package in Ubuntu: Confirmed Bug description: Release: Ubuntu 14.04 Nautilus version: 1:3.10.1-0ubuntu9.1 Expected: After pressing "Eject" on a flash drive (formatted with NTFS -- haven't tried with FAT yet) I expected it to return only after flushing and unmounting the drive so the drive is completely safe to remove at that point What happened: "Eject" returned after a short while. The drive still kept writing for a long time. Mount shows the drive still mounted for the period while the flash drive keeps blinking though "df" does not show the drive anymore. Removing the drive at this point results in partial file write and NTFS filesystem damage (fixable with ntfsfix but dangerous). Steps to reproduce: 1) Insert a flash drive (tried with NTFS mounted drive though I believe FAT will show similar behaviour though latter uses "flush" mount option so may not be that prominent) 2) Try copying a large file. For testing use a size that will also mostly fit into filesystem cache so that real wait for writing is during unmount: dd if=/dev/zero of=/media///test.out bs=1M count=1000 is the user name and the name where drive was mounted by nautilus as per the label. 3) "Eject" the drive from nautilus context menu after dd command above returns. 4) Eject returns shortly. However drive is still writing as seen by the blinking, or disk throughput in gkrellm, iostat. Also note that "mount" still shows the drive as mounted though "df" and other tools don't. I have confirmed the same issue exists on all similar file managers namely nemo and caja. Haven't filed bugs against those yet. For comparison, the gnome-disks system utility correctly unmounts, ejects and stops the drive (last one even powers down the drive so the LED on drive is switched off which one would expect nautilus "Eject" to also do) so it doesn't seem to be a bug in udisks2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1336184/+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 1240198] Re: Wrong keyboard layout active after booting into desktop
Same here. It happens seldom but it's really annoying. For me the fix from the duplicate bug comments gsettings set org.gnome.desktop.input-sources current 0 works fine. Funny thing: Login has german layout (my password wouldnt work otherwise) but the gnome shell has already us keyboard, eg [] instaed of öä. Don't have unity installed. Its a fresh ubuntu 14.04 gnome install on an ideapad . System settings have only german an report german even if have us layout. (And everybody who thinks this is only low priority should be forced to use a strange keyboard layout for more than 1h while working... ;) -- 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/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE="de_DE.UTF-8" LC_NUMERIC="de_DE.UTF-8" LC_TIME="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_MONETARY="de_DE.UTF-8" LC_MESSAGES="de_DE.UTF-8" LC_PAPER="de_DE.UTF-8" LC_NAME="de_DE.UTF-8" LC_ADDRESS="de_DE.UTF-8" LC_TELEPHONE="de_DE.UTF-8" LC_MEASUREMENT="de_DE.UTF-8" LC_IDENTIFICATION="de_DE.UTF-8" LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="" # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 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: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+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 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** No longer affects: vte -- 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/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in “vte” package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1340687/+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 1345546] Re: [Upstream] Dates in cell change randomly on load
** Summary changed: - dates in cell change randomly on load + [Upstream] Dates in cell change randomly on load -- 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/1345546 Title: [Upstream] Dates in cell change randomly on load Status in LibreOffice Productivity Suite: Incomplete Status in “libreoffice” package in Ubuntu: New Bug description: Problem description: Steps to reproduce: 0. This is on Ubuntu x86_64 in german local, I did not test others. 1. Set Settings -> Libreoffice Calc -> "Berechnen" (Calculation?) -> Date = 1.1.1904 2. Create new spreadsheet 3. Enter 2.6.2014 in the cell (here: german date format, maybe 2014-06-02 in English) 4. Save file 5. Close file 6. Reopen file 7. Display file 8. save the file Current behavior: After step 4, 2014-06-02 is saved in content.xml in the ods file: 02.06.14 But it step 7, it is display as 1.6.2010 (that is 2010-06-01) . After saving in step 8, content.xml contains: 01.06.10 The current mode of operation breaks file display and corrupts the original file! Expected behavior: The date should not change, neither while displaying nor when saving the file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.4-0ubuntu2 Uname: Linux 3.15.0-031500rc7-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jul 20 12:58:26 2014 SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-06-18 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+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 1366426] [NEW] [Super][Alt] is interpreted as [Super] if [Super] is pressed first
Public bug reported: If is pressed first in a key chord, is disregarded. Steps: - go to Settings->Keyboard->Shortcuts->Launchers - set the shortcut for "Launch calculator" to Alt+Super+C (note, here the order in which Alt and Super are pressed does not matter) - press Alt+Super+C (in that order, Alt first). The calculator launches. - press Super+Alt+C (in that order, Super first). The dash opens with the Photos lens. Tested on two different machines (14.04) and keyboards, and with a freshly created user. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Sep 7 00:12:12 2014 InstallationDate: Installed on 2014-09-01 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1366426 Title: [Super][Alt] is interpreted as [Super] if [Super] is pressed first Status in “unity” package in Ubuntu: New Bug description: If is pressed first in a key chord, is disregarded. Steps: - go to Settings->Keyboard->Shortcuts->Launchers - set the shortcut for "Launch calculator" to Alt+Super+C (note, here the order in which Alt and Super are pressed does not matter) - press Alt+Super+C (in that order, Alt first). The calculator launches. - press Super+Alt+C (in that order, Super first). The dash opens with the Photos lens. Tested on two different machines (14.04) and keyboards, and with a freshly created user. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Sun Sep 7 00:12:12 2014 InstallationDate: Installed on 2014-09-01 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1366426/+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 1345546] Re: dates in cell change randomly on load
** Changed in: df-libreoffice Status: New => Incomplete -- 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/1345546 Title: dates in cell change randomly on load Status in LibreOffice Productivity Suite: Incomplete Status in “libreoffice” package in Ubuntu: New Bug description: Problem description: Steps to reproduce: 0. This is on Ubuntu x86_64 in german local, I did not test others. 1. Set Settings -> Libreoffice Calc -> "Berechnen" (Calculation?) -> Date = 1.1.1904 2. Create new spreadsheet 3. Enter 2.6.2014 in the cell (here: german date format, maybe 2014-06-02 in English) 4. Save file 5. Close file 6. Reopen file 7. Display file 8. save the file Current behavior: After step 4, 2014-06-02 is saved in content.xml in the ods file: 02.06.14 But it step 7, it is display as 1.6.2010 (that is 2010-06-01) . After saving in step 8, content.xml contains: 01.06.10 The current mode of operation breaks file display and corrupts the original file! Expected behavior: The date should not change, neither while displaying nor when saving the file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.4-0ubuntu2 Uname: Linux 3.15.0-031500rc7-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jul 20 12:58:26 2014 SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-06-18 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+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 1366423] [NEW] My wifi connection is unstable. It disconnects every few minutes. Sometime it will reconnect on its own and at other times I have to manually reconnect. I have W
Public bug reported: arthik@Karthik-Linux:~$ sudo lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: eth0 version: 02 serial: 6c:62:6d:85:93:7b size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:41 ioport:d800(size=256) memory:febff000-febf memory:fdff-fdff memory:febc-febd *-network description: Wireless interface physical id: 1 bus info: usb@1:6 logical name: wlan0 serial: c0:4a:00:21:a8:c3 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8192cu driverversion=3.13.0-35-generic firmware=N/A ip=192.168.8.110 link=yes multicast=yes wireless=IEEE 802.11bgn karthik@Karthik-Linux:~$ ubuntu-bug -w karthik@Karthik-Linux:~$ ubuntu-bug evince karthik@Karthik-Linux:~$ ubuntu-bug evince karthik@Karthik-Linux:~$ Created new window in existing browser session. sudo lshw -C network [sudo] password for karthik: *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: eth0 version: 02 serial: 6c:62:6d:85:93:7b size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:41 ioport:d800(size=256) memory:febff000-febf memory:fdff-fdff memory:febc-febd *-network description: Wireless interface physical id: 1 bus info: usb@1:6 logical name: wlan0 serial: c0:4a:00:21:a8:c3 capabilities: ethernet physical wireless configuration: broadcast=yes driver=rtl8192cu driverversion=3.13.0-35-generic firmware=N/A ip=192.168.8.110 link=yes multicast=yes wireless=IEEE 802.11bgn ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 15:11:28 2014 InstallationDate: Installed on 2014-09-04 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1366423 Title: My wifi connection is unstable. It disconnects every few minutes. Sometime it will reconnect on its own and at other times I have to manually reconnect. I have Windows 8.1 running on a different partition in the same machine. Wifi works fine in Windows 8.1. So, this seems to be an issue with Ubuntu. Status in “evince” package in Ubuntu: New Bug description: arthik@Karthik-Linux:~$ sudo lshw -C network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:02:00.0 logical name: eth0 version: 02 serial: 6c:62:6d:85:93:7b size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:41 ioport:d800(size=256) memory:febff000-febf memory:fdff-fdff memory:febc-febd *-network description: Wireless interface physical id: 1 bus info: usb@1:6 logical name:
[Desktop-packages] [Bug 1345546]
I cannot confirm: Bodhi Linux 2.x (built on Ubuntu 12.04) LibreOffice 4.3.1.2 release Please try the following: https://wiki.documentfoundation.org/UserProfile and try installing 4.3. With three QA members now committing time and not being able to reproduce - I'm afraid that this might be your computer environment causing something to happen and therefore WORKSFORME. That being said, for now throwing in NEEDINFO - try the above steps and if you still see the problem mark as UNCONFIRMED and we'll see where to go from there. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1345546 Title: dates in cell change randomly on load Status in LibreOffice Productivity Suite: Incomplete Status in “libreoffice” package in Ubuntu: New Bug description: Problem description: Steps to reproduce: 0. This is on Ubuntu x86_64 in german local, I did not test others. 1. Set Settings -> Libreoffice Calc -> "Berechnen" (Calculation?) -> Date = 1.1.1904 2. Create new spreadsheet 3. Enter 2.6.2014 in the cell (here: german date format, maybe 2014-06-02 in English) 4. Save file 5. Close file 6. Reopen file 7. Display file 8. save the file Current behavior: After step 4, 2014-06-02 is saved in content.xml in the ods file: 02.06.14 But it step 7, it is display as 1.6.2010 (that is 2010-06-01) . After saving in step 8, content.xml contains: 01.06.10 The current mode of operation breaks file display and corrupts the original file! Expected behavior: The date should not change, neither while displaying nor when saving the file. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice-calc 1:4.2.4-0ubuntu2 Uname: Linux 3.15.0-031500rc7-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jul 20 12:58:26 2014 SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-06-18 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1345546/+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 1366419] [NEW] [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal soundcard to "off"
Public bug reported: There seems to be no easy way to tell the application which soundcard to choose. Sometimes it works, sometimes it works half, but mostly it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Sep 6 16:38:49 2014 InstallationDate: Installed on 2014-07-14 (54 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB failed Symptom_Card: E-Mu 0404 - E-MU 0404 | USB Symptom_Type: None of the above Title: [USB-Audio - E-MU 0404 | USB, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.0F dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0D dmi.chassis.asset.tag: CNU9501Y74 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.0F:bd10/20/2009:svnHewlett-Packard:pnHPProBook4510s:pvrF.0F:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4510s dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1366419 Title: [USB-Audio - E-MU 0404 | USB, playback] No Playback even with internal soundcard to "off" Status in “alsa-driver” package in Ubuntu: New Bug description: There seems to be no easy way to tell the application which soundcard to choose. Sometimes it works, sometimes it works half, but mostly it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Sat Sep 6 16:38:49 2014 InstallationDate: Installed on 2014-07-14 (54 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB failed Symptom_Card: E-Mu 0404 - E-MU 0404 | USB Symptom_Type: None of the above Title: [USB-Audio - E-MU 0404 | USB, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PZI Ver. F.0F dmi.board.name: 3072 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 24.0D dmi.chassis.asset.tag: CNU9501Y74 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZIVer.F.0F:bd10/20/2009:svnHewlett-Packard:pnHPProBook4510s:pvrF.0F:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4510s dmi.product.version: F.0F dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1366419/+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 1310489] Re: xorg.conf overwritten by booting system
Hi Alberto Did as asked, but no avail. Same black screen appears on reboot. I have attached the files as asked. Thanks Abhijit ** Attachment added: "files2.zip" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4197421/+files/files2.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2013 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag:
[Desktop-packages] [Bug 1029289] Re: Need to authorize my google account each time I boot the computer
The upstream developers have fixed it Shouldnt the LTS version be fixed first and get almost all the attention from developers? Also 12.04.5 has a major flaw if you try to install virtualbox... the kernel module isnt yet available. Another LTS fail. Everything is going the wrong way with ubuntu... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1029289 Title: Need to authorize my google account each time I boot the computer Status in Online Accounts: Account plugins: In Progress Status in Online Accounts: OAuth2 plug-in: Unknown Status in Online Accounts: Sign-on UI: Fix Released Status in “account-plugins” package in Ubuntu: Fix Released Status in “evolution-data-server” package in Ubuntu: Confirmed Status in “signon-plugin-oauth2” package in Ubuntu: Fix Released Status in “account-plugins” source package in Quantal: Fix Released Status in “signon-plugin-oauth2” source package in Quantal: Fix Released Bug description: [Impact] Google calendar integration is broken, and users are requested to re-enter their Google password everytime they log in, or everytime they enable/disable their Google account from the System Settings. [Test Case] Disable/re-enable your Google account. When affected by this bug, a notification will appear and you'll be asked to enter your Google password in the Online Accounts panel in System Settings. [Regression Potential] Minimal: the fix is a backport of a patch from the evolution-data-server code which is already in 14.10, and which only touches the calendar code (which is currently broken). Old description === [Test Case] Sometimes after one day, sometimes after one week, the system indicator will turn red and the Google account will be marked as needing reauthentication. Time can vary, but any period shorter than one month is a symptom of the bug. [Regression Potential] Minimal: the change to the Google plugin (in account-plugins) simply changes the authentication method, in a way that is well-documented. The change in signon-plugin-oauth2 affects only those accounts/providers which use the OAuth refresh tokens -- which is only Google, at the moment -- and in a way that can't possibly break any existing functionality; if the new code had some mistake, the refresh token would be unusable and the system would automatically fall back to requesting a new access token (which is exactly what happens now, with this bug). I'll try to find why the account-plugins package was not uploaded; indeed, both are required in order to fix this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1029289/+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 1366413] [NEW] Android tethering does not work when network manager is running
Public bug reported: After lost many hours trying to discover why the USB Tethering of my LG E615f and my friend's LG E470 android phones, I just realised: (with cable unplugged) alex@ubuntu_asus:~$ sudo start network-manager network-manager start/running, process 3843 (plugging the cable and start tethering) alex@ubuntu_asus:~$ ip link (...) 9: usb0: mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff But, when I try without network-manager (with cable unplugged) alex@ubuntu_asus:~$ sudo stop network-manager network-manager stop/waiting (plugging again and starting tethering) alex@ubuntu_asus:~$ ip addr (...) 10: usb0: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff I tried many times and aways got the same result. I've found this problem in both raring and Ubuntu 14.04, but only in raring I have tested this soluction. alex@ubuntu_asus:~$ lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 alex@ubuntu_asus:~$ apt-cache policy network-manager network-manager: Installed: 0.9.4.0-0ubuntu4.3 Candidate: 0.9.8.0-0ubuntu6.1 Version table: 0.9.8.0-0ubuntu6.1 0 500 http://old-releases.ubuntu.com/ubuntu/ raring-updates/main amd64 Packages 0.9.8.0-0ubuntu6 0 500 http://old-releases.ubuntu.com/ubuntu/ raring/main amd64 Packages *** 0.9.4.0-0ubuntu4.3 0 100 /var/lib/dpkg/status ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: android carrier tethering usb ** Attachment added: "tail from syslog with and without nm running" https://bugs.launchpad.net/bugs/1366413/+attachment/4197398/+files/out-nm.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1366413 Title: Android tethering does not work when network manager is running Status in “network-manager” package in Ubuntu: New Bug description: After lost many hours trying to discover why the USB Tethering of my LG E615f and my friend's LG E470 android phones, I just realised: (with cable unplugged) alex@ubuntu_asus:~$ sudo start network-manager network-manager start/running, process 3843 (plugging the cable and start tethering) alex@ubuntu_asus:~$ ip link (...) 9: usb0: mtu 1500 qdisc pfifo_fast state DOWN qlen 1000 link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff But, when I try without network-manager (with cable unplugged) alex@ubuntu_asus:~$ sudo stop network-manager network-manager stop/waiting (plugging again and starting tethering) alex@ubuntu_asus:~$ ip addr (...) 10: usb0: mtu 1500 qdisc noop state DOWN qlen 1000 link/ether 02:61:5a:5d:30:2c brd ff:ff:ff:ff:ff:ff I tried many times and aways got the same result. I've found this problem in both raring and Ubuntu 14.04, but only in raring I have tested this soluction. alex@ubuntu_asus:~$ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 alex@ubuntu_asus:~$ apt-cache policy network-manager network-manager: Installed: 0.9.4.0-0ubuntu4.3 Candidate: 0.9.8.0-0ubuntu6.1 Version table: 0.9.8.0-0ubuntu6.1 0 500 http://old-releases.ubuntu.com/ubuntu/ raring-updates/main amd64 Packages 0.9.8.0-0ubuntu6 0 500 http://old-releases.ubuntu.com/ubuntu/ raring/main amd64 Packages *** 0.9.4.0-0ubuntu4.3 0 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1366413/+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 36812]
As far as I can tell, it is already clear that XKB specifications needs to be extended for this to be cleanly solved. While Ilya's hack works for many people, and as much as I would like to see this fixed, I understand why it is unacceptable to the developers. So, trying to delve into XKB specs now; this page seems to be a good starting point to me: https://wiki.archlinux.org/index.php/X_KeyBoard_extension Also (as suggested by the author), copying info here from https://bugzilla.redhat.com/show_bug.cgi?id=660254 Peter Hutterer 2011-01-05 22:07:57 EST there is two problems with the "tiny" patch you mentioned. one, it's an _explicit_ violation of the XKB specification (see section 4.4). two, implementing this behaviour requires guesswork that I'm not sure is safe in a number of setups. Peter Hutterer 2011-01-06 17:12:05 EST (In reply to comment #4) > But: doesn't fixing of a huge problem have a priority over preservation of a > "holy spec"? it's a matter of figuring out the side-effects. a specification is a behaviour promise, in this case in place for 15 years or so. a lot of users and apps rely on the promised behaviour (in general, not necessarily this specific issue) and breaking it is a dangerous thing because you may not know what else you break. this is why we're hesitant to break the behaviour on purpose. note that i'm not claiming that there is no problem, i'm just saying it's the balance between a known problem and introducing new bugs that potentially break current applications. > > two, > > implementing this behaviour requires guesswork that I'm not sure is safe in > > a > > number of setups. > > What guesswork do you mean? Which setups can present problems? > BTW, I'm 100% sure that Ilya Murav'jev (patch author) will be glad to > cooperate. afaict, the desired behaviour for a ctrl+shift groupchange is: ctrl down → set Control modifier shift down → set Shift modifier if (other key pressed) send event Contrl+Shift+ else if (ctrl || shift released) change group The XKB map for left control in this case is: key { [ Control_L, ISO_Next_Group ] }; So whenever ISO_Next_Group is pressed, you still need to know which modifier to set in case the group action isn't executed. The XkbSA_SetMod, XkbSA_LockMod, etc. actions provide the modifiers set for a given key, hence why it works currently. This information comes from the client when the xkb map is loaded and is used to trigger the modifier flags for a given key. The XkbSA_LockGroup behaviour (which is triggered at ISO_Next_Group) does not have this field (adding it would break ABI), so you need to guess which modifiers to set if you didn't trigger this action. This is the main stumbling point that I found and if you look at Ilya's patch that's where he needs the big hack that I'm not comfortable at all with it. Now, I don't know if there are layouts where the modifier mask would be different on the second level as opposed to the first (and Ilya's hack or a similar attempt would fail completely) but there's so many layouts that it'll take a while to get through them all. > And leaving the design bug because of purist reason looks really strange... there's two-ish ppl working on input at them moment, both are badly overloaded because there's a lot of bugs and plenty new features that ppl cry out for. so this bug has less to do with purist reasons, it's more along the lines of "i've got so many things to do that don't break the spec, they get priority". -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in GNOME Control Center: Unknown Status in X.Org X server: In Progress Status in “control-center” package in Ubuntu: Invalid Status in “xorg-server” package in Ubuntu: Fix Released Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a r
[Desktop-packages] [Bug 1366406] [NEW] Virtualbox capture error webm(vp8)
Public bug reported: virtualbox libvpx used to capture video in webm format, in ubuntu the file created is corrupt using the relevant library. Ubuntu 14.04.1 Virtualbox Version: 4.3.14 r95030 Forum virtualbox https://forums.virtualbox.org/viewtopic.php?f=7&t=63487. ** Affects: libvpx (Ubuntu) Importance: Undecided Status: New ** Attachment added: "I file generated is not correct" https://bugs.launchpad.net/bugs/1366406/+attachment/4197396/+files/vlc_virtualbox.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libvpx in Ubuntu. https://bugs.launchpad.net/bugs/1366406 Title: Virtualbox capture error webm(vp8) Status in “libvpx” package in Ubuntu: New Bug description: virtualbox libvpx used to capture video in webm format, in ubuntu the file created is corrupt using the relevant library. Ubuntu 14.04.1 Virtualbox Version: 4.3.14 r95030 Forum virtualbox https://forums.virtualbox.org/viewtopic.php?f=7&t=63487. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1366406/+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 1320560] Re: Removal of gdmflexiserver breaks user switching
** Also affects: xfce4-whiskermenu-plugin (Ubuntu) Importance: Undecided Status: New ** Changed in: xfce4-whiskermenu-plugin (Ubuntu) Status: New => Confirmed -- 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/1320560 Title: Removal of gdmflexiserver breaks user switching Status in “xfce4-panel” package in Ubuntu: Confirmed Status in “xfce4-whiskermenu-plugin” package in Ubuntu: Confirmed Status in “xfswitch-plugin” package in Ubuntu: Confirmed Status in “xscreensaver” package in Ubuntu: Confirmed Bug description: Hello and pardon for my bad english. On xfce4, the button to log with a new user without logout never wants to works. It accepts to open a confirmation windows "To you really want to change user?" That's OK. Then I press Yes and I've got an error message who says in french : "Impossible to create a new display" and in english : "GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.DisplayManager was not provided by any .service files" lsb_release-rd : Description:Ubuntu 14.04 LTS Release:14.04 apt-cache policy xfswitch-plugin xfswitch-plugin: Installé : 0.0.1-4ubuntu1 Candidat : 0.0.1-4ubuntu1 Table de version : *** 0.0.1-4ubuntu1 0 500 http://fr.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Thanks for your help. Claude Micouin ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfswitch-plugin 0.0.1-4ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Sun May 18 00:20:57 2014 InstallationDate: Installed on 2014-05-07 (10 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: xfswitch-plugin UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1320560/+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 1360005] Re: Cyrillic symbols looks strange when using autocompletion
So it is a bash or bash-completion problem (not sure which), but not gnome-terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1360005 Title: Cyrillic symbols looks strange when using autocompletion Status in “bash-completion” package in Ubuntu: New Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: You need use autocompletion (via TAB button) to folder/file/etc to cyrillic symbols and at least one space in its name to reproduce this bug. Then symbols in name look strange, but your command works correct. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 22 02:52:51 2014 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-06-01 (81 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcEnviron: PATH=(custom, no user) LANGUAGE=ru XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1360005/+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 783856] Re: Thunderbird 3.1.10 Crash Report [@ uGlobalMenuBar::~uGlobalMenuBar ]
There hasn't been any crashes on crash-stats.mozilla.com with this signature in the last 30 days. ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Fix Released ** Changed in: thunderbird (Ubuntu Natty) Status: Triaged => Fix Released -- 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/783856 Title: Thunderbird 3.1.10 Crash Report [@ uGlobalMenuBar::~uGlobalMenuBar ] Status in Unity global menubar extension for Firefox and Thunderbird: Fix Released Status in Global menubar extension 1.0 series: Fix Released Status in “firefox” package in Ubuntu: Fix Released Status in “thunderbird” package in Ubuntu: Fix Released Status in “firefox” source package in Natty: Fix Released Status in “thunderbird” source package in Natty: Fix Released Bug description: *** TEST CASE FOR SRU *** Note that whilst this bug affects both Thunderbird and Firefox, the only extension I've found which triggers it will only work in Thunderbird (and most of the crash reports upstream are for Thunderbird) Preparation: - Install the "MR Tech Toolkit" extension from https://addons.mozilla.org/en-US/firefox/addon/mr-tech-toolkit/ Test: - Run Thunderbird and go to Tools -> Add-ons Result: - The old version will crash - With the new version, the addons dialog shall appear and there will be a functioning menubar in the panel There's a fair few of these: https://crash- stats.mozilla.com/report/list?product=Thunderbird&platform=linux&query_search=signature&query_type=contains&query=uGlobalMenu&reason_type=contains&date=05%2F16%2F2011%2023%3A29%3A46&range_value=1&range_unit=weeks&hang_type=any&process_type=any&do_query=1&signature=uGlobalMenuBar%3A%3A~uGlobalMenuBar Some example comments: "Tools > Add Ins > *Boom* (Reproducible every time I use this menu option) Profile directory was copied over from another machine." "activated unity menu bar and clicking on Add-ons" "When I click the "Addons" link on the Thunderbird toolbar, the whole program crashes." It seems like it's linked to the Addons window, but I haven't been able to reproduce To manage notifications about this bug go to: https://bugs.launchpad.net/globalmenu-extension/+bug/783856/+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 1274726] Re: Rhythmbox "Control" menu states that Control-Space controls play/pause, but actually Control-P is the shortcut
** Changed in: rhythmbox Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1274726 Title: Rhythmbox "Control" menu states that Control-Space controls play/pause, but actually Control-P is the shortcut Status in The Rhythmbox Music Management Application: Invalid Status in “rhythmbox” package in Ubuntu: New Bug description: The keyboard shortcut for play/pause is documented in the help system of rhythmbox 2.99.1 as being CTRL+Spacebar (which is what I'm used to), but it doesn't work. Playing a song, then hitting CTRL+Space does not pause it, it just seems to toggle the highlighting of the current track down in the tracks pane. Can we please restore the behavior of CTRL+Spacebar? In Rhythmbox 3.0.2 the shorcut Control-P is what is being used for this functionality, but Control-space is still being mentioned in the "Control" menu. To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1274726/+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 378668] Re: Cursor in terminal behaves badly with special characters present
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. ** Changed in: bash (Ubuntu) Status: New => Incomplete ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xfce4-terminal (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/378668 Title: Cursor in terminal behaves badly with special characters present Status in “bash” package in Ubuntu: Incomplete Status in “gnome-terminal” package in Ubuntu: Incomplete Status in “xfce4-terminal” package in Ubuntu: Incomplete Bug description: Binary package hint: xfce4-terminal Both xfce4-terminal and gnome-terminal are affected, but not the text- only terminals (alt+f1, f2 etc.). So probably the package hint is wrong... Description: With special characters present before the $ sign, when going back to the previous line (backspace or cursor keys), the cursor jumps to the left too far (one character per special character). How to reproduce (cf. always my attachment): 1. Open the terminal (in X, not the real text-only screens) 2. Create a folder with special characters in it, e.g. with german special characters: $ mkdir abcäöü 3. Go to the special character folder. $ cd abcäöü 4. Type some rubbish until you reach the end of the screen (in my attached example: "abcdefghijklmnopqrst". As soon as you have filled up the last column (the "t" in my case), the cursor jumps correctly to the next line. 5. Hit backspace or the left cursor once. Backspace eats 2 characters instead of one if one special character is present (3 if there are 2; 4 if there are 3 etc.). 6. Hit return. Bash says it does not know the rubbish that you've actually typed (not the rubbish that was displayed). So obviously this is a display problem, not an input problem. Instead of step 4, you can also type some new rubbish. It will be inserted into the old rubbish exactly the way you type it, but it won't display correctly. It's like a blind flight: As long as you know exactly where you are, you'll land on the airport. But never try to tell your position from what you see... The bug is most probably not a duplicate of Bug #238055 or Bug #88504. The symptoms described there don't match ours here. Xubuntu 9.04, up to date as of July 15 2009. $ apt-cache policy gnome-terminal gnome-terminal: Installed: 2.26.0-0ubuntu2 Candidate: 2.26.0-0ubuntu2 Version table: *** 2.26.0-0ubuntu2 0 500 http://ch.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status $ apt-cache policy xfce4-terminal xfce4-terminal: Installed: 0.2.10-1ubuntu2 Candidate: 0.2.10-1ubuntu2 Version table: *** 0.2.10-1ubuntu2 0 500 http://ch.archive.ubuntu.com jaunty/universe Packages 100 /var/lib/dpkg/status ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: xfce4-terminal 0.2.10-1ubuntu2 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-terminal Uname: Linux 2.6.28-11-generic i686 WORKAROUND: 1. The correct text can be displayed by hitting the up and then the down cursor button. 2. The bug is triggered by special characters in what comes before the $ sign. If those special characters are removed from the prompt, the terminal acts correctly. Please see comments #9 and #10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/378668/+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 1360005] Re: Cyrillic symbols looks strange when using autocompletion
Egmont Koblinger, tried xterm and rxvt-unicode - problem remains. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1360005 Title: Cyrillic symbols looks strange when using autocompletion Status in “bash-completion” package in Ubuntu: New Status in “gnome-terminal” package in Ubuntu: Confirmed Bug description: You need use autocompletion (via TAB button) to folder/file/etc to cyrillic symbols and at least one space in its name to reproduce this bug. Then symbols in name look strange, but your command works correct. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-terminal 3.6.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 22 02:52:51 2014 ExecutablePath: /usr/bin/gnome-terminal InstallationDate: Installed on 2014-06-01 (81 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) ProcEnviron: PATH=(custom, no user) LANGUAGE=ru XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1360005/+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 1296378] Re: Activate VP9 codec in libav
That's true : Utopic now ships with libav-tools version 6:11~beta1-2, that is able to encode with VP9 codec inside a WebM container. Great! For those using Trusty, there are a few ways to encode with VP9 anyway (without upgrading to Utopic or running it inside a virtual machine) : - compile libav 11 beta 1 under Trusty - use Utopic libraries inside a Docker container I explained these 2 options in http://blog.mossroy.fr/2014/09/03/encoder-des-videos-avec-le-codec-vp9-sur-ubuntu-trusty-en-utilisant-libav-et-docker/ (in French) , with some generated videos and comparisons with VP8 - it's certainly also possible to upgrade libav with a PPA, but I did not want to "pollute" my OS (some programs that depend on libav might be broken) Thanks for the upgrade in Utopic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1296378 Title: Activate VP9 codec in libav Status in “libav” package in Ubuntu: Fix Released Bug description: "avconv -encoders | grep vp" gives only : V... libvpx libvpx VP8 (codec vp8) It does not give the encoder libvpx-vp9, which seems to be necessary to encode with VP9. Or maybe I missed something? Based on http://git.libav.org/?p=libav.git;a=commit;h=9aa053ceded5550b2e538578af383fd89d82364c , VP9 is available in libvpx since version 1.3.0 , which is the version libav is built with : http://packages.ubuntu.com/trusty/libvpx1 VP9 is also mentioned in the changelog of the libvpx1 package : http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvpx/libvpx_1.3.0-2/changelog Same issue when trying to read a file with VP9 codec. I tried with http://base-n.de/webm/out9.webm "avplay out9.webm" gives : [matroska,webm @ 0x7f1a80005be0] Unknown/unsupported AVCodecID V_VP9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1296378/+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 1366389] Re: compiz crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1366351 *** https://bugs.launchpad.net/bugs/1366351 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1366351, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1366389/+attachment/4197303/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1366389/+attachment/4197317/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1366389/+attachment/4197319/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1366389/+attachment/4197320/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1366389/+attachment/4197321/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1366389/+attachment/4197322/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1366351 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1366389 Title: compiz crashed with SIGSEGV in g_closure_invoke() Status in “compiz” package in Ubuntu: New Bug description: compiz crashed with SIGSEGV in g_closure_invoke() ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Sep 6 20:13:04 2014 Disassembly: => 0x0: Cannot access memory at address 0x0 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: fglrx-updates, 13.350.1, 3.16.0-13-generic, x86_64: installed ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller]) Subsystem: Dell Mobility Radeon HD 5650 [1028:0447] InstallationDate: Installed on 2014-09-06 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140905) MachineType: Dell Inc. Inspiron N5010 ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=7e738a7d-d136-415a-8e34-911b2f4181ce ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x0: Cannot access memory at address 0x0 PC (0x) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: compiz StacktraceTop: ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: compiz crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YXXJJ dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn0YXXJJ:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-x
[Desktop-packages] [Bug 614369] Re: Unable to remove keyboard switcher from gnome-panel
This is a support request. ** Summary changed: - Unable to remove kayboard switcher from gnome-panel + Unable to remove keyboard switcher from gnome-panel ** Description changed: - I'm unable (I don't know how) to remove kayboard switcher from gnome- - panel. I just upgraded to latest ubuntu, I never used this keyboard + I'm unable (I don't know how) to remove keyboard switcher from gnome- + panel. I just upgraded to latest Ubuntu, I never used this keyboard switcher and it suddenly appeared in my notification area. I can't remove it because it's not an applet, and I don't know how to get rid of it. pgrep-ing for some random keyboard related terms gave no results. How are users supposed to get rid of it if they want to? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gkbd-capplet (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Aug 6 16:10:03 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: - LANG=en_US.utf8 - SHELL=/bin/bash + LANG=en_US.utf8 + SHELL=/bin/bash SourcePackage: libgnomekbd ** Changed in: libgnomekbd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomekbd in Ubuntu. https://bugs.launchpad.net/bugs/614369 Title: Unable to remove keyboard switcher from gnome-panel Status in “libgnomekbd” package in Ubuntu: Invalid Bug description: I'm unable (I don't know how) to remove keyboard switcher from gnome- panel. I just upgraded to latest Ubuntu, I never used this keyboard switcher and it suddenly appeared in my notification area. I can't remove it because it's not an applet, and I don't know how to get rid of it. pgrep-ing for some random keyboard related terms gave no results. How are users supposed to get rid of it if they want to? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: gkbd-capplet (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Fri Aug 6 16:10:03 2010 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: libgnomekbd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomekbd/+bug/614369/+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 1366385] [NEW] libgnome-control-center1 should be a conditional dependency
Public bug reported: I use unity-control-center instead of gnome-control-center, but activity-log-manager depends on libgnome-control-center1 and forces me to install a package I don't need. The dependency should instead be libunity-control-center1 (>= 14.04.0) | libgnome-control-center1 (>= 1:2.91.2) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: activity-log-manager 0.9.7-0ubuntu14 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 15:01:17 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-01 (674 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: activity-log-manager UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago) ** Affects: activity-log-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to activity-log-manager in Ubuntu. https://bugs.launchpad.net/bugs/1366385 Title: libgnome-control-center1 should be a conditional dependency Status in “activity-log-manager” package in Ubuntu: New Bug description: I use unity-control-center instead of gnome-control-center, but activity-log-manager depends on libgnome-control-center1 and forces me to install a package I don't need. The dependency should instead be libunity-control-center1 (>= 14.04.0) | libgnome-control-center1 (>= 1:2.91.2) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: activity-log-manager 0.9.7-0ubuntu14 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 15:01:17 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2012-11-01 (674 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) SourcePackage: activity-log-manager UpgradeStatus: Upgraded to trusty on 2014-09-04 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activity-log-manager/+bug/1366385/+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 1365695] Re: No longer able to use GUI after update
Also until bug is solved I suggest to lock ubuntu-drivers-common upgrade by: sudo echo “ubuntu-drivers-common hold” | sudo dpkg –set-selections -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Confirmed Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1365695] Re: No longer able to use GUI after update
I have identified this bug after many tries upgrading and downgrading packages. ---TEMPORARY SOLUTION--- The issue does not happen if 1)I purge nvidia drivers OR if I downgrade to 2) sudo apt-get install ubuntu-drivers-common=1:0.2.91.4 ** Also affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-331 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-304-updates in Ubuntu. https://bugs.launchpad.net/bugs/1365695 Title: No longer able to use GUI after update Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Confirmed Bug description: Until yesterday the 14.04 install on this Thinkpad T530 (nvidia Optimus) with nvidia-331 drivers worked just fine, including excellent multi-monitor behavior. Yesterday the set of packages below [1] was updated. I shut down, booted this morning and found out that I was not shown the lightdm login screen: I was stuck at the purple screen that precedes it (into which I enter my disk encryption password). Now the funny thing is that I could hear the lightdm startup sound and could actually login by typing my password (disk activity and started processes verify I am actually logged in), but I can't see anything: I'm still stuck at the puple screen. Uninstalling the nvidia drivers solved the problem: I'm typing this in a browser window using the nouveau drivers. I atttempted switching to nvidia-304, but that doesn't work either. Using those drivers I am shown the lightdm login screen, but after logging in I'm stuck with a screen showing only the background image. Nothing else is available, no keyboard or mouse trickery will reveal any menu, dialog or terminal to gain access. Since nouveau doesn't support a multi-monitor setup, it would be great if I someone could tell me how to get the nvidia drivers working again. Some things I noticed: - .xsession-errors reported 'Xlib: extension "GLX" missing on display ":0"' - /var/log/Xorg.0.log reported 'setversion 1.4 failed: Permission denied' [1] The packages that were updated: Start-Date: 2014-09-03 15:07:38 Upgrade: libsystemd-login0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), systemd-services:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librbd1:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), ubuntu-drivers-common:amd64 (0.2.91.5, 0.2.91.6), libsystemd-daemon0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libgudev-1.0-0:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), libpam-systemd:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), librados2:amd64 (0.80.1-0ubuntu1.1, 0.80.5-0ubuntu0.14.04.1), shotwell-common:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), udev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), shotwell:amd64 (0.18.0-0ubuntu4.1, 0.18.0-0ubuntu4.2), gir1.2-gudev-1.0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev-dev:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), libudev1:i386 (204-5ubuntu20.4, 204-5ubuntu20.5), xserver-xorg-video-intel:amd64 (2.99.910-0ubuntu1, 2.99.910-0ubuntu1.1), libsystemd-journal0:amd64 (204-5ubuntu20.4, 204-5ubuntu20.5), rsyslog:amd64 (7.4.4-1ubuntu2, 7.4.4-1ubuntu2.1) End-Date: 2014-09-03 15:08:06 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nvidia-current-updates (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 4 22:07:11 2014 SourcePackage: nvidia-graphics-drivers-304-updates UpgradeStatus: Upgraded to trusty on 2014-06-03 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304-updates/+bug/1365695/+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 1309145] Re: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE)
Fixed for me in Version 37.0.2062.94 Ubuntu 14.04 (290621) (64-bit), can anyone confirm? -- 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/1309145 Title: Chromium 34 and 36 ignores ComposeKey (with xim GTK_IM_MODULE) Status in Chromium Browser: Unknown Status in “chromium-browser” package in Ubuntu: Incomplete Bug description: When entering the key combination AltGr + [ a in any text input field or address bar, it does not translate to ä (a umlaut) anymore. This worked in the "pre-aura" Chromium 33. --- Ubuntu 14.04 UK International Keyboard $ echo $GTK_IM_MODULE xim Chromium 34.0.1847.116 (Developer Build 260972) Ubuntu 14.04 aura OSLinux Blink 537.36 (@170605) JavaScriptV8 3.24.35.22 Flash 13.0.0.182 User AgentMozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/34.0.1847.116 Chrome/34.0.1847.116 Safari/537.36 Command Line /usr/lib/chromium-browser/chromium-browser --ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so --ppapi-flash-version=13.0.0.182 --enable-pinch --flag-switches-begin --enable-experimental-extension-apis --flag-switches-end (See also https://code.google.com/p/chromium/issues/detail?id=351230) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1309145/+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 1296378] Re: Activate VP9 codec in libav
@mossroy: You should be able to also encode in vp9 now in utopic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1296378 Title: Activate VP9 codec in libav Status in “libav” package in Ubuntu: Fix Released Bug description: "avconv -encoders | grep vp" gives only : V... libvpx libvpx VP8 (codec vp8) It does not give the encoder libvpx-vp9, which seems to be necessary to encode with VP9. Or maybe I missed something? Based on http://git.libav.org/?p=libav.git;a=commit;h=9aa053ceded5550b2e538578af383fd89d82364c , VP9 is available in libvpx since version 1.3.0 , which is the version libav is built with : http://packages.ubuntu.com/trusty/libvpx1 VP9 is also mentioned in the changelog of the libvpx1 package : http://changelogs.ubuntu.com/changelogs/pool/main/libv/libvpx/libvpx_1.3.0-2/changelog Same issue when trying to read a file with VP9 codec. I tried with http://base-n.de/webm/out9.webm "avplay out9.webm" gives : [matroska,webm @ 0x7f1a80005be0] Unknown/unsupported AVCodecID V_VP9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1296378/+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 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Could you rebuild pcsc-lite and libccid yourself and install them in /usr/local/ or somewhere else to try to debug the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes2 Transfer TypeBulk Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes2 Transfer TypeBulk Synch Type
[Desktop-packages] [Bug 1366381] [NEW] Importing ICC color profile fails: "failed to get imported profile: The profile was not added in time"
Public bug reported: Steps to reproduce: 1) Run the command "unity-control-center color" in a terminal, to open the Color profile management dialog 2) Click "Add profile" 3) Select "Other profile..." from the drop down list 4) Select the ICC color profile attached to this bug report 5) Click Add Wait a couple of seconds, and the following line should appear in the terminal: (unity-control-center:20636): color-cc-panel-WARNING **: failed to get imported profile: The profile was not added in time This is the complete command line output: rune@pc:~$ unity-control-center color (unity-control-center:24164): color-cc-panel-WARNING **: failed to get the active profile (unity-control-center:24164): color-cc-panel-WARNING **: failed to get imported profile: The profile was not added in time ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 20:17:30 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-09 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ** Attachment added: "Color profile in question" https://bugs.launchpad.net/bugs/1366381/+attachment/4197265/+files/benq-bl2400.icc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1366381 Title: Importing ICC color profile fails: "failed to get imported profile: The profile was not added in time" Status in “unity-control-center” package in Ubuntu: New Bug description: Steps to reproduce: 1) Run the command "unity-control-center color" in a terminal, to open the Color profile management dialog 2) Click "Add profile" 3) Select "Other profile..." from the drop down list 4) Select the ICC color profile attached to this bug report 5) Click Add Wait a couple of seconds, and the following line should appear in the terminal: (unity-control-center:20636): color-cc-panel-WARNING **: failed to get imported profile: The profile was not added in time This is the complete command line output: rune@pc:~$ unity-control-center color (unity-control-center:24164): color-cc-panel-WARNING **: failed to get the active profile (unity-control-center:24164): color-cc-panel-WARNING **: failed to get imported profile: The profile was not added in time ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Sep 6 20:17:30 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-04-09 (150 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140409) SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1366381/+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 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Hi, I fear that that the backtrace will be rather disappointing, as the gdb doesn't find any symbols for the pcscd-binary. Now the odd thing is, if you start the gdb if you then remove the card-reader for the first time, it doesn't crash. It is only the second time when the read is removed that the application crashes. As there are no symbols, you get only the addresses in the backtrace. If the gdb starts its notifies me that already another instance of pcscd is running. If you look at the green led of the reader, it goes out just before ubuntu-login-screen pops up. If you remove the reader and plug the reader back in, the green led goes on for a second or two and then goes back out. ** Attachment added: "LogGdbVascoReader.txt" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4197264/+files/LogGdbVascoReader.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Da
[Desktop-packages] [Bug 1366380] Re: telepathy-mission-control is trying to open weird files on startup
More about this bug http://askubuntu.com/questions/490690/how-to-fix- apparmor-denied-for-telepathy-mission-control-5-under-ubuntu-14-04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1366380 Title: telepathy-mission-control is trying to open weird files on startup Status in “telepathy-mission-control-5” package in Ubuntu: New Bug description: Upon startup I'm getting a notice that an error occured. When I check the syslog I see errors like: Sep 6 19:57:22 Earth kernel: [ 86.045357] type=1400 audit(1410026242.433:76): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="rw" denied_mask="rw" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.045707] type=1400 audit(1410026242.433:77): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.050493] type=1400 audit(1410026242.437:78): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.108894] type=1400 audit(1410026242.497:79): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 According to http://askubuntu.com/questions/410808/what-is-reason-for- apparmor-denied-operation-open, telepathy-mission-control-5 is trying to open a file it has no access to. However, the "name" part is completely rubbish. How can check what file telepathy is actually trying to open? How do I fix that? I am on Ubuntu 14.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1366380/+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 1366380] [NEW] telepathy-mission-control is trying to open weird files on startup
Public bug reported: Upon startup I'm getting a notice that an error occured. When I check the syslog I see errors like: Sep 6 19:57:22 Earth kernel: [ 86.045357] type=1400 audit(1410026242.433:76): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="rw" denied_mask="rw" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.045707] type=1400 audit(1410026242.433:77): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.050493] type=1400 audit(1410026242.437:78): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.108894] type=1400 audit(1410026242.497:79): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 According to http://askubuntu.com/questions/410808/what-is-reason-for- apparmor-denied-operation-open, telepathy-mission-control-5 is trying to open a file it has no access to. However, the "name" part is completely rubbish. How can check what file telepathy is actually trying to open? How do I fix that? I am on Ubuntu 14.04 LTS. ** Affects: telepathy-mission-control-5 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu. https://bugs.launchpad.net/bugs/1366380 Title: telepathy-mission-control is trying to open weird files on startup Status in “telepathy-mission-control-5” package in Ubuntu: New Bug description: Upon startup I'm getting a notice that an error occured. When I check the syslog I see errors like: Sep 6 19:57:22 Earth kernel: [ 86.045357] type=1400 audit(1410026242.433:76): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="rw" denied_mask="rw" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.045707] type=1400 audit(1410026242.433:77): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F6C69626163636F756E74732D676C69622F6163636F756E74732E6462 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.050493] type=1400 audit(1410026242.437:78): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E636F6E6669672F64636F6E662F75736572 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 Sep 6 19:57:22 Earth kernel: [ 86.108894] type=1400 audit(1410026242.497:79): apparmor="DENIED" operation="open" profile="/usr/lib/telepathy/mission-control-5" name=2F6D656469612F53746F726167652F50726F66696C652F5562756E74752031342E30342F6C6F6F7374726F2F2E6C6F63616C2F73686172652F74656C6570617468792F6D697373696F6E2D636F6E74726F6C2F6163636F756E74732E636667 pid=3007 comm="mission-control" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 According to http://askubuntu.com/questions/410808/what-is-reason-for- apparmor-denied-operation-open, telepathy-mission-control-5 is trying to open a file it has no access to. However, the "name" part is completely rubbish. How can check what file telepathy is actually trying to open? How do I fix that? I am on Ubuntu 14.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1366380/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1366206] Re: Graphical desktop not starting from livesession
Booted usb to hardware and installed - not present there at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1366206 Title: Graphical desktop not starting from livesession Status in “lightdm” package in Ubuntu: New Bug description: Boot live session - choose Try Same issue with at least Xubuntu,Ubuntu and Lubuntu No desktop, black screen - change to vt1 - run loginctl show-seat seat0 gives CanGraphical=no run startx and desktop boots this is in a vm on a machine using nvidia card and 331-updates appears similar to lp:1365336 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CasperVersion: 1.343 Date: Fri Sep 5 21:40:54 2014 LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140905.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1366206/+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 1342675] Re: Random characters in screen text suddenly disappear
Great. If you don't mind me asking how I can get this fix? I've checked my package version and it's still on 2.99.910 -- 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/1342675 Title: Random characters in screen text suddenly disappear Status in “xserver-xorg-video-intel” package in Ubuntu: Fix Committed Bug description: While using my machine, characters suddenly disappear. No character in particular, not in any single application in particular, and copying and pasting the text preserves the characters. Scrolling the text out of view and back into view doesn't affect the missing characters. Switching between applications may change the affected characters (possibly due to a redraw operation?) Restarting often solves the problem, but it comes back after a couple of hours working. I've attached a screenshot to show you the problem. I do believe this is different than the bug relating to garbled characters in a number of ways 1. I don't ever get garbled characters 2. Scrolling out/in of the affected text doesn't re-show the missing characters, even navigating inside the application has no effect. 3. It's global, I can even see it on Desktop icon names ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 16 14:48:25 2014 DistUpgraded: 2014-06-29 16:38:35,552 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.11.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: LG Electronics, Inc. Device [1854:0803] InstallationDate: Installed on 2014-03-28 (109 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LG Electronics R590-G.ARIBE8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=79c2f2b5-87cb-44d0-83fa-d99e73bb0a73 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: Upgraded to trusty on 2014-06-29 (16 days ago) dmi.bios.date: 01/06/2010 dmi.bios.vendor: INSYDE dmi.bios.version: QL4L3I51 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrQL4L3I51:bd01/06/2010:svnLGElectronics:pnR590-G.ARIBE8:pvr05:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: R590-G.ARIBE8 dmi.product.version: 05 dmi.sys.vendor: LG Electronics version.compiz: compiz 1:0.9.11.1+14.04.20140701-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Jul 16 01:52:06 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 560 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1342675/+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 1313459] Re: Screen corruption with Radeon 6670
Is this still occurring with recent updates? ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1313459 Title: Screen corruption with Radeon 6670 Status in “xserver-xorg-video-ati” package in Ubuntu: Incomplete Bug description: Unfortunately I have no reliable way of reproducing this issue, but it seems that after some time of using Ubuntu (especially when browsing websites with firefox) the graphics are getting corrupted. It starts with some small artifacts (single lines and pixels) and all of the sudden the entire screen is full of artifacts and the OS is basically unusable at this state. Coincidentally, I've had this problem with Arch Linux before. I was able to fix it, by setting the power profile of the GPU to "mid" or "high" as described here: https://wiki.archlinux.org/index.php/ATI#Profile-based_frequency_switching So to me it seems like this might be related to power management. Doing some more testing with Ubuntu, I was able to fix the corruption when switching the profile to mid and then logging out and in again. Leaving the profile at default did not fix the issue after re-login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity CurrentDmesg: [ 16.420258] init: plymouth-upstart-bridge main process ended, respawning [ 42.046534] audit_printk_skb: 123 callbacks suppressed [ 42.046536] type=1400 audit(1398637834.876:68): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2158 comm="apparmor_parser" [ 42.046541] type=1400 audit(1398637834.876:69): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2158 comm="apparmor_parser" [ 42.046831] type=1400 audit(1398637834.876:70): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2158 comm="apparmor_parser" Date: Mon Apr 28 00:32:39 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670] [1002:6758] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e198] InstallationDate: Installed on 2014-04-27 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=71941913-ad5f-4bba-8378-81cbf78bd8d2 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-ati UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd07/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Apr 28 00:30:08 2014 xserver.configfile: default xserver.
[Desktop-packages] [Bug 573640] Re: mixed rtsp and http playlist does not play in totem
Is this still occurring on Ubuntu 14.04 "Trusty Tahr"? ** Changed in: totem (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/573640 Title: mixed rtsp and http playlist does not play in totem Status in “totem” package in Ubuntu: Incomplete Bug description: Binary package hint: totem Totem can not open the online radio in this link: http://cluster.quantumart.ru/broadcast/default.aspx?media=rusradio The playlist at this location contains both rtsp and http streams. The rtsp streams fail to play directly in any player I have tried (totem, mplayer and vlc). The rtsp stream appears first in the playlist. vlc seems to skip the streams it can't play, but totem just throws an error on the first stream and gives up: ** Message: Error: Could not read from resource. gstrtspsrc.c(3847): gst_rtspsrc_try_send (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin1/GstRTSPSrc:source: Could not receive message. (Timeout while waiting for server response) ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: libgstreamer0.10-0 0.10.28-1 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic Uname: Linux 2.6.31-14-generic i686 Architecture: i386 Date: Sun May 2 14:30:36 2010 InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta i386 (20100318) ProcEnviron: LANG=nl_BE.utf8 SHELL=/bin/bash SourcePackage: gstreamer0.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/573640/+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 1366378] [NEW] crash in cogl_object_unref
Public bug reported: I know of #955356 and this happens with a much newer version. This happens when I use python with libcogl to display a very large window. See attached file for gdb info. % lsb_release -rd Description:Ubuntu 14.04.1 LTS Release:14.04 % apt-cache policy libcogl15 libcogl15: Installiert: 1.16.2-1 Installationskandidat: 1.16.2-1 Versionstabelle: *** 1.16.2-1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: cogl (Ubuntu) Importance: Undecided Status: New ** Attachment added: "gdb info about the two frames above the crash" https://bugs.launchpad.net/bugs/1366378/+attachment/4197262/+files/gdb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cogl in Ubuntu. https://bugs.launchpad.net/bugs/1366378 Title: crash in cogl_object_unref Status in “cogl” package in Ubuntu: New Bug description: I know of #955356 and this happens with a much newer version. This happens when I use python with libcogl to display a very large window. See attached file for gdb info. % lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 % apt-cache policy libcogl15 libcogl15: Installiert: 1.16.2-1 Installationskandidat: 1.16.2-1 Versionstabelle: *** 1.16.2-1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1366378/+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 1364196] Re: system-config-printer.py crashed with NameError in __lt__(): name 'lt' is not defined
This bug was fixed in the package system-config-printer - 1.5.1+20140906-0ubuntu1 --- system-config-printer (1.5.1+20140906-0ubuntu1) utopic; urgency=medium * New upstream bug fix release o GIT 1.5.x snapshot from 6 September 2014 o StateReason: Fixed __cmp__ conversion to rich comparisons (LP: #1364196) o This release has some Python3 fixes, as well as some fixes to udev-configure-printer and a fix for a D-Bus service hang. o In the 1.5.1 upstream release scp-dbus-service crashes immediately after starting. This is fixed in this snapshot. * debian/patches/33_ipp-over-usb-support.patch: Bug fix update of the patch from Daniel Dressler. * debian/patchs/30_scp-dbus-service-driver-download-hang-fixes.patch: Updated to apply to current source code. -- Till KamppeterSat, 06 Sep 2014 14:27:59 +0200 ** Changed in: system-config-printer (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1364196 Title: system-config-printer.py crashed with NameError in __lt__(): name 'lt' is not defined Status in “system-config-printer” package in Ubuntu: Fix Released Bug description: While attempting to check the printer queue after sending a print job to the printer the printer applet crashed. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: system-config-printer-gnome 1.5.0+20140805-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CupsErrorLog: E [01/Sep/2014:19:02:55 -0700] [Job 3] The printer is not responding. E [01/Sep/2014:19:03:28 -0700] [Job 3] The printer is not responding. E [01/Sep/2014:19:04:01 -0700] [Job 3] The printer is not responding. E [01/Sep/2014:19:04:34 -0700] [Job 3] The printer is not responding. CurrentDesktop: Unity Date: Mon Sep 1 19:04:01 2014 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2014-08-05 (27 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 Lpstat: device for Brother-HL-5250DN: socket://192.168.0.100:9100 MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: all Papersize: letter PpdFiles: Brother-HL-5250DN: Brother HL-5250DN BR-Script3 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic root=UUID=2a23588b-e7cb-4295-b314-23978b964b34 ro quiet splash init=/lib/systemd/systemd PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py'] SourcePackage: system-config-printer Title: system-config-printer.py crashed with NameError in __lt__(): name 'lt' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 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:bvnAmericanMegatrendsInc.:bvr2201:bd12/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1364196/+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 1364196] Re: system-config-printer.py crashed with NameError in __lt__(): name 'lt' is not defined
** Branch linked: lp:ubuntu/utopic-proposed/system-config-printer -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1364196 Title: system-config-printer.py crashed with NameError in __lt__(): name 'lt' is not defined Status in “system-config-printer” package in Ubuntu: New Bug description: While attempting to check the printer queue after sending a print job to the printer the printer applet crashed. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: system-config-printer-gnome 1.5.0+20140805-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-11.16-generic 3.16.1 Uname: Linux 3.16.0-11-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CupsErrorLog: E [01/Sep/2014:19:02:55 -0700] [Job 3] The printer is not responding. E [01/Sep/2014:19:03:28 -0700] [Job 3] The printer is not responding. E [01/Sep/2014:19:04:01 -0700] [Job 3] The printer is not responding. E [01/Sep/2014:19:04:34 -0700] [Job 3] The printer is not responding. CurrentDesktop: Unity Date: Mon Sep 1 19:04:01 2014 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationDate: Installed on 2014-08-05 (27 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) InterpreterPath: /usr/bin/python3.4 Lpstat: device for Brother-HL-5250DN: socket://192.168.0.100:9100 MachineType: To be filled by O.E.M. To be filled by O.E.M. PackageArchitecture: all Papersize: letter PpdFiles: Brother-HL-5250DN: Brother HL-5250DN BR-Script3 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/system-config-printer.py ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-11-generic root=UUID=2a23588b-e7cb-4295-b314-23978b964b34 ro quiet splash init=/lib/systemd/systemd PythonArgs: ['/usr/share/system-config-printer/system-config-printer.py'] SourcePackage: system-config-printer Title: system-config-printer.py crashed with NameError in __lt__(): name 'lt' is not defined UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/10/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2201 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: 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:bvnAmericanMegatrendsInc.:bvr2201:bd12/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1364196/+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 956618]
Addition : some emails need to be accessed regularly, but have the same part before the @. Hence, i use the nickname or some free field of the email card in the adress book to as to state a unique nickname or keyword that differenciate each of these adress. Its good that all these fields are searched. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/956618 Title: Nickname not over-riding names in email address Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: New Bug description: From what I have read in the support forum the nickname should take priority in the search for an email address in the to: field. It does not appear to work any more. Example: One friend's address is Mark. The other is James. Both are in my address book with Mark entered as the nickname of m...@.com and James as nickname for james.m...@.com. If I type james in the To: field I get james.mark as a first entry in the list of available addresses. If I type mark I get the same address again, when I would prefer the first optional address to be m...@.com Reason it is needed: I am trying to avoid sending emails meant for m...@.com to James.mark because I do not notice in time that I have defaulted to the first entry in the list of available addresses. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 10.0.2+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20 Uname: Linux 3.0.0-16-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 BuildID: 20120216123548 Date: Fri Mar 16 00:31:06 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/956618/+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 956618]
I have a quite large email adress book : 525 "collected adresses" and 15000 "personnal adresses". My colleagues have a less large email adress book but both my thunderbird and my coworker's thunderbird is badly impacted with the new TB31 email autocompletion behaviour. - it sometimes does not lead to any result and leaves the typed begining of the email as is, without autocompleting it. Ex : when typing 'secret' and TAB, TB leaves 'secret' instead of completing to 'secretar...@domain.ext' - it sometimes require to type allmost the whole email before the autocompletion gives a result : we sometime have to type 'secretariat@' so as to get 'secretar...@domain.ext' - it sometimes leads to bad results. When typing 'secret' TB autocompletes to 'redact...@domain.ext' for some unknown reason (or because it got the same doamine name ) Please revert to previous satisfying behaviour or fix new behaviour !!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/956618 Title: Nickname not over-riding names in email address Status in Mozilla Thunderbird Mail and News: Confirmed Status in “thunderbird” package in Ubuntu: New Bug description: From what I have read in the support forum the nickname should take priority in the search for an email address in the to: field. It does not appear to work any more. Example: One friend's address is Mark. The other is James. Both are in my address book with Mark entered as the nickname of m...@.com and James as nickname for james.m...@.com. If I type james in the To: field I get james.mark as a first entry in the list of available addresses. If I type mark I get the same address again, when I would prefer the first optional address to be m...@.com Reason it is needed: I am trying to avoid sending emails meant for m...@.com to James.mark because I do not notice in time that I have defaulted to the first entry in the list of available addresses. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: thunderbird 10.0.2+build1-0ubuntu0.11.10.1 ProcVersionSignature: Ubuntu 3.0.0-16.29-generic-pae 3.0.20 Uname: Linux 3.0.0-16-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 BuildID: 20120216123548 Date: Fri Mar 16 00:31:06 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/956618/+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 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Changed in: vte Status: Unknown => New ** Changed in: vte Importance: Unknown => Medium -- 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/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in Gnome Virtual Terminal Emulator: New Status in “vte” package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1340687/+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 1366357] [NEW] Banshee freezes shortly (about 5–10s) between songs
Public bug reported: Two days ago, I made some small changes to my music library in Banshee, removing some songs, adding others, etc. But not on a large scale. Anyways, since then I have the problem that after every song (I'm playing a playlist, in shuffle mode) Banshee freezes for several seconds, the window graying out after a few of them, until playback resumes normally with the next song. The same upon initially starting playback and when skipping ahead to the next song. I activated --debug and got the following output when Banshee freezes: [5 Warn 18:24:58.416] Executed in 18321ms SELECT CoreTracks.Rating,CoreTracks.LastStreamError,CoreTracks.TrackID,CoreTracks.PrimarySourceID,CoreTracks.ArtistID,CoreTracks.AlbumID,CoreTracks.TagSetID,CoreTracks.MusicBrainzID,CoreTracks.MimeType,CoreTracks.FileSize,CoreTracks.FileModifiedStamp,CoreTracks.LastSyncedStamp,CoreTracks.Attributes,CoreTracks.Title,CoreTracks.TitleSort,CoreTracks.TrackNumber,CoreTracks.TrackCount,CoreTracks.Disc,CoreTracks.DiscCount,CoreTracks.Duration,CoreTracks.Year,CoreTracks.Genre,CoreTracks.Composer,CoreTracks.Conductor,CoreTracks.Grouping,CoreTracks.Copyright,CoreTracks.LicenseUri,CoreTracks.Comment,CoreTracks.BPM,CoreTracks.BitRate,CoreTracks.SampleRate,CoreTracks.BitsPerSample,CoreTracks.Score,CoreTracks.PlayCount,CoreTracks.SkipCount,CoreTracks.ExternalID,CoreTracks.LastPlayedStamp,CoreTracks.LastSkippedStamp,CoreTracks.DateAddedStamp,CoreTracks.DateUpdatedStamp,CoreTracks.Uri,CoreArtists.Name,CoreArtists.NameSort,CoreAlbums.Title,CoreAlbums.TitleSort,CoreAlbums.ArtistName,CoreAlbums.ArtistNameSort,CoreAlbums.IsCompilation,CoreAlbums.MusicBrainzID,CoreArtists.MusicBrainzID , OrderID, CoreCache.ItemID FROM CoreTracks,CoreArtists,CoreAlbums INNER JOIN CorePlaylistEntries ON CoreTracks.TrackID = CorePlaylistEntries.TrackID INNER JOIN CoreCache ON CorePlaylistEntries.EntryID = CoreCache.ItemID WHERE CoreCache.ModelID = 131 AND CoreArtists.ArtistID = CoreTracks.ArtistID AND CoreAlbums.AlbumID = CoreTracks.AlbumID AND 1=1 AND LastStreamError = 0 AND (LastPlayedStamp < 1410024153 OR LastPlayedStamp IS NULL) AND (LastSkippedStamp < 1410024153 OR LastSkippedStamp IS NULL) ORDER BY RANDOM () LIMIT 1 So, apparently, there is a really slow SQL query executed for finding out the next song. What I don't understand, though, is why this problem suddenly occurred, since I only added a few songs to that playlist – also, there are now only 365 songs in that list, so really nothing that should lead to such lags. Ubuntu version: Ubuntu 14.04.1 LTS Package version banshee: 2.9.0+really2.6.2-2ubuntu2.1 ** Affects: banshee (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to banshee in Ubuntu. https://bugs.launchpad.net/bugs/1366357 Title: Banshee freezes shortly (about 5–10s) between songs Status in “banshee” package in Ubuntu: New Bug description: Two days ago, I made some small changes to my music library in Banshee, removing some songs, adding others, etc. But not on a large scale. Anyways, since then I have the problem that after every song (I'm playing a playlist, in shuffle mode) Banshee freezes for several seconds, the window graying out after a few of them, until playback resumes normally with the next song. The same upon initially starting playback and when skipping ahead to the next song. I activated --debug and got the following output when Banshee freezes: [5 Warn 18:24:58.416] Executed in 18321ms SELECT CoreTracks.Rating,CoreTracks.LastStreamError,CoreTracks.TrackID,CoreTracks.PrimarySourceID,CoreTracks.ArtistID,CoreTracks.AlbumID,CoreTracks.TagSetID,CoreTracks.MusicBrainzID,CoreTracks.MimeType,CoreTracks.FileSize,CoreTracks.FileModifiedStamp,CoreTracks.LastSyncedStamp,CoreTracks.Attributes,CoreTracks.Title,CoreTracks.TitleSort,CoreTracks.TrackNumber,CoreTracks.TrackCount,CoreTracks.Disc,CoreTracks.DiscCount,CoreTracks.Duration,CoreTracks.Year,CoreTracks.Genre,CoreTracks.Composer,CoreTracks.Conductor,CoreTracks.Grouping,CoreTracks.Copyright,CoreTracks.LicenseUri,CoreTracks.Comment,CoreTracks.BPM,CoreTracks.BitRate,CoreTracks.SampleRate,CoreTracks.BitsPerSample,CoreTracks.Score,CoreTracks.PlayCount,CoreTracks.SkipCount,CoreTracks.ExternalID,CoreTracks.LastPlayedStamp,CoreTracks.LastSkippedStamp,CoreTracks.DateAddedStamp,CoreTracks.DateUpdatedStamp,CoreTracks.Uri,CoreArtists.Name,CoreArtists.NameSort,CoreAlbums.Title,CoreAlbums.TitleSort,CoreAlbums.ArtistName,CoreAlbums.ArtistNameSort,CoreAlbums.IsCompilation,CoreAlbums.MusicBrainzID,CoreArtists.MusicBrainzID , OrderID, CoreCache.ItemID FROM CoreTracks,CoreArtists
[Desktop-packages] [Bug 1173828] Re: extreme performance issue with raring
** Changed in: compiz (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1173828 Title: extreme performance issue with raring Status in “compiz” package in Ubuntu: Invalid Bug description: I've been running Raring since early beta on this system from a clean install. I just upgraded my system to the latest in raring-proposed just a little while ago and then needed to reboot for some reason. When I came back up into the Unity login I started noticing issues. After entering my password at the login prompt screen, I noticed that the screen went terribly pixelated for about 15 seconds. Then, once actually logged in, every new event on the screen is taking much much longer than it should. Basically, any window being opened or window element being changed (new tabs in browser, window menus, etc) it is taking a vidibly long amount of time to go through any transitions. Attempt to open a new window and you can see it studder to fade in from nothing to all there in about 4-5 steps where it should be coming right up. Same with any application. Then once the application is up and running you can go about your business just fine. The only exception seems to be with Totem (aka Video). In this case, the video studders constantly. Especially in sync with when any other windows are opened. Even just moving windows around on the screen is extremely studder-y. I'm not quite sure what might be causing this issue. I tried using the unity-tweak-tool to reset my unity settings, but that doesn't seem to have had any affect. Not sure what information would be pertinent for someone to traige this. My system consists of: CPU: AMD Athlon II X4 640 (amd64) MEM: 16G HDD: Crucial M4 256G Video: Radeon HD 4250 (on-board) w/1G dedicated Kenrel: linux-image-3.8.0-17-generic (I've also tried 3.8.0-19) Let me know how I can get this resolved... --- .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.12, 3.8.0-17-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] [1002:9715] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-04-22 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130411) MachineType: Gigabyte Technology Co., Ltd. GA-880GA-UD3H MarkForUpload: True Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=ebd44c6f-b757-4427-89e6-f8d95a212293 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-880GA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 27 22:36:28 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.
[Desktop-packages] [Bug 1366356] [NEW] the bug when loading it says error missing file
Public bug reported: during loading theres a problem it says error missing file clikc to continue ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Sun Sep 7 00:18:46 2014 DistUpgraded: 2014-08-22 07:13:20,302 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:2400] InstallationDate: Installed on 2012-11-12 (663 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: CLEVO CO. W24xCZ ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=2e0045c6-833e-4cc3-83c2-62cbba1def82 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-21 (15 days ago) dmi.bios.date: 08/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/30/2012:svnCLEVOCO.:pnW24xCZ:pvrNotApplicable:rvnCLEVOCO.:rnW24xCZ:rvrV3.0:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: W24xCZ dmi.product.version: Not Applicable dmi.sys.vendor: CLEVO CO. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sun Sep 7 00:08:40 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 901 vendor LGD xserver.version: 2:1.15.1-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty 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/1366356 Title: the bug when loading it says error missing file Status in “xorg” package in Ubuntu: New Bug description: during loading theres a problem it says error missing file clikc to continue ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.3 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: Sun Sep 7 00:18:46 2014 DistUpgraded: 2014-08-22 07:13:20,302 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:2400] InstallationDate: Installed on 2012-11-12 (663 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423) MachineType: CLEVO CO. W24xCZ ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-35-generic root=UUID=2e0045c6-833e-4cc3-83c2-62cbba1def82 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-08-21 (15 days ago) dmi.bios.date: 08/30/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W24xCZ dmi.board.vendor: CLEVO CO. dmi.board.version: V3.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type:
[Desktop-packages] [Bug 1340687] Re: Please replace current alternate screen scroll patch with the new one, making this scroll permanent
** Bug watch added: GNOME Bug Tracker #736196 https://bugzilla.gnome.org/show_bug.cgi?id=736196 ** Also affects: vte via https://bugzilla.gnome.org/show_bug.cgi?id=736196 Importance: Unknown Status: Unknown -- 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/1340687 Title: Please replace current alternate screen scroll patch with the new one, making this scroll permanent Status in Gnome Virtual Terminal Emulator: Unknown Status in “vte” package in Ubuntu: Confirmed Bug description: Dear maintainers, Please remove 93_add_alt_screen_scroll_toggle.patch and replace it with the new patch from the attachment. This patch adds support for DEC 1007 escape sequence, thus making the alternate screen scroll work always. After applying it, the corresponding patches with the calls to vte_terminal_set_alternate_screen_scroll function can be safely dropped from the terminal applications using GTK2-based vte (e.g. xfce4-terminal). The patch has been adapted from the upstream commit in VTE3 [1]. [1] https://git.gnome.org/browse/vte/commit/?id=9f8c1b88dcd880c2d9e78c93521ee755560a9275 To manage notifications about this bug go to: https://bugs.launchpad.net/vte/+bug/1340687/+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 882321] Re: ONDA MW503HSA 3g usb modem not working, with "open blocked by driver for more than 7 seconds" warning
Is this fixed in Ubuntu 14.04 "Trusty Tahr? ** Changed in: modemmanager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/882321 Title: ONDA MW503HSA 3g usb modem not working, with "open blocked by driver for more than 7 seconds" warning Status in “modemmanager” package in Ubuntu: Incomplete Bug description: The same 3g key worked in Natty and Maverick. Only appearent difference in the syslog in Oneiric is the "open blocked by driver for more than 7 seconds!" warning. Judging from a Fedora users' forum discussion it seems like it's the latest version of modemmanager causing this issue on similar hardware: http://www.fedoraonline.it/modules/newbb/viewtopic.php?viewmode=flat&topic_id=16200&forum=41 ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: modemmanager 0.5-1ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic i686 ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Thu Oct 27 01:02:22 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/882321/+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 806336] Re: nautilus crashed with SIGSEGV in __memcpy_sse2()
*** This bug is a duplicate of bug 805783 *** https://bugs.launchpad.net/bugs/805783 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- 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/806336 Title: nautilus crashed with SIGSEGV in __memcpy_sse2() Status in “nautilus” package in Ubuntu: Confirmed Bug description: I was happen in rename at the desktop folder. ProblemType: Crash DistroRelease: Ubuntu 11.10 Package: nautilus 1:3.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4 Uname: Linux 3.0-2-generic x86_64 Architecture: amd64 CrashCounter: 1 Date: Wed Jul 6 15:14:05 2011 ExecutablePath: /usr/bin/nautilus InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) ProcCmdline: nautilus -n ProcEnviron: LANGUAGE=ja_JP:en LANG=ja_JP.UTF-8 LC_MESSAGES=ja_JP.UTF-8 SHELL=/bin/zsh SegvAnalysis: Segfault happened at: 0x7fc2e6ddca76 <__memcpy_sse2+70>: mov (%rsi),%rcx PC (0x7fc2e6ddca76) ok source "(%rsi)" (0x) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: __memcpy_sse2 () at ../sysdeps/x86_64/multiarch/../memcpy.S:102 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in __memcpy_sse2() UpgradeStatus: Upgraded to oneiric on 2011-07-01 (5 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/806336/+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 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
I am affected by this problem too, running Ubuntu 14.04 64 bit. "dirty files" seem to cause this problem on 64 bit systems. I solved it on my system by decreasing the dirty files cache. This article explains it in detail: http://lonesysadmin.net/2013/12/22/better-linux-disk- caching-performance-vm-dirty_ratio/ -- 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/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in “nautilus” package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 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: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True 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/1208993/+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 886481] Re: cannot print after upgrade from natty to oneiric
Old bug, Ubuntu 11.10 no longer supported. Please open bug on supported release. ** Changed in: cups (Ubuntu) Status: New => Invalid -- 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/886481 Title: cannot print after upgrade from natty to oneiric Status in “cups” package in Ubuntu: Invalid Bug description: cannot print after upgrade from natty to oneiric ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cups 1.5.0-8ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 ApportVersion: 1.23-0ubuntu4 Architecture: i386 Date: Sat Nov 5 09:37:55 2011 MachineType: Dell Inc. Latitude D630 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcKernelCmdLine: root=UUID=4d92d0f2-fd56-438f-9952-f1e80de75c56 ro quiet splash SourcePackage: cups UpgradeStatus: Upgraded to oneiric on 2011-10-15 (20 days ago) dmi.bios.date: 01/04/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0KU184 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd01/04/2010:svnDellInc.:pnLatitudeD630:pvr:rvnDellInc.:rn0KU184:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D630 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/886481/+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 1066612] Re: skype [AOA150, Realtek ALC268, Mic, Internal] No sound at all
This is fixed in kernel 3.8. Ubuntu 14.04 "Trusty Tahr" is using the 3.13 kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1107477 ** Changed in: alsa-driver (Ubuntu) Status: New => Fix Released -- 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/1066612 Title: skype [AOA150, Realtek ALC268, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: Fix Released Bug description: acer aspireOne AOA150 - internal mic not works with skype. If you open the pulse audio sound settings -> go to the tab configuration -> set the sound to disabled and then to analoge stereo dublex again, the internal mic works for 3-5 seconds and then stops like to turn of a button. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: alsa-base 1.0.25+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicholas 1305 F xfce4-volumed nicholas 1317 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x5854 irq 45' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1025015b,00100101' Controls : 15 Simple ctrls : 8 Date: Mon Oct 15 02:04:02 2012 InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:Intel successful Symptom_Card: Ενσωματωμένος ήχος - HDA Intel Symptom_DevicesInUse: 1305 1317 nicholas F xfce4-volumed nicholas F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:Intel successful Symptom_Type: No sound at all Title: [AOA150, Realtek ALC268, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3114 dmi.board.asset.tag: Base Board Asset Tag dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrv0.3114:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: AOA150 dmi.product.version: 1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1066612/+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 1366206] Re: Graphical desktop not starting from livesession
Appears to only affect a virtual machine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1366206 Title: Graphical desktop not starting from livesession Status in “lightdm” package in Ubuntu: New Bug description: Boot live session - choose Try Same issue with at least Xubuntu,Ubuntu and Lubuntu No desktop, black screen - change to vt1 - run loginctl show-seat seat0 gives CanGraphical=no run startx and desktop boots this is in a vm on a machine using nvidia card and 331-updates appears similar to lp:1365336 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CasperVersion: 1.343 Date: Fri Sep 5 21:40:54 2014 LiveMediaBuild: Xubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140905.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1366206/+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 1293384] Re: Compiz CPU usage dramatically increased in Ubuntu 14.04
I assume this bug (or https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1268146 which sounds the same to me) is why I cannot use 14.04 on my (ancient) Dell Dimension 3000. It used to run 12.04 fine but with 14.04 it is unusably slow. Compiz runs at least 25% of the CPU when nothing is being done (other than System Monitor showing this). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1293384 Title: Compiz CPU usage dramatically increased in Ubuntu 14.04 Status in Compiz: Triaged Status in “compiz” package in Ubuntu: Triaged Bug description: It appears that the workload of low-level graphical operations used by compiz when, for example, moving windows has increased dramatically between Ubuntu 12.04 and Ubuntu 14.04. This might not be that visible when using high-end gpus, but should be clearly visible when using compiz on llvmpipe and to some-extent invalidates the approach of using compiz on top of llvmpipe as a fallback when no GPU is available: How to reproduce: 1) Use the unity-3d desktop in Ubuntu 14.04 on top of a non-accelerating Xorg driver like "modesetting". Move windows around. Note peak and average cpu-usage. How to verify compiz is the culprit: 1) copy /usr/bin/compiz from a Ubuntu 12.04 installation. Drop it in as /usr/bin/compiz on 14.04. Reboot. Perform the same window movement. CPU-usage should be substantially lower. This problem also affects VMs running on VMware ESX with a software- rendering GPU. Window movement becomes sluggish, which suggests that even with GPUs, compiz has increased the number of operations required to move windows. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1293384/+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 1366333] Re: Xorg crashed with SIGABRT
*** This bug is a duplicate of bug 1365176 *** https://bugs.launchpad.net/bugs/1365176 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1365176, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1366333/+attachment/4197057/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1366333/+attachment/4197060/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1366333/+attachment/4197071/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1366333/+attachment/4197073/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1366333/+attachment/4197074/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1366333/+attachment/4197075/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1366333/+attachment/4197076/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1365176 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1366333 Title: Xorg crashed with SIGABRT Status in “xorg-server” package in Ubuntu: New Bug description: Ubuntu release 14.10 beta, kernel version 3.16.0.13 Crashing at random times. I read somewhere it would be due to a kernelbug in kernel 3.16 and 3.17 Setting cma=0 as grub boot option should fix this ATM. So far it did not came back. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.15.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sat Sep 6 15:47:11 2014 DistUpgraded: 2014-08-28 19:58:26,552 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.14, 3.13.0-35-generic, x86_64: installed virtualbox, 4.3.14, 3.16.0-10-generic, x86_64: installed virtualbox, 4.3.14, 3.16.0-11-generic, x86_64: installed virtualbox, 4.3.14, 3.16.0-12-generic, x86_64: installed virtualbox, 4.3.14, 3.16.0-13-generic, x86_64: installed ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:3231] InstallationDate: Installed on 2014-02-08 (209 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140208) MachineType: System manufacturer System Product Name ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic root=UUID=cc642ca4-4994-4e85-b2c7-5268479e4f35 ro quiet splash cma=0 vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to utopic on 2014-08-28 (8 days ago) UserGroups: dmi.bios.date: 04/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3304 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V GEN3 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.:bvr3304:bd04/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VGEN3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.n
[Desktop-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
LogCardReader%40Powerup.txt indicates that the device is not responding correctly: 0024 -> 00 65 00 00 00 00 00 00 00 00 00 05000412 ccid_usb.c:751:WriteUSB() write failed (1/4): -7 Resource temporarily unavailable -7 is LIBUSB_ERROR_TIMEOUT So the device is not visible at the PC/SC level. I have no idea what is happening. I suspect a reader firmware bug. I do not see the pcscd crash in this log. Can you run pcscd inside gdb? $ gdb /usr/sbin/pcscd (gdb) set args -dfa (gdb) run remove the reader do make pcscd crash (gdb) backtrace Then send me the complete gdb trace. Thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1366152 Title: System crash when Vasco-card-reader is plugged in at powerup Status in “pcsc-lite” package in Ubuntu: New Bug description: I'm using VASCO Data Security International Digipass 905 SmartCard Reader which is working fine. However if the device is plugged in at power-up, the device isn't handled well. Although the device is in the ilisted usb-devices, pcsc-scan doesn't find the device at all (Which is normal as the green-led is going out after the kernel starts). If one tries to remove the card-reader, a system-crash happens. After that the pcscd-service seems to be halted : pcsc_scan PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau Compiled with PC/SC lite version: 1.8.10 SCardEstablishContext: Service not available. One can recover from this problem by 1. Unplugging the reader 2. Manually starting the service again by sudo service pcscd start 3. Plugging back the reader in (green led stays on, red led goes on when a card is put in) The bug is not related to a 64-bit architecture as it happens also with 32-bit machines. Info about the device Bus 001 Device 005: ID 1a44:0001 VASCO Data Security International Digipass 905 SmartCard Reader Couldn't open device, some information will be missing Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 1.10 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x1a44 VASCO Data Security International idProduct 0x0001 Digipass 905 SmartCard Reader bcdDevice1.02 iManufacturer 1 iProduct2 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 93 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 50mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass11 Chip/SmartCard bInterfaceSubClass 0 bInterfaceProtocol 0 iInterface 0 ChipCard Interface Descriptor: bLength54 bDescriptorType33 bcdCCID 1.00 nMaxSlotIndex 0 bVoltageSupport 3 5.0V 3.0V dwProtocols 3 T=0 T=1 dwDefaultClock 3700 dwMaxiumumClock 3700 bNumClockSupported 1 dwDataRate 9946 bps dwMaxDataRate 318280 bps bNumDataRatesSupp. 53 dwMaxIFSD 254 dwSyncProtocols 0007 2-wire 3-wire I2C dwMechanical dwFeatures 000404BE Auto configuration based on ATR Auto activation on insert Auto voltage selection Auto clock change Auto baud rate change Auto PPS made by CCID Auto IFSD exchange Short and extended APDU level exchange dwMaxCCIDMsgLen 272 bClassGetResponseecho bClassEnvelope echo wlcdLayout none bPINSupport 0 bMaxCCIDBusySlots 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 32 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes
[Desktop-packages] [Bug 1173828] Re: extreme performance issue with raring
I haven't got 13.04 installed any more, so I guess we can close this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1173828 Title: extreme performance issue with raring Status in “compiz” package in Ubuntu: Incomplete Bug description: I've been running Raring since early beta on this system from a clean install. I just upgraded my system to the latest in raring-proposed just a little while ago and then needed to reboot for some reason. When I came back up into the Unity login I started noticing issues. After entering my password at the login prompt screen, I noticed that the screen went terribly pixelated for about 15 seconds. Then, once actually logged in, every new event on the screen is taking much much longer than it should. Basically, any window being opened or window element being changed (new tabs in browser, window menus, etc) it is taking a vidibly long amount of time to go through any transitions. Attempt to open a new window and you can see it studder to fade in from nothing to all there in about 4-5 steps where it should be coming right up. Same with any application. Then once the application is up and running you can go about your business just fine. The only exception seems to be with Totem (aka Video). In this case, the video studders constantly. Especially in sync with when any other windows are opened. Even just moving windows around on the screen is extremely studder-y. I'm not quite sure what might be causing this issue. I tried using the unity-tweak-tool to reset my unity settings, but that doesn't seem to have had any affect. Not sure what information would be pertinent for someone to traige this. My system consists of: CPU: AMD Athlon II X4 640 (amd64) MEM: 16G HDD: Crucial M4 256G Video: Radeon HD 4250 (on-board) w/1G dedicated Kenrel: linux-image-3.8.0-17-generic (I've also tried 3.8.0-19) Let me know how I can get this resolved... --- .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.12, 3.8.0-17-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] [1002:9715] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-04-22 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130411) MachineType: Gigabyte Technology Co., Ltd. GA-880GA-UD3H MarkForUpload: True Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=ebd44c6f-b757-4427-89e6-f8d95a212293 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-880GA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Sat Apr 27 22:36:28 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xo
[Desktop-packages] [Bug 1358134] Re: Bluetooth unable to receive files from phone
I've found a workaround that is working for me: install Lubuntu Desktop Environment alongside Unity DE: [CODE] sudo apt-get install lubuntu-desktop [/CODE] My smartphone now not only pairs but connects to my PC; I can transfer photos from my phone to my PC now in both Unity and Lubuntu DE's. The bluetooth packages have the same versions in common in Lubuntu and Unity, but Unity has more bluetooth packages in addition. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1358134 Title: Bluetooth unable to receive files from phone Status in “unity-control-center” package in Ubuntu: New Bug description: Ubuntu 14.04.1 64-bit: Bluetooth will not receive photos or files from HTC Rezound running Android 4.0.3 OEM. I can browse files on the phone, but cannot use them (copy, transfer, etc.). If I attempt to transfer files from phone to PC, I get anOBEX error message. I also occasionally see an input/output error message. Bluetooth can send files to the phone. Lubuntu 14.04.1 running from Live-USB is able to send & receive files & photos successfully on the same hardware. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20140604-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 18 01:33:24 2014 EcryptfsInUse: Yes ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2014-08-09 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_unity-control-center: activity-log-manager 0.9.7-0ubuntu14 deja-dup 30.0-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1358134/+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 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware
If I either blacklist nouveau or remove the xserver-xorg-video-nouveau package then everything works as expected with the current xserver-xorg-video-intel package. This also *seems* to make restarts & shutdowns more reliable & makes going to a tty not be liable to cause some sort of looping kernel panic (happens about 40% of the time with nouveau package installed & not blacklisted So choices here on Haswell Mobile - Downgrade xserver-xorg-video-intel Blacklist nouveau Remove xserver-xorg-video-nouveau -- 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/1357746 Title: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware Status in Compiz: Invalid Status in Accelerated Xorg driver for nVidia cards: New Status in “unity” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Seen here with Haswell (Mobile) Logs into a session with black desktop no unity panel a non functional launcher Nothing can be done in the session except go to a tty If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then all is well & compiz loads as expected ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 16 12:29:42 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2014-08-16 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140813) MachineType: LENOVO 20217 ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-8-generic.efi.signed root=UUID=1696b1d2-76dc-4df4-bafc-65f8cd743e53 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 12:28:54 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 729 vendor LGD xserver.version: 2:1.15.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1357746/+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 1310489] Re: xorg.conf overwritten by booting system
@Abhijit: please download the attached file and type the following commands: cd path_to_the_downloaded_xorg_conf sudo mv -f xorg.conf /etc/X11/ Then restart your computer, see how it goes, and finally attach your /var/log/gpu-manager.log and /var/log/Xorg.0.log ** Attachment added: "xorg.conf" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4197036/+files/xorg.conf -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log pr
[Desktop-packages] [Bug 1357746] Re: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware
** Also affects: nouveau Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. Matching subscriptions: dp-unity https://bugs.launchpad.net/bugs/1357746 Title: Compiz fails to load with xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 on some Intel hardware Status in Compiz: Invalid Status in Accelerated Xorg driver for nVidia cards: New Status in “unity” package in Ubuntu: Invalid Status in “xserver-xorg-video-intel” package in Ubuntu: Confirmed Bug description: Seen here with Haswell (Mobile) Logs into a session with black desktop no unity panel a non functional launcher Nothing can be done in the session except go to a tty If I downgrade back to xserver-xorg-video-intel_2.99.910-0ubuntu1 then all is well & compiz loads as expected ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140811-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-8.13-generic 3.16.0 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Aug 16 12:29:42 2014 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3801] InstallationDate: Installed on 2014-08-16 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140813) MachineType: LENOVO 20217 ProcEnviron: SHELL=/bin/bash TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-8-generic.efi.signed root=UUID=1696b1d2-76dc-4df4-bafc-65f8cd743e53 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.5-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.5-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Aug 16 12:28:54 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 729 vendor LGD xserver.version: 2:1.15.1-0ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1357746/+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 1366317] Re: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace()
since the other bug isn't accessible, I am unlinking its dupe status ** This bug is no longer a duplicate of private bug 1299364 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/1366317 Title: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace() Status in “amarok” package in Ubuntu: New Bug description: while scanning the collection... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: amarok-utils 2:2.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Sat Sep 6 14:08:12 2014 ExecutablePath: /usr/bin/amarokcollectionscanner ExecutableTimestamp: 1380109713 ProcCmdline: /usr/bin/amarokcollectionscanner --idlepriority -r -s --sharedmemory AmarokScannerMemory{4fd94376-39ae-44d1-962f-edc38ff61d69} /media/mandree/VERBATIM_HD/Musik /home/mandree/Audiobooks /home/mandree/Musik /media/mandree/MA-WD-Elements/Musik ProcCwd: /home/mandree SegvAnalysis: Segfault happened at: 0x7fe7d8b90a7e <__memcpy_sse2_unaligned+46>: movdqu -0x10(%rsi,%rdx,1),%xmm8 PC (0x7fe7d8b90a7e) ok source "-0x10(%rsi,%rdx,1)" (0x10240778b) not located in a known VMA region (needed readable region)! destination "%xmm8" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: amarok StacktraceTop: TagLib::ByteVector::replace(TagLib::ByteVector const&, TagLib::ByteVector const&) () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const&) () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const&, TagLib::ID3v2::Header*) const () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::Tag::parse(TagLib::ByteVector const&) () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::Tag::read() () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 Title: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace() UpgradeStatus: Upgraded to trusty on 2014-08-29 (7 days ago) UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1366317/+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 1366317] Re: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace()
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1299364, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1366317/+attachment/4197012/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1366317/+attachment/4197014/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1366317/+attachment/4197016/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1366317/+attachment/4197017/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1366317/+attachment/4197018/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1366317/+attachment/4197019/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1366317/+attachment/4197021/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1299364 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to amarok in Ubuntu. https://bugs.launchpad.net/bugs/1366317 Title: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace() Status in “amarok” package in Ubuntu: New Bug description: while scanning the collection... ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: amarok-utils 2:2.8.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: KDE Date: Sat Sep 6 14:08:12 2014 ExecutablePath: /usr/bin/amarokcollectionscanner ExecutableTimestamp: 1380109713 ProcCmdline: /usr/bin/amarokcollectionscanner --idlepriority -r -s --sharedmemory AmarokScannerMemory{4fd94376-39ae-44d1-962f-edc38ff61d69} /media/mandree/VERBATIM_HD/Musik /home/mandree/Audiobooks /home/mandree/Musik /media/mandree/MA-WD-Elements/Musik ProcCwd: /home/mandree SegvAnalysis: Segfault happened at: 0x7fe7d8b90a7e <__memcpy_sse2_unaligned+46>: movdqu -0x10(%rsi,%rdx,1),%xmm8 PC (0x7fe7d8b90a7e) ok source "-0x10(%rsi,%rdx,1)" (0x10240778b) not located in a known VMA region (needed readable region)! destination "%xmm8" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: amarok StacktraceTop: TagLib::ByteVector::replace(TagLib::ByteVector const&, TagLib::ByteVector const&) () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::SynchData::decode(TagLib::ByteVector const&) () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::FrameFactory::createFrame(TagLib::ByteVector const&, TagLib::ID3v2::Header*) const () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::Tag::parse(TagLib::ByteVector const&) () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 TagLib::ID3v2::Tag::read() () from /tmp/apport_sandbox_X1US4m/usr/lib/x86_64-linux-gnu/libtag.so.1 Title: amarokcollectionscanner crashed with SIGSEGV in TagLib::ByteVector::replace() UpgradeStatus: Upgraded to trusty on 2014-08-29 (7 days ago) UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse libvirtd lpadmin netdev plugdev pulse sambashare saned tape vboxusers video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/1366317/+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 1280794] Re: Can't change default "Open with" application
With .mp4 can add another that will cause this - video/x-m4v So for example if a user sets Videos as default thru "Default Applications" then these 3 are entered in mimeapps.list video/mp4= video/mp4v-es= video/x-m4v= Nautilus only sets the first one so if the other 2 exist then the default for .mp4 cannot be altered thru nautilus until they are removed or edited to intended new default. Also if another player is set thru Default Applications & the above 3 are in mimeapps.list then the default for .mp4 will only be changed if that player has all 3 in it's .desktop's MimeType= line -- 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/1280794 Title: Can't change default "Open with" application Status in “nautilus” package in Ubuntu: Confirmed Bug description: I am on Ubuntu 13.10 using nautilus 1:3.8.2-0ubuntu2.2. I am trying to change default application to open .avi files. I right- click an .avi file select "Properties", go to "Open With". There is a default application there (banshee) and recommended (VLC media player). I select VLC media player and click "Set as default" button, selection jumps back to banshee, "Set as default" button disabled and nothing else happens. Nautilus still opens .avi files with banshee. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: nautilus 1:3.8.2-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sun Feb 16 21:45:45 2014 GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'1497x873+0+171'" InstallationDate: Installed on 2013-11-17 (91 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.xdg.autostart.nautilus.autostart.desktop: 2013-11-20T19:34:55.419627 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1280794/+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 838543] Re: False battery warning +suspend
Happens for me on 14.04 on a Dell XPS13 -- 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/838543 Title: False battery warning +suspend Status in “gnome-settings-daemon” package in Ubuntu: Confirmed Bug description: I pulled the plug on my laptop with it's battery full: ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/state present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 7200 mAh present voltage: 11100 mV ubuntu@ubuntu:~$ ubuntu-bug -w ubuntu@ubuntu:~$ cat /proc/acpi/battery/BAT1/info present: yes design capacity: 7200 mAh [...] And suddenly got a dialog saying that it was critically low (while the icon top-left appears, properly, as full) and the laptop did suspend shortly after that. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.5-0ubuntu4 ProcVersionSignature: Ubuntu 3.0.0-9.15-generic 3.0.3 Uname: Linux 3.0.0-9-generic x86_64 Architecture: amd64 CasperVersion: 1.280 Date: Thu Sep 1 02:26:17 2011 ExecutablePath: /usr/bin/gnome-control-center LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110831) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/838543/+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 201375] Re: [upstream] .doc header converted to .odt then .doc is removed
Jaak, thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in Trusty Tahr. This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: libreoffice (Ubuntu) Status: Triaged => Fix Released -- 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/201375 Title: [upstream] .doc header converted to .odt then .doc is removed Status in LibreOffice Productivity Suite: Confirmed Status in The OpenOffice.org Suite: Confirmed Status in “libreoffice” package in Ubuntu: Fix Released Status in “openoffice.org” package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/201375/+attachment/228294/+files/documents.tgz && file-roller -h documents.tgz && cd documents && unoconv --listener && unoconv -f odt Original.doc && cp Original.odt example.odt && unoconv -f doc example.odt && lowriter -nologo example.doc Original.doc is the example.doc and Original.doc look the same. 4) What happens instead is the header on page 2 is missing. Original.doc was created in MS Office. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/201375/+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 1310489] Re: xorg.conf overwritten by booting system
Hi Alberto Ok, here are all the files requested plus the gpu-manager.log after I redid everything once again from scratch. Its all there in the zip file. The original xorg.conf file is labelled as xorg.conf.orig and the output of dmesg is dmesg.out. Hope this helps. Thanks again for all the help. Abhijit ** Attachment added: "files.zip" https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4197010/+files/files.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1310489 Title: xorg.conf overwritten by booting system Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “ubuntu-drivers-common” source package in Trusty: Fix Committed Bug description: Description: Ubuntu 14.04 LTS Release: 14.04 == SRU Request == There is a regression in the gpu-manager that causes it to revert user changes right before the first reboot after enabling the fglrx driver or the nvidia driver on a system with hybrid graphics (Intel+AMD or Intel+NVIDIA). This causes the gpu-manager to remove the current xorg.conf and to switch to Mesa. [Impact] * This regression makes it almost impossible to use binary drivers on systems with hybrid graphics. [Test Case] * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. * Make sure that the gpu-manager is not disabled (only necessary if you disabled it manually). * Remove all fglrx and nvidia drivers (keep the nvidia-common and the nvidia-prime packages): sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove nvidia-331 sudo apt-get --purge remove fglrx sudo apt-get --purge remove fglrx-updates * Install ubuntu-drivers-common from trusty-proposed. * Restart the system. * Install the binary driver (either fglrx or nvidia, according to the available discrete GPU), reboot, and check that the binary driver is enabled (attach your /var/log/gpu-manager.log) - Expected: the (AMD or NVIDIA) discrete GPU is enabled. - Bad behavior: the system switches back to the intel driver and the discrete GPU is not used, despite the fact that the system was configured properly. [Regression Potential] * Low. Systems that currently work will keep working as usual, the ones that currently fail should finally work. [Other Info] * N/A - Hello, I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. After installing fglrx I generated the xorg.conf in the terminal with 'sudo aticonfig --adapter=all --initial' and it looked pretty good. Up to this point I was able to switch between the cards with the commands 'sudo aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for the intigrated card to save power. After rebooting I realized that I was no longer able to switch between the cards and found that the xorg.conf will be overwritten whenever I modified it and reboot the system. The new (by boot) generated xorg.conf contains not the relevant information for switing between the cards. I attached both configuration in one file (xorg.conf.comparison). I will also provide the atisysteminfo-report.txt so far I will find the place where to attach. Edit: I fixed the error --> "AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file or directory]" but it changed not the bug of overwriting the xorg.conf. Regards, Uwe ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Mon Apr 21 08:43:29 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G] [1002:990b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1985] Subsystem: Hewlett-Packard Company Device [103c:1985] InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=fdcb1eaf-eda9-48ee-9d5b-b44e1fc06687 ro quiet splash vt.handoff=7 SourcePa
[Desktop-packages] [Bug 1085704] Re: No HD7470 in catalyst control center [Asus X53B notebook]
phukariflux - are you still having this issue with Catalyst 13.1 or later? ** Changed in: fglrx-installer-updates (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer-updates in Ubuntu. https://bugs.launchpad.net/bugs/1085704 Title: No HD7470 in catalyst control center [Asus X53B notebook] Status in “fglrx-installer-updates” package in Ubuntu: Incomplete Bug description: I cannot switch to "high-performance" gpu because it is not shown in catalyst control center. I only got weaker, HD6320 gpu listed in there. Some command line magic does show that HD7470 exists: aticonfig --lsa * 0. 00:01.0 AMD Radeon HD 6320 Graphics 1. 01:00.0 AMD Radeon HD 7400M Series ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: fglrx-updates 2:9.000-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-19.30-generic 3.5.7 Uname: Linux 3.5.0-19-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu6 Architecture: amd64 Date: Sun Dec 2 21:32:02 2012 InstallationDate: Installed on 2012-11-28 (4 days ago) InstallationMedia: Xubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: fglrx-installer-updates UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1085704/+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 1363910] Re: GTK2 theme not loaded from ~/.local/share/themes
"That’s happening because GTK2 cannot read the Theme RC file from “~/.local/share/themes/” location." http://worldofgnome.org/gtk-theme-ing-issue-in-gnome-3-10/ ** Package changed: xfce4 (Ubuntu) => gtk+2.0 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1363910 Title: GTK2 theme not loaded from ~/.local/share/themes Status in “gtk+2.0” package in Ubuntu: New Bug description: In Xubuntu 13.10 I was able to load themes from ~/.local/share/themes. In Xubuntu 14.04 I can still load the GTK3 theme, but not the GTK2 theme. Workaround: Load the themes from ~/.themes. Downside: Cluttered home directory. How to reproduce: 1. Download a theme and put in in ~/.themes. 2. Open settings manager and a GTK3 app. (I used gedit.) 3. Apply the downloaded theme. So far everything should work. 4. Move the downloaded theme to ~/.local/share/themes. 5. Apply another theme and reapply the downloaded one. At this point only the GTK2 theme is loaded. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Sep 1 11:12:59 2014 SourcePackage: xfce4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1363910/+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 1173828] Re: extreme performance issue with raring
Yup, it sounds like you have/had a kernel DRM issue. Official support for Ubuntu 13.04 "Raring Ringtail" has ended. Does this issue still occur in Ubuntu 14.04 "Trusty Tahr"? ** Changed in: compiz (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to compiz in Ubuntu. https://bugs.launchpad.net/bugs/1173828 Title: extreme performance issue with raring Status in “compiz” package in Ubuntu: Incomplete Bug description: I've been running Raring since early beta on this system from a clean install. I just upgraded my system to the latest in raring-proposed just a little while ago and then needed to reboot for some reason. When I came back up into the Unity login I started noticing issues. After entering my password at the login prompt screen, I noticed that the screen went terribly pixelated for about 15 seconds. Then, once actually logged in, every new event on the screen is taking much much longer than it should. Basically, any window being opened or window element being changed (new tabs in browser, window menus, etc) it is taking a vidibly long amount of time to go through any transitions. Attempt to open a new window and you can see it studder to fade in from nothing to all there in about 4-5 steps where it should be coming right up. Same with any application. Then once the application is up and running you can go about your business just fine. The only exception seems to be with Totem (aka Video). In this case, the video studders constantly. Especially in sync with when any other windows are opened. Even just moving windows around on the screen is extremely studder-y. I'm not quite sure what might be causing this issue. I tried using the unity-tweak-tool to reset my unity settings, but that doesn't seem to have had any affect. Not sure what information would be pertinent for someone to traige this. My system consists of: CPU: AMD Athlon II X4 640 (amd64) MEM: 16G HDD: Crucial M4 256G Video: Radeon HD 4250 (on-board) w/1G dedicated Kenrel: linux-image-3.8.0-17-generic (I've also tried 3.8.0-19) Let me know how I can get this resolved... --- .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true DistUpgraded: Fresh install DistroCodename: raring DistroRelease: Ubuntu 13.04 DistroVariant: ubuntu DkmsStatus: vboxhost, 4.2.12, 3.8.0-17-generic, x86_64: installed GraphicsCard: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4250] [1002:9715] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000] InstallationDate: Installed on 2013-04-22 (6 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130411) MachineType: Gigabyte Technology Co., Ltd. GA-880GA-UD3H MarkForUpload: True Package: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-17-generic root=UUID=ebd44c6f-b757-4427-89e6-f8d95a212293 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6 Tags: raring raring ubuntu compiz-0.9 Uname: Linux 3.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 04/16/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: GA-880GA-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd04/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GA-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GA-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-880GA-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.9~daily13.04.18.1~13.04-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.1.1-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.1.1-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.6-0ubuntu4 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1363910] [NEW] GTK2 theme not loaded from ~/.local/share/themes
You have been subscribed to a public bug: In Xubuntu 13.10 I was able to load themes from ~/.local/share/themes. In Xubuntu 14.04 I can still load the GTK3 theme, but not the GTK2 theme. Workaround: Load the themes from ~/.themes. Downside: Cluttered home directory. How to reproduce: 1. Download a theme and put in in ~/.themes. 2. Open settings manager and a GTK3 app. (I used gedit.) 3. Apply the downloaded theme. So far everything should work. 4. Move the downloaded theme to ~/.local/share/themes. 5. Apply another theme and reapply the downloaded one. At this point only the GTK2 theme is loaded. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xfce4 (not installed) ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Sep 1 11:12:59 2014 SourcePackage: xfce4 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty xubuntu -- GTK2 theme not loaded from ~/.local/share/themes https://bugs.launchpad.net/bugs/1363910 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. -- 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 1310489] Re: xorg.conf overwritten by booting system
That's right. I installed the proprietary drivers after the fglrx-packages created problems when I switched graphics cards via amdcccle or aticonfig(X-Server-crash). The problems unfortunately still exists with newest AMD Catalyst. I will deinstall the drivers, use fglrx again and report back. I don't think gpu-manager is blacklisted as I would not have had the problem (overwritten xorg.conf) in the first place. -- Philipp Commans In der Silbert 21 47877 Willich 0163 6961900 PGP-Key Threema AHZSVZ2V > Am 06.09.2014 um 13:07 schrieb Alberto Milone : > > @Philipp: even if the gpu-manager started on boot, it wouldn't solve > your problem. Here's why (as your log shows): > > "Proprietary driver installer detected" > > I assume you installed fglrx from the AMD installer without generating > the deb packages. By doing so, you probably broke your system. > > Also, I don't know if they blacklist the gpu-manager in Linux Mint 17 (I > don't use Mint). > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1310489 > > Title: > xorg.conf overwritten by booting system > > Status in “ubuntu-drivers-common” package in Ubuntu: > Fix Released > Status in “ubuntu-drivers-common” source package in Trusty: > Fix Committed > > Bug description: > Description:Ubuntu 14.04 LTS > Release:14.04 > > > > == SRU Request == > > There is a regression in the gpu-manager that causes it to revert user > changes right before the first reboot after enabling the fglrx driver > or the nvidia driver on a system with hybrid graphics (Intel+AMD or > Intel+NVIDIA). This causes the gpu-manager to remove the current > xorg.conf and to switch to Mesa. > > [Impact] > * This regression makes it almost impossible to use binary drivers on > systems with hybrid graphics. > > [Test Case] > * Make sure to be using a hybrid system with Intel+AMD or Intel+NVIDIA GPUs. > > * Make sure that the gpu-manager is not disabled (only necessary if > you disabled it manually). > > * Remove all fglrx and nvidia drivers (keep the nvidia-common and the > nvidia-prime packages): > sudo apt-get --purge remove nvidia-331 > sudo apt-get --purge remove nvidia-331 > sudo apt-get --purge remove fglrx > sudo apt-get --purge remove fglrx-updates > > * Install ubuntu-drivers-common from trusty-proposed. > > * Restart the system. > > * Install the binary driver (either fglrx or nvidia, according to the > available discrete GPU), reboot, and check that the binary driver is enabled > (attach your /var/log/gpu-manager.log) > - Expected: the (AMD or NVIDIA) discrete GPU is enabled. > - Bad behavior: the system switches back to the intel driver and the > discrete GPU is not used, despite the fact that the system was configured > properly. > > [Regression Potential] > * Low. Systems that currently work will keep working as usual, the ones > that currently fail should finally work. > > [Other Info] > * N/A > > - > > Hello, > > I am using a notebook with a quadcore AMD A10 and hybrid graficcard AMD/ATI > Radeon HD 8650G / AMD/ATI Sun XT Radeon HD 8670A/8670M/8690M. > After installing fglrx I generated the xorg.conf in the terminal with 'sudo > aticonfig --adapter=all --initial' and it looked pretty good. Up to this > point I was able to switch between the cards with the commands 'sudo > aticonfig --px-dgpu' for the discrete card and 'sudo aticonfig --px-igpu' for > the intigrated card to save power. > After rebooting I realized that I was no longer able to switch between the > cards and found that the xorg.conf will be overwritten whenever I modified it > and reboot the system. The new (by boot) generated xorg.conf contains not the > relevant information for switing between the cards. > I attached both configuration in one file (xorg.conf.comparison). I will > also provide the atisysteminfo-report.txt so far I will find the place where > to attach. > > Edit: I fixed the error --> "AIGLX error: failed to open > /usr/lib64/dri/fglrx_dri.so, error[/usr/lib64/dri/fglrx_dri.so: cannot > open shared object file: No such file or directory]" but it changed > not the bug of overwriting the xorg.conf. > > Regards, > Uwe > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: xorg 1:7.7+1ubuntu8 > ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 > Uname: Linux 3.13.0-24-generic x86_64 > NonfreeKernelModules: fglrx > .tmp.unity.support.test.0: > > ApportVersion: 2.14.1-0ubuntu3 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: Unity > Date: Mon Apr 21 08:43:29 2014 > DistUpgraded: Fresh install > DistroCodename: trusty > DistroVariant: ubuntu > DkmsStatus: fglrx, 13.350.1, 3.13.0-24-generic, x86_64: installed > ExtraDebuggingInte
[Desktop-packages] [Bug 531208]
There's a project (created by me) which tries to work around this limitation of X by providing a daemon-like app intercepting Ctrl+Shift+U and allowing to enter UTF-32 character codes: https://gitorious.org/ucode/ucode/ -- 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/531208 Title: Need way to insert arbitrary unicode characters in Kubuntu Status in X.Org X server: Confirmed Status in “xorg” package in Ubuntu: Won't Fix Bug description: KDE, Qt, and Xorg are in disagreement about who should implement ISO 14755, which would facilitate the input of arbitrary unicode characters. This is the original KDE bug: https://bugs.kde.org/show_bug.cgi?id=103788 It was pushed upstream to Qt: http://bugreports.qt.nokia.com/browse/QTBUG-8 From there it was pushed further upstream to Xorg: https://bugs.freedesktop.org/show_bug.cgi?id=26747 Xorg pushes the bug downstream, back to either Qt or KDE to implement, just as Gnome implemented the fix themselves. An Xorg developer who does not want to be named says that if KDE won't implement it then my distro should. So here I file that request. Note that in KDE 3 one could use the Kcharselect applet to enter arbitrary unicode characters, however that has been disabled in KDE 4: https://bugs.kde.org/show_bug.cgi?id=190776 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/531208/+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