[Desktop-packages] [Bug 1365755] [NEW] keyboard input method system not available from keyboard configuration in gnome-control-center
You have been subscribed to a public bug: The setting for the keyboard input system is not available in the only place where it should be set. It is only available instead in the separate application gnome-language-selector which has an icon in the gnome-control-center but is labeled as Language Support. This caused pain to me and a lot of other users because of the installation and default activation of iBus in 14.04. (see #1365752). It took me a long time to find that the setting is in gnome-language- selector, and I've discovered just now, filing this bug, that there is a way to access it from the control center. 30 minutes ago I would have titled the bug just keyboard input method not available in control center. - Language Support should deal with the selection of a language. Setting the behaviour of the keyboard here is inappropriate. - Keyboard should deal with the configuration of the keyboard. A setting that changes the behaviour of the keyboard such as the input method should be available here. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- keyboard input method system not available from keyboard configuration in gnome-control-center https://bugs.launchpad.net/bugs/1365755 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center 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
[Desktop-packages] [Bug 1316035] Re: matrox g200eR2 is unclaimed in 14.04
Just confirming, same thing here on an IBM x3500 M3: *-display UNCLAIMED description: VGA compatible controller product: MGA G200EV vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:07:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm vga_controller bus_master cap_list configuration: latency=64 maxlatency=32 mingnt=16 resources: memory:9600-96ff memory:9780-97803fff memory:9700-977f Also: $ lsmod | grep mg $ sudo modprobe mga $ lsmod | grep mg mga40811 0 drm 303102 1 mga Tried a recommended xorg.conf: Section Device Identifier Matrox Graphics, Inc. MGA G200 AGP2 Driver mga Option OldDmaInit True EndSection Doesn't help, as expected after Zoltán's comments. -- 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/1316035 Title: matrox g200eR2 is unclaimed in 14.04 Status in “xorg-server” package in Ubuntu: Confirmed Bug description: On a certified Dell PowerEdge T620 server (http://www.ubuntu.com/certification/hardware/201207-11426/) The matrox video card is not recognised: lspci | grep VGA 0a:00.0 VGA compatible controller: Matrox Electronics Systems Ltd. G200eR2 lshw -C display *-display UNCLAIMED description: VGA compatible controller product: G200eR2 vendor: Matrox Electronics Systems Ltd. physical id: 0 bus info: pci@:0a:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm vga_controller bus_master cap_list configuration: latency=64 maxlatency=32 mingnt=16 resources: memory:d800-d8ff memory:deffc000-deff memory:de00-de7f Thus xserver is not hardver accelerated. Also /dev/dri and /dev/dri/card0 is missing. kernel module mga is not loaded, although if i manually load by modprobe it works fine modprobe mga lsmod | grep mga mga40811 0 drm 302817 1 mga To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1316035/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365755] Re: keyboard input method system not available from keyboard configuration in gnome-control-center
** Package changed: ubuntu-meta (Ubuntu) = gnome-control-center (Ubuntu) ** Also affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: language-selector (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1365755 Title: keyboard input method system not available from keyboard configuration in gnome-control-center Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “language-selector” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: The setting for the keyboard input system is not available in the only place where it should be set. It is only available instead in the separate application gnome-language-selector which has an icon in the gnome-control-center but is labeled as Language Support. This caused pain to me and a lot of other users because of the installation and default activation of iBus in 14.04. (see #1365752). It took me a long time to find that the setting is in gnome-language- selector, and I've discovered just now, filing this bug, that there is a way to access it from the control center. 30 minutes ago I would have titled the bug just keyboard input method not available in control center. - Language Support should deal with the selection of a language. Setting the behaviour of the keyboard here is inappropriate. - Keyboard should deal with the configuration of the keyboard. A setting that changes the behaviour of the keyboard such as the input method should be available here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1365755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365755] Re: keyboard input method system not available from keyboard configuration in gnome-control-center
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-control-center (Ubuntu) Status: New = Confirmed -- 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/1365755 Title: keyboard input method system not available from keyboard configuration in gnome-control-center Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “language-selector” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: The setting for the keyboard input system is not available in the only place where it should be set. It is only available instead in the separate application gnome-language-selector which has an icon in the gnome-control-center but is labeled as Language Support. This caused pain to me and a lot of other users because of the installation and default activation of iBus in 14.04. (see #1365752). It took me a long time to find that the setting is in gnome-language- selector, and I've discovered just now, filing this bug, that there is a way to access it from the control center. 30 minutes ago I would have titled the bug just keyboard input method not available in control center. - Language Support should deal with the selection of a language. Setting the behaviour of the keyboard here is inappropriate. - Keyboard should deal with the configuration of the keyboard. A setting that changes the behaviour of the keyboard such as the input method should be available here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1365755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365755] Re: keyboard input method system not available from keyboard configuration in gnome-control-center
** Tags added: trusty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1365755 Title: keyboard input method system not available from keyboard configuration in gnome-control-center Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “language-selector” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: The setting for the keyboard input system is not available in the only place where it should be set. It is only available instead in the separate application gnome-language-selector which has an icon in the gnome-control-center but is labeled as Language Support. This caused pain to me and a lot of other users because of the installation and default activation of iBus in 14.04. (see #1365752). It took me a long time to find that the setting is in gnome-language- selector, and I've discovered just now, filing this bug, that there is a way to access it from the control center. 30 minutes ago I would have titled the bug just keyboard input method not available in control center. - Language Support should deal with the selection of a language. Setting the behaviour of the keyboard here is inappropriate. - Keyboard should deal with the configuration of the keyboard. A setting that changes the behaviour of the keyboard such as the input method should be available here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1365755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365755] Re: keyboard input method system not available from keyboard configuration in gnome-control-center
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: language-selector (Ubuntu) Status: New = Confirmed -- 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/1365755 Title: keyboard input method system not available from keyboard configuration in gnome-control-center Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “language-selector” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: The setting for the keyboard input system is not available in the only place where it should be set. It is only available instead in the separate application gnome-language-selector which has an icon in the gnome-control-center but is labeled as Language Support. This caused pain to me and a lot of other users because of the installation and default activation of iBus in 14.04. (see #1365752). It took me a long time to find that the setting is in gnome-language- selector, and I've discovered just now, filing this bug, that there is a way to access it from the control center. 30 minutes ago I would have titled the bug just keyboard input method not available in control center. - Language Support should deal with the selection of a language. Setting the behaviour of the keyboard here is inappropriate. - Keyboard should deal with the configuration of the keyboard. A setting that changes the behaviour of the keyboard such as the input method should be available here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1365755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365755] Re: keyboard input method system not available from keyboard configuration in gnome-control-center
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New = Confirmed -- 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/1365755 Title: keyboard input method system not available from keyboard configuration in gnome-control-center Status in “gnome-control-center” package in Ubuntu: Confirmed Status in “language-selector” package in Ubuntu: Confirmed Status in “unity-control-center” package in Ubuntu: Confirmed Bug description: The setting for the keyboard input system is not available in the only place where it should be set. It is only available instead in the separate application gnome-language-selector which has an icon in the gnome-control-center but is labeled as Language Support. This caused pain to me and a lot of other users because of the installation and default activation of iBus in 14.04. (see #1365752). It took me a long time to find that the setting is in gnome-language- selector, and I've discovered just now, filing this bug, that there is a way to access it from the control center. 30 minutes ago I would have titled the bug just keyboard input method not available in control center. - Language Support should deal with the selection of a language. Setting the behaviour of the keyboard here is inappropriate. - Keyboard should deal with the configuration of the keyboard. A setting that changes the behaviour of the keyboard such as the input method should be available here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1365755/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1040193] Re: Redundant ubuntu-online-accounts and gnome-online-accounts panels using a session other than Unity
** Tags added: ubuntu-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1040193 Title: Redundant ubuntu-online-accounts and gnome-online-accounts panels using a session other than Unity Status in “gnome-control-center” package in Ubuntu: Confirmed Bug description: To reproduce this, close gnome-control-center and run the following command: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center Note that there are two Online Accounts panels: one for ubuntu-online- accounts and one for gnome-online-accounts. This is very unpleasant. These two panels claim to do the same thing, but ultimately they have nothing to do with each other. To make matters worse, the gnome-online-accounts panel doesn't appear to do much of anything by default (except probably with Evolution) since Empathy has been built to use ubuntu-online-accounts — to the extent that Empathy will open that configuration panel when the user chooses Accounts from its menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1040193/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 589518] [NEW] Error activating XKB configuration
You have been subscribed to a public bug: On login to ubuntu-desktop this appears: Error activating XKB configuration It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10706000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Here is the requested information: zie@zulubuntu ~ % xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, us, mac, lv3:ralt_switch _XKB_RULES_NAMES(STRING) = evdev, pc105, us, mac, lv3:ralt_switch zie@zulubuntu ~ % gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [lv3 lv3:ralt_switch] model = macbook78 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ubuntu-desktop 1.197 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 Date: Thu Jun 3 20:48:50 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubuntu-meta ** Affects: libxklavier (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Error activating XKB configuration https://bugs.launchpad.net/bugs/589518 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier 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
[Desktop-packages] [Bug 1365695] Re: No longer able to use GUI after update
I'm experiencing the same problem (I'm the OP from the link posted in #2) on my T530. However, downgrading ubuntu-drivers-common to 0.2.91.5 didn't work for me, even after reinstalling the nvidia drivers. It seems as if something keeps changing the alternatives for x86_64 -linux-gnu_gl_conf because if I change them, I can modprobe the nvidia driver. I just can't get the update to persist. Switching to Discrete Graphics in the BIOS is a workaround for me because the nvidia driver can now load and I can use a multiple monitor setup. It's not a fix though and causes other (well-known) problems. -- 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-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 589518] Re: Error activating XKB configuration
*** This bug is a duplicate of bug 524406 *** https://bugs.launchpad.net/bugs/524406 ** Package changed: ubuntu-meta (Ubuntu) = libxklavier (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/589518 Title: Error activating XKB configuration Status in “libxklavier” package in Ubuntu: New Bug description: On login to ubuntu-desktop this appears: Error activating XKB configuration It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10706000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Here is the requested information: zie@zulubuntu ~ % xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, us, mac, lv3:ralt_switch _XKB_RULES_NAMES(STRING) = evdev, pc105, us, mac, lv3:ralt_switch zie@zulubuntu ~ % gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [lv3 lv3:ralt_switch] model = macbook78 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ubuntu-desktop 1.197 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 Date: Thu Jun 3 20:48:50 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxklavier/+bug/589518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 589518] Re: Error activating XKB configuration
*** This bug is a duplicate of bug 524406 *** https://bugs.launchpad.net/bugs/524406 ** This bug has been marked a duplicate of bug 524406 Frequent Error activating XKB configuration -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxklavier in Ubuntu. https://bugs.launchpad.net/bugs/589518 Title: Error activating XKB configuration Status in “libxklavier” package in Ubuntu: New Bug description: On login to ubuntu-desktop this appears: Error activating XKB configuration It can happen under various circumstances: - a bug in libxklavier library - a bug in X server (xkbcomp, xmodmap utilities) - X server with incompatible libxkbfile implementation X server version data: The X.Org Foundation 10706000 If you report this situation as a bug, please include: - The result of xprop -root | grep XKB - The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd Here is the requested information: zie@zulubuntu ~ % xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = evdev, pc105, us, mac, lv3:ralt_switch _XKB_RULES_NAMES(STRING) = evdev, pc105, us, mac, lv3:ralt_switch zie@zulubuntu ~ % gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [] options = [lv3 lv3:ralt_switch] model = macbook78 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ubuntu-desktop 1.197 ProcVersionSignature: Ubuntu 2.6.32-22.35-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 NonfreeKernelModules: wl nvidia Architecture: amd64 Date: Thu Jun 3 20:48:50 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: ubuntu-meta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxklavier/+bug/589518/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Description changed: Boot live session - choose Try + + Same issue with at least Ubuntu and Xubuntu 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=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- 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 Ubuntu and Xubuntu 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=set 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 1366276] Re: iphone-set-info crashed with SIGSEGV in strlen()
*** This bug is a duplicate of bug 1352170 *** https://bugs.launchpad.net/bugs/1352170 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 #1352170, 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/1366276/+attachment/4196908/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1366276/+attachment/4196910/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1366276/+attachment/4196911/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1366276/+attachment/4196912/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1366276/+attachment/4196913/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1366276/+attachment/4196914/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1366276/+attachment/4196915/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1352170 ** 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 libgpod in Ubuntu. https://bugs.launchpad.net/bugs/1366276 Title: iphone-set-info crashed with SIGSEGV in strlen() Status in “libgpod” package in Ubuntu: New Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: libgpod-common 0.8.3-4ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 Date: Wed Sep 3 17:16:55 2014 ExecutablePath: /lib/udev/iphone-set-info InstallationDate: Installed on 2014-03-04 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcCmdline: /lib/udev/iphone-set-info ProcEnviron: SegvAnalysis: Segfault happened at: 0x7f5ace7394fa strlen+42:movdqu (%rax),%xmm12 PC (0x7f5ace7394fa) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %xmm12 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: libgpod StacktraceTop: strlen () at ../sysdeps/x86_64/strlen.S:106 __GI___strdup (s=0x0) at strdup.c:41 plist_new_string () from /usr/lib/x86_64-linux-gnu/libplist.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 lockdownd_client_new_with_handshake () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 Title: iphone-set-info crashed with SIGSEGV in strlen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgpod/+bug/1366276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1366221] Re: gnome-calculator does not show application menu anywhere
** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1366221 Title: gnome-calculator does not show application menu anywhere Status in “gnome-calculator” package in Ubuntu: New Bug description: gnome-calculator no longer offers, as of 14.04, an application menu. It used to be there before the upgrade, in 12.04. So switching between scientific and engineering now requires me to use dconf-editor. Note that I did check hovering menu line, application title bar, and thereabouts, to no avail. This application is now useless... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-calculator 1:3.10.2-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 CurrentDesktop: GNOME Date: Sat Sep 6 01:12:00 2014 SourcePackage: gnome-calculator UpgradeStatus: Upgraded to trusty on 2014-08-29 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1366221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365870] Re: Too little visual feedback during import
** Tags added: regression-release -- 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/1365870 Title: Too little visual feedback during import Status in “rhythmbox” package in Ubuntu: New Bug description: if I pick a directory in ubuntu for importing into the collection, there is too little UI feedback, sometimes just the import box/count remain dimmed; I would need feedback no music in folder or all music already in library or there were errors, check import errors list. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 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: Fri Sep 5 09:09:18 2014 SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2014-08-29 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1365870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1365861] Re: rhythmbox's interface was stripped bare the application is no longer useful
** Tags added: regression-release -- 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/1365861 Title: rhythmbox's interface was stripped bare the application is no longer useful Status in “rhythmbox” package in Ubuntu: New Bug description: There are no more preferences dialogs, for instance there is no way to remove directories from the music collection. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 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: Fri Sep 5 09:08:03 2014 SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2014-08-29 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1365861/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1366278] Re: upowerd crashed with SIGSEGV in strlen()
*** This bug is a duplicate of bug 1334827 *** https://bugs.launchpad.net/bugs/1334827 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 #1334827, 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/1366278/+attachment/4196916/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1366278/+attachment/4196918/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1366278/+attachment/4196919/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1366278/+attachment/4196920/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1366278/+attachment/4196921/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1366278/+attachment/4196922/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1366278/+attachment/4196923/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1334827 ** 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 upower in Ubuntu. https://bugs.launchpad.net/bugs/1366278 Title: upowerd crashed with SIGSEGV in strlen() Status in “upower” package in Ubuntu: New Bug description: ... ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: upower 0.9.23-2ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Tue Sep 2 18:06:10 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-03-04 (185 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0x7fdad0bd84fa strlen+42:movdqu (%rax),%xmm12 PC (0x7fdad0bd84fa) ok source (%rax) (0x) not located in a known VMA region (needed readable region)! destination %xmm12 ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: upower StacktraceTop: strlen () at ../sysdeps/x86_64/strlen.S:106 __GI___strdup (s=0x0) at strdup.c:41 plist_new_string () from /usr/lib/x86_64-linux-gnu/libplist.so.2 ?? () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 lockdownd_client_new_with_handshake () from /usr/lib/x86_64-linux-gnu/libimobiledevice.so.4 Title: upowerd crashed with SIGSEGV in strlen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1366278/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
** Description changed: Boot live session - choose Try - Same issue with at least Ubuntu and Xubuntu + 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=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) -- 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=set 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 1310489] Re: xorg.conf overwritten by booting system
Hi All I have an AMD APU system with two graphics cards - one integrated and one stand alone (RADEON HD 6550 6670). I have been having the same problem as described above, every time I install the driver from AMD's website generating a new xorg.conf, rebooting removes it and the system goes into a black screen. I followed the instructions as above, did a fresh install of 14.04, enabled trusty-proposed, updated ubuntu-drivers-common and reinstalled the drivers, but the problem persists. xorg.conf keeps getting rewritten and the system goes to the black screen on reboot. I am using the Catalyst 14.6 driver from AMD's website and am choosing the Generate distribution specific package option for the installation. Am attaching the gpu-manager.log here. Have been struggling with this for the last few months and the problem is that the system under Xorg is almost unusable - laggy graphics and keyboard. I do hope someone can help me with this. The only other option I can see is fall back to 12.04, which was working fine on my machine. Thanks in advance folks. A ** Attachment added: gpu-manager log https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1310489/+attachment/4196926/+files/gpu-manager.log -- 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
[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
I should add that the gpu-manager attached above is actually from the second reboot I tried once the first one failed. xorg.conf was already rewritten in the first reboot attempt. -- 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.board.vendor: Hewlett-Packard dmi.board.version: 01.13
[Desktop-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
Thank you Ludovic for your quick response. I generated to log-files, logcardrea...@powerup.txt in case it goes wrong (only when the card-reader is plugged in while the computer is starting-up or rebooting LogCardReaderOK.txt after the crash - removed the reader and sudo service pcscd start /usr/sbin/pcscd --version pcsc-lite version 1.8.10. Copyright (C) 1999-2002 by David Corcoran corco...@linuxnet.com. Copyright (C) 2001-2011 by Ludovic Rousseau ludovic.rouss...@free.fr. Copyright (C) 2003-2004 by Damien Sauveron sauve...@labri.fr. Report bugs to mus...@lists.musclecard.com. Enabled features: Linux x86_64-pc-linux-gnu serial usb libudev usbdropdir=/usr/lib/pcsc/drivers ipcdir=/var/run/pcscd configdir=/etc/reader.conf.d pcsc_scan (when the reader is ok) PC/SC device scanner V 1.4.22 (c) 2001-2011, Ludovic Rousseau ludovic.rouss...@free.fr Compiled with PC/SC lite version: 1.8.10 Using reader plug'n play mechanism Scanning present readers... 0: VASCO DP905v1.1 00 00 Sat Sep 6 10:18:48 2014 Reader 0: VASCO DP905v1.1 00 00 Card state: Card removed, apt-cache policy pcscd pcscd: Geïnstalleerd: 1.8.10-1ubuntu1 Kandidaat: 1.8.10-1ubuntu1 Versietabel: *** 1.8.10-1ubuntu1 0 500 http://be.archive.ubuntu.com/ubuntu/ trusty/universe amd64 Packages 100 /var/lib/dpkg/status Middleware = eid-mw low-level support for Belgian Electronic Identity Card apt-cache policy eid-mw eid-mw: Geïnstalleerd: 4.0.6r1620-0trusty1 Kandidaat: 4.0.6r1620-0trusty1 Versietabel: *** 4.0.6r1620-0trusty1 0 500 http://files.eid.belgium.be/debian/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ** Attachment added: logcardrea...@powerup.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196927/+files/LogCardReader%40Powerup.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 ludovic.rouss...@free.fr 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.
[Desktop-packages] [Bug 1366152] Re: System crash when Vasco-card-reader is plugged in at powerup
And log-file when the reader is ok ** Attachment added: LogCardReaderOK.txt https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1366152/+attachment/4196928/+files/LogCardReaderOK.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 ludovic.rouss...@free.fr 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
[Desktop-packages] [Bug 1365336] Re: Lightdm update=No desktop
utopic + lightdm 1.11.8 + nvidia-331 (newest): black screen (nvidia-331 has a nvidia-prime error, so the 'nouveau' fallback is used) utopic + gdm boots well with 'nouveau' only nvidia-331 report lp:1366284 -- 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/1365336 Title: Lightdm update=No desktop Status in “fglrx-installer” package in Ubuntu: In Progress Status in “fglrx-installer-updates” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: Confirmed Status in “nvidia-graphics-drivers-304” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Fix Released Bug description: Update to lightdm from 1.11.7-0ubuntu1 to 1.11.8-0ubuntu1 leaves me with no desktop on normal boot. Machine boots directly to tty1. Logged in at tty1 and then startx leads to a desktop that requires password to start properly and with themes unapplied. Password required to reboot machine. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.11.8-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Sep 4 08:20:14 2014 InstallationDate: Installed on 2014-07-17 (48 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140717) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1365336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1366284] [NEW] Unit nvidia-prime.service failed to load: No such file or directory
Public bug reported: Utopic i386 with gtx 750 and q9550 (no builtin gpu here) using systemd- boot Follow up lp:1365336 nvidia-331 package error about nvidia-prime at build time: oem@u32:~$ sudo apt-get install --reinstall nvidia-331 [sudo] password for oem: Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/27,7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 216738 files and directories currently installed.) Preparing to unpack .../nvidia-331_331.89-0ubuntu3_i386.deb ... Removing all DKMS Modules Done. Unpacking nvidia-331 (331.89-0ubuntu3) over (331.89-0ubuntu3) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... Setting up nvidia-prime (0.6.6) ... Failed to issue method call: Unit nvidia-prime.service failed to load: No such file or directory. invoke-rc.d: initscript nvidia-prime, action start failed. dpkg: error processing package nvidia-prime (--configure): subprocess installed post-installation script returned error exit status 6 Setting up nvidia-331 (331.89-0ubuntu3) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-331-331.89 DKMS files... Building only for 3.16.0-13-generic Building for architecture i686 Building initial module for 3.16.0-13-generic Done. nvidia_331: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.16.0-13-generic/updates/dkms/ depmod DKMS: install completed. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-13-generic Errors were encountered while processing: nvidia-prime E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nvidia-331 331.89-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1 Uname: Linux 3.16.0-13-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Sat Sep 6 10:52:02 2014 SourcePackage: nvidia-graphics-drivers-331 UpgradeStatus: No upgrade log present (probably fresh install) Note: uninstalling the faulty nvidia-prime package does not let booting with nvidia (jockey fails to find nvidia driver) and then 'nouveau' is used ** Affects: nvidia-graphics-drivers-331 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 systemd-boot utopic ** Description changed: - Follow up lp:1365336 nvidia-331 package + Utopic i386 with gtx 750 using systemd-boot + + + Follow up lp:1365336 nvidia-331 package error about nvidia-prime at build time: oem@u32:~$ sudo apt-get install --reinstall nvidia-331 - [sudo] password for oem: + [sudo] password for oem: Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/27,7 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 216738 files and directories currently installed.) Preparing to unpack .../nvidia-331_331.89-0ubuntu3_i386.deb ... Removing all DKMS Modules Done. Unpacking nvidia-331 (331.89-0ubuntu3) over (331.89-0ubuntu3) ... Processing triggers for man-db (2.6.7.1-1) ... Processing triggers for ureadahead (0.100.0-16) ... Setting up nvidia-prime (0.6.6) ... Failed to issue method call: Unit nvidia-prime.service failed to load: No such file or directory. invoke-rc.d: initscript nvidia-prime, action start failed. dpkg: error processing package nvidia-prime (--configure): - subprocess installed post-installation script returned error exit status 6 + subprocess installed post-installation script returned error exit status 6 Setting up nvidia-331 (331.89-0ubuntu3) ... update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-331 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-331-331.89 DKMS files... Building only for 3.16.0-13-generic Building for architecture i686 Building initial module for 3.16.0-13-generic Done. nvidia_331: Running module version sanity check. - - Original module -- No original module exists within this kernel - -
[Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
Abhijit: the log looks fine. It says that fglrx is enabled and in use. Please attach the following files: 1) /var/log/Xorg.0.log 2) the output of the dmesg command 3) your current xorg.conf 4) the xorg.conf that the gpu-manager keeps overwriting (you can try generating a new one using the ati-config tool) This way I can see if you're being hit by the problem discussed here or if it's a separate issue that needs a different fix. -- 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:
Re: [Desktop-packages] [Bug 1310489] Re: xorg.conf overwritten by booting system
Hallo Alberto, here are my results: 1) After the reboot there was no log-file. It was not created. 2) After starting the upstart job (output:gpu-manager stop/waiting) , an new log-file was created. See attachment. Is gpu-manager working correctly, according to the log-file? Will the gpu-manager now be working after a restart? How can I verify? Can I check its status via sudo service gpu-manager status ? The output of the above command after a reboot was also:gpu-manager stop/waiting. After further reboots the log-file was not rewritten according to the last change time in ls -la. Additional information: I am using Linux Mint 17 with cinnamon. THX! Best regards Philipp ** Attachment added: gpu-manager.log https://bugs.launchpad.net/bugs/1310489/+attachment/4196949/+files/gpu-manager.log -- 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]
[Desktop-packages] [Bug 1320132] Re: Evince crashes with segmentation fault
This fix is in poppler 0.26.4. Any chance of getting this into Utopic? -- 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/1320132 Title: Evince crashes with segmentation fault Status in “evince” package in Ubuntu: New Bug description: 1. Open the pdf attached 2. See evince crashing with segmentation fault I tried to deliver a backtrace but failed. Behaviour is somewhat different in gdb - evince freezes now and does not crash. When I close evince and get back to the terminal I am not able to type anything in the command line. CTRC+C does not help. This is how far I got: GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. Type show configuration for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type help. Type apropos word to search for commands related to word... Reading symbols from evince...(no debugging symbols found)...done. (gdb) sd[K[Khandle SIG33 pass nostop noprint SignalStopPrint Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: /usr/bin/evince [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7f0453194700 (LWP 25150)] [New Thread 0x7f0452786700 (LWP 25151)] [New Thread 0x7f0451f85700 (LWP 25152)] [New Thread 0x7f0451784700 (LWP 25153)] [New Thread 0x7f042d761700 (LWP 25154)] [Thread 0x7f042d761700 (LWP 25154) exited] [New Thread 0x7f042d761700 (LWP 25158)] [Thread 0x7f042d761700 (LWP 25158) exited] [New Thread 0x7f042d761700 (LWP 25162)] [New Thread 0x7f04274ce700 (LWP 25163)] [New Thread 0x7f0426ccd700 (LWP 25164)] [Thread 0x7f04274ce700 (LWP 25163) exited] [Thread 0x7f0426ccd700 (LWP 25164) exited] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f042d761700 (LWP 25162)] 0x7f045c8effd5 in ?? () from /usr/lib/x86_64-linux-gnu/libcairo.so.2 (gdb) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: evince 3.10.3-0ubuntu10 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.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri May 16 09:51:48 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-11-26 (170 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) SourcePackage: evince UpgradeStatus: Upgraded to trusty on 2014-04-22 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1320132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1364199] Re: Unable to change the refresh rate of the monitor
** Description changed: The xrandr does not work with the proprietary NVIDIA drivers, and in Unity and NVIDIA X Server Settings there is no option to change the refresh rate of the monitor. Ubuntu 14.04.1 Xorg 1.15.1 Driver 331.38 sudo lspci -c display output: renan@ubuntu:~$ sudo lshw -C display [sudo] password for renan: *-display description: VGA compatible controller product: GT218 [GeForce 8400 GS Rev. 3] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:04:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:45 memory:fd00-fdff memory:e000-efff memory:de00-dfff ioport:ec00(size=128) memory:fe00-fe07 renan@ubuntu:~$ Question: https://answers.launchpad.net/ubuntu/+source/xorg/+question/254081 - Theads on Ubuntu forums (without solution): + Theads on Ubuntu forums: http://ubuntuforums.org/showthread.php?t=2241692 http://ubuntuforums.org/showthread.php?t=2242124 -- 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/1364199 Title: Unable to change the refresh rate of the monitor Status in “xorg” package in Ubuntu: New Bug description: The xrandr does not work with the proprietary NVIDIA drivers, and in Unity and NVIDIA X Server Settings there is no option to change the refresh rate of the monitor. Ubuntu 14.04.1 Xorg 1.15.1 Driver 331.38 sudo lspci -c display output: renan@ubuntu:~$ sudo lshw -C display [sudo] password for renan: *-display description: VGA compatible controller product: GT218 [GeForce 8400 GS Rev. 3] vendor: NVIDIA Corporation physical id: 0 bus info: pci@:04:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:45 memory:fd00-fdff memory:e000-efff memory:de00-dfff ioport:ec00(size=128) memory:fe00-fe07 renan@ubuntu:~$ Question: https://answers.launchpad.net/ubuntu/+source/xorg/+question/254081 Theads on Ubuntu forums: http://ubuntuforums.org/showthread.php?t=2241692 http://ubuntuforums.org/showthread.php?t=2242124 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1364199/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
@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 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)
[Desktop-packages] [Bug 1359486] Re: [PPA] Use LibreOffice Dialogs setting is ignored in KDE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qt4-x11 (Ubuntu) Status: New = Confirmed -- 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/1359486 Title: [PPA] Use LibreOffice Dialogs setting is ignored in KDE Status in LibreOffice Productivity Suite: Won't Fix Status in “libreoffice” package in Ubuntu: Fix Released Status in “qt4-x11” package in Ubuntu: Confirmed Bug description: Kubuntu 14.04 (KDE Desktop Environment) Packages from this ppa: https://launchpad.net/~libreoffice Version: 4.3.0-3ubuntu2~trusty1 (as reported by dpkg, note updated packages as of about 1 hour ago) or 4.3.0.4 Build ID: 430m0(Build:4) as reported by LibreOffice about dialog. LibreOffice uses it's native filepicker/save dialogs, regardless of whether the config option Use LibreOffice Dialogs is ticked or not. This is a regression from 4.2.4-0ubuntu2 currently in the main ubuntu security repository. Related Bugs: https://bugreports.qt-project.org/browse/QTBUG-38585 https://bugreports.qt-project.org/browse/QTBUG-34614 According to the LO team, both these bugs have patches that address the automatic disabling of Qt dialogs at runtime (if buggy Qt is detected.) Initial report/discussion on LO bugtracker (now closed) here: https://bugs.freedesktop.org/show_bug.cgi?id=82598 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1359486/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[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
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 alberto.mil...@canonical.com: @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 ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8650G]
[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
[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=set 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] 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 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=set 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 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 SourcePackage:
[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 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 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 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 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 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=set 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 present
[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=set 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 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=set 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 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=set 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:
[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 ludovic.rouss...@free.fr 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
[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.name: System
[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 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=set 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 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 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 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 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 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=flattopic_id=16200forum=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 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 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: 10
[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=set 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:
[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
[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 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 Markm...@.com. The other is Jamesjames.m...@.com. 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]
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 Markm...@.com. The other is Jamesjames.m...@.com. 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 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=set 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
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 Kamppeter till.kamppe...@gmail.com Sat, 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=set 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 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 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 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.devices: inputPower
[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 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=set 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 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 : 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 ludovic.rouss...@free.fr 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
[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 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
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 ludovic.rouss...@free.fr 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
[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 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 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 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 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 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 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-xorg-video-ati
[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 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=set 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 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 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 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=Thunderbirdplatform=linuxquery_search=signaturequery_type=containsquery=uGlobalMenureason_type=containsdate=05%2F16%2F2011%2023%3A29%3A46range_value=1range_unit=weekshang_type=anyprocess_type=anydo_query=1signature=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 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=set 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 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 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=7t=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=7t=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 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+other key
else if (ctrl || shift released)
change group
The XKB map for left control in this case is:
key LCTL { [ 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 really
[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: NO-CARRIER,BROADCAST,MULTICAST,UP 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: BROADCAST,MULTICAST 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: NO-CARRIER,BROADCAST,MULTICAST,UP 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: BROADCAST,MULTICAST 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 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 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: Base
[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: table:table-cell office:value-type=date office:date-value=2014-06-02 calcext:value-type=date text:p02.06.14/text:p /table:table-cell But it step 7, it is display as 1.6.2010 (that is 2010-06-01) . After saving in step 8, content.xml contains: table:table-cell office:value-type=date office:date-value=2010-06-01 calcext:value-type=date text:p01.06.10/text:p /table:table-cell 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] 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: table:table-cell office:value-type=date office:date-value=2014-06-02 calcext:value-type=date text:p02.06.14/text:p /table:table-cell But it step 7, it is display as 1.6.2010 (that is 2010-06-01) . After saving in step 8, content.xml contains: table:table-cell office:value-type=date office:date-value=2010-06-01 calcext:value-type=date text:p01.06.10/text:p /table:table-cell 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 Super is pressed first in a SuperAltkey chord, Alt 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 Super is pressed first in a SuperAltkey chord, Alt 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
