[Desktop-packages] [Bug 2062982] [NEW] [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect
Public bug reported: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- 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/2062982 Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider and mute button have no effect Status in alsa-driver package in Ubuntu: New Bug description: When the external sound card (SB Live! 24 bit) is used, the volume slider and the mute button have no effect. The volume is low. I tried two SB Live! 24 bit cards (at home and at work). The behaviour is the same. On Lubuntu 20.04, there was no problem. The embedded sound card operates normally and reacts on the volume slider. Ubuntu 22.04.4 LTS pulseaudio 1:15.99.1+dfsg1-1ubuntu2.2 pavucontrol 5.0-2 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.8.7-2-liquorix-amd64 x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Apr 20 21:33:26 2024 InstallationDate: Installed on 2024-04-03 (16 days ago) InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: SoundBlaster Live! 24-bit External SB0490 - SB Live! 24-bit External Symptom_PulseAudioLog: кві 20 19:57:33 Lattitude dbus-daemon[590]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.33' (uid=1001 pid=845 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo") Symptom_Type: Volume slider, or mixer problems Title: [USB-Audio - SB Live! 24-bit External, playback] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2023 dmi.bios.release: 1.32 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.32.2 dmi.board.name: 015DR5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: NTB71181 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.32.2:bd09/22/2023:br1.32:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn015DR5:rvrA00:cvnDellInc.:ct10:cvr:sku07A7: dmi.product.family: Latitude dmi.product.name: Latitude 5480 dmi.product.sku: 07A7 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2062982/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 583122] Re: firefox occasionally highlights contents of form fields while typing thereby overwriting previously entered keystrokes
Is it Firefox or operating system bug? No problems in Chrome/Chromium/Opera, no problem found in Ubuntu 16.04 and LUbuntu 18.04. Nevertheless, the same problem occurs in LibreOffice (search field) and GIMP 2.10 (some settings) on Ubuntu/Kubuntu 18.04 using GNOME and Unity (installed manually). Maybe, the problem is belong to the text field component in the operating system. If it is actually OS problem, the bug may be reported in the corresponding bug tracker. -- 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/583122 Title: firefox occasionally highlights contents of form fields while typing thereby overwriting previously entered keystrokes Status in Mozilla Firefox: New Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox On occasion while typing into a form field in firefox (search field, url field, webpage form field), after typing a few characters, the browser will automatically highlight the previously entered characters, causing my subsequently entered keystrokes to overwrite the previously entered keystrokes. I cannot reproduce this behavior reliably, though it does happen quite often. There are various methods that I have used to make the problem go away, though none work reliably. These include closing the tab, hitting enter to cause a pageload, restarting the browser. I am using Ubuntu 10.04. This problem was not present in Ubuntu 9.10 on the same hardware. The firefox package version is 3.6.3+nobinonly- 0ubuntu4. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-22-generic x86_64 Architecture: amd64 CheckboxSubmission: e8b67d75e6dc3e68647d9c34878edc73 CheckboxSystem: d00f84de8a555815fa1c4660280da308 Date: Wed May 19 20:21:20 2010 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/583122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568604] Re: Mouse cursor lost when unlocking with Intel graphics
Also affect Ubuntu 18.04. Laptop: Acer Aspire 5715Z-2A1G12Mi. -- 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/1568604 Title: Mouse cursor lost when unlocking with Intel graphics Status in elementary OS: Fix Released Status in xf86-video-intel: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Status in xserver-xorg-video-intel-lts-xenial package in Ubuntu: Confirmed Status in xserver-xorg-video-intel source package in Xenial: Fix Released Status in xserver-xorg-video-intel package in Debian: Fix Released Bug description: [Relevant details] This bug also affects Trusty and all distributions based on it, like Elementary OS Freya. [Impact] Mouse cursor is no longer visible after VT-switch for systems with Intel graphics. Switching VTs again may cause the cursor to become visible again. - Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) This is often observed in systems that lock the session and return to the greeter (including at least Xubuntu, Ubuntu Mate, and elementary OS). [Test Case] (Requires a lightdm-based screen locking solution) 1. Start a new session. 2. Lock your screen. 2a. You are redirected to the lightdm greeter. 3. Login/Unlock your session. 4. Cursor is no longer visible. [Regression Potential] remains to be seen === [Original Report] Cursor is visible at unlock screen either after returning from suspend or just locking. After unlocking screen cursor is invisible. Changing to vt1 then back to vt7 (ctrl+alt+f1 then ctrl+alt+f7) cursor returns no matter if you suspend or sleep, to swap or disk when you return from it, the mouse cursor is missing.you can still move the mouse and you can see (because it highlights the window) as you move it around. But the cursor is not displayed on the screen. i am using a lenovo W540 laptop. I downloaded the latest beta on april 8 2016. this is xubuntu using the xfce window manager. the cursor does return if i log off and log back in, but that actually defeats the purpose of going to sleep. --- ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-08 (2 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia Package: light-locker 1.7.0-2ubuntu1 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Tags: xenial Uname: Linux 4.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1568604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1244087] Re: Ubuntu 13.10 Main Menu editor Problem
I can not perform any editions. No moving, no folder creation. Starting from a terminal causes only one message repeated twice: (alacarte:13511): Gtk-CRITICAL **: gtk_accel_label_set_accel_closure: assertion 'gtk_accel_group_from_accel_closure (accel_closure) != NULL' failed And nothing else in terminal window. Tested on Ubuntu 13.10 X64 fresh install and upgraded from 13.04. The same problem in OpenSUSE discussed at http://forums.opensuse.org/showthread.php/486011-Can-t-edit-menu-or-item-properties-in-Alacarte With best regards. Viktor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1244087 Title: Ubuntu 13.10 Main Menu editor Problem Status in One Hundred Papercuts: Confirmed Status in “alacarte” package in Ubuntu: Confirmed Bug description: I just ungraded to *Ubuntu 13.10* using ) *Gnome (classic) Desktop*. The [Main Menu] editor does NOT work properly. I cannot ADD items. I CAN edit and move existing items only. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1244087/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1282767] Re: Screen does not dim or blank after specified time
Fresh installation of Ubuntu solves this bug. Possible updater bug. -- 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/1282767 Title: Screen does not dim or blank after specified time Status in “xorg” package in Ubuntu: Confirmed Bug description: Dear developers! After upgrading from Ubuntu 13.04 to Ubuntu 13.10 x64 the screen always stays on at standard brightness. After specified time it does not go blank. It may cause quicker LED degradation. I tried different settings without a result. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 Date: Thu Feb 20 22:05:38 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-15-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-02-08 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO IdeaPad Z580 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=304853b1-c803-465a-93ee-3f894d45099d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5FCN34WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: Lenovo Z580 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr5FCN34WW:bd06/11/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvrLenovoZ580:cvnIntelCorporation:ct9:cvr0.1: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131113-0ubuntu1ppa1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Feb 20 13:53:25 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. evdev: B16_b_02 USB-PS/2 Optical Mouse: Unable to open evdev device /dev/input/event5. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 52268 vendor VSC xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1282767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283505] [NEW] Addressing error playing next track of CD
Public bug reported: Dear Developers! After upgrading to Ubuntu 13.10 x64 rhythmbox can not play CD. It plays one track and close with Addressing error trying to play next track. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgstreamer0.10-0 0.10.36-1.2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Feb 22 19:11:19 2014 InstallationDate: Installed on 2014-02-08 (14 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: Dear Developers! After upgrading to Ubuntu 13.10 x64 rhythmbox can not play CD. It plays one track and close with Addressing error trying to play next track. + With best regards. + Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgstreamer0.10-0 0.10.36-1.2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Feb 22 19:11:19 2014 InstallationDate: Installed on 2014-02-08 (14 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gstreamer0.10 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 gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1283505 Title: Addressing error playing next track of CD Status in “gstreamer0.10” package in Ubuntu: New Bug description: Dear Developers! After upgrading to Ubuntu 13.10 x64 rhythmbox can not play CD. It plays one track and close with Addressing error trying to play next track. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgstreamer0.10-0 0.10.36-1.2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Feb 22 19:11:19 2014 InstallationDate: Installed on 2014-02-08 (14 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1283505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1283505] Re: Addressing error playing next track of CD
** Attachment added: This is a back trace. My comment included with // prefix. https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1283505/+attachment/3991665/+files/rhythmbox-backtrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1283505 Title: Addressing error playing next track of CD Status in “gstreamer0.10” package in Ubuntu: New Bug description: Dear Developers! After upgrading to Ubuntu 13.10 x64 rhythmbox can not play CD. It plays one track and close with Addressing error trying to play next track. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgstreamer0.10-0 0.10.36-1.2ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Sat Feb 22 19:11:19 2014 InstallationDate: Installed on 2014-02-08 (14 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: gstreamer0.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1283505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
I test the shortcat Alt+Shift. It works only if shift pressed before alt. Pressing alt - pressing shift - releasing in any order does not work. With best regards. Viktor. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: New Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) Separate bug reports for individual layout switching hotkey combinations: Super+Space and Shift+Super+Space: * Unity greeter (bug 1245137); * Unity session (bug 1245136);
[Desktop-packages] [Bug 1282767] [NEW] Screen does not dim or blank after specified time
Public bug reported: Dear developers! After upgrading from Ubuntu 13.04 to Ubuntu 13.10 x64 the screen always stays on at standard brightness. After specified time it does not go blank. It may cause quicker LED degradation. I tried different settings without a result. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.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 Date: Thu Feb 20 22:05:38 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-15-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.11.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3977] NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2014-02-08 (12 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MachineType: LENOVO IdeaPad Z580 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic root=UUID=304853b1-c803-465a-93ee-3f894d45099d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5FCN34WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: Lenovo Z580 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr5FCN34WW:bd06/11/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvrLenovoZ580:cvnIntelCorporation:ct9:cvr0.1: dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.10+13.10.20131113-0ubuntu1ppa1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Thu Feb 20 13:53:25 2014 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. evdev: B16_b_02 USB-PS/2 Optical Mouse: Unable to open evdev device /dev/input/event5. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 52268 vendor VSC xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug blank compiz-0.9 saucy screen ubuntu ** Tags added: blank screen ** Description changed: Dear developers! After upgrading from Ubuntu 13.04 to Ubuntu 13.10 x64 the screen always stays on at standard brightness. After specified time it does not go blank. It may cause quicker LED degradation. - I try different settings without a result. + I tried different settings without a result. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: xorg 1:7.7+1ubuntu6 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 .tmp.unity.support.test.0: - + ApportVersion: 2.12.5-0ubuntu2.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 Date: Thu Feb 20 22:05:38 2014 DistUpgraded: Fresh install DistroCodename: saucy DistroVariant: ubuntu DkmsStatus: - bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64: installed - bcmwl, 6.30.223.141+bdcom, 3.11.0-15-generic, x86_64: installed - bcmwl, 6.30.223.141+bdcom, 3.11.0-17-generic, x86_64: installed + bcmwl, 6.30.223.141+bdcom, 3.11.0-12-generic, x86_64:
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Dear members! The fix from ppa:attente/modifier-only-input-switch can't unlock alt+shift for me. It causes Shift+Alt+Next Group shortcut. Ctrl+Shift works normally. Ubuntu upgraded from 13.04 x64 at Lenovo Ideapad Z580A. With best regards. Viktor. -- 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/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in Gnome Settings Daemon: Invalid Status in Ubuntu GNOME: Confirmed Status in “gnome-control-center” package in Ubuntu: Fix Released Status in “gnome-settings-daemon” package in Ubuntu: Triaged Status in “gnome-settings-daemon” source package in Saucy: Triaged Status in “gnome-control-center” package in ALT Linux: Unknown Status in “gnome-control-center” package in Baltix: New Status in “gnome-control-center” package in Gentoo Linux: Invalid Status in “gnome-control-center” package in Mandriva: Invalid Bug description: *** The old PPA, ppa:attente/1218322 is superceded by the following one. You can remove the old repository using ppa-purge. *** A PPA which should provide some relief for this issue is available at https://launchpad.net/~attente/+archive/modifier-only-input-switch. To install: sudo add-apt-repository ppa:attente/modifier-only-input-switch sudo apt-get update sudo apt-get upgrade (log out, log in) If the packages improve the situation for you, you can pin them using: sudo apt-mark hold compiz sudo apt-mark hold gnome-settings-daemon sudo apt-mark hold unity If the packages don't work for you, you can purge them using: sudo ppa-purge ppa:attente/modifier-only-input-switch === compiz === Impact: modifier-only key bindings need to be independent of key-press order, there's no support for double tapping two modifier keys of the same type Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - holding left shift, press and release ctrl - the current input source should change Regression potential: possible, but highly unlikely, that some key bindings may be triggered due to the removal of some code that would normally prevent a possible tap from occurring. === unity === Impact: gnome-settings-daemon eats modifier-only shortcuts preventing them from propagating down to applications Test case: - open gnome-control-center's text input settings - set the next input source key binding to ctrl+left shift - open gnome-terminal - press ctrl+shift+t - gnome-terminal should open a new tab Regression potential: the additional input switch key bindings could collide with other functionality such as opening the dash or hud === gnome-control-center === Impact: the UI to change the layout switching keys doesn't work Test case: - open gnome-control-center's text input settings - click on the next layout key entry - try entering a key combinaison (e.g ctrl-space) - the UI should reflect the new keys Regression potential: that UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) === gnome-settings-daemon === Impact: attempting to change keyboard layouts using only modifier keys doesn't work Test case: - add at least two input sources through gnome-control-center's text entry settings - use gsettings to set the input switching shortcut to ctrl+left shift: gsettings set org.gnome.desktop.wm.keybindings switch-input-source ['PrimaryShift_L'] - press and release ctrl+left shift - the current input source should change Regression potential: The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVEusp=sharing). -- Recent discovered bugs related to keyboard layouts: * keyboard layout settings must be consistent between gnome-control-center keyboard, indicator-keyboard and gnome-tweak-tool and /etc/default/keyboard (bug 1270574) * Ubuntu 14.04 should have gnome-tweak-tool installed by default because of many settings that are missed gnome-control-center (bug 1270572) Separate bug reports for individual layout switching hotkey combinations: Super+Space and
[Desktop-packages] [Bug 1277868] [NEW] Can not edit main menu by Alacarte
Public bug reported: Dear members! Alacarte opens, allows creating or editing menu items, checking or unchecking checkboxes but nothing happen in Classicmenu-Indicator or Classic Ubuntu session. The checkbox state restores after the next Alacarte starting. All new items are lost. System restart is not helpful. This bug is not a Bug #64264 because the system restart is not helpful. The OS is Ubuntu 13.10 x64 updated from 13.04. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alacarte 3.10.0-1 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: Sat Feb 8 15:15:15 2014 InstallationDate: Installed on 2014-02-08 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alacarte (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy ** Description changed: Dear members! Alacarte opens, allows creating or editing menu items, checking or unchecking checkboxes but nothing happen in Classicmenu-Indicator or Classic Ubuntu session. The checkbox state restores after the next Alacarte starting. All new items are lost. System restart is not helpful. + This bug is not a Bug #64264 because the system restart is not helpful. The OS is Ubuntu 13.10 x64 updated from 13.04. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alacarte 3.10.0-1 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: Sat Feb 8 15:15:15 2014 InstallationDate: Installed on 2014-02-08 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alacarte 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 alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1277868 Title: Can not edit main menu by Alacarte Status in “alacarte” package in Ubuntu: New Bug description: Dear members! Alacarte opens, allows creating or editing menu items, checking or unchecking checkboxes but nothing happen in Classicmenu-Indicator or Classic Ubuntu session. The checkbox state restores after the next Alacarte starting. All new items are lost. System restart is not helpful. This bug is not a Bug #64264 because the system restart is not helpful. The OS is Ubuntu 13.10 x64 updated from 13.04. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alacarte 3.10.0-1 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: Sat Feb 8 15:15:15 2014 InstallationDate: Installed on 2014-02-08 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1277868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277868] Re: Can not edit main menu by Alacarte
The back trace is very short. Starting alacarte causes two identical error messages. Creating new items or closing alacarte cause no messages. ** Attachment added: This is a back trace during openning and creating new item. https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1277868/+attachment/3973893/+files/Backtrace_alacarte.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1277868 Title: Can not edit main menu by Alacarte Status in “alacarte” package in Ubuntu: New Bug description: Dear members! Alacarte opens, allows creating or editing menu items, checking or unchecking checkboxes but nothing happen in Classicmenu-Indicator or Classic Ubuntu session. The checkbox state restores after the next Alacarte starting. All new items are lost. System restart is not helpful. This bug is not a Bug #64264 because the system restart is not helpful. The OS is Ubuntu 13.10 x64 updated from 13.04. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alacarte 3.10.0-1 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: Sat Feb 8 15:15:15 2014 InstallationDate: Installed on 2014-02-08 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1277868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1277868] Re: Can not edit main menu by Alacarte
There is the same bugs in ArchLinux https://bugs.archlinux.org/task/37221 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alacarte in Ubuntu. https://bugs.launchpad.net/bugs/1277868 Title: Can not edit main menu by Alacarte Status in “alacarte” package in Ubuntu: New Bug description: Dear members! Alacarte opens, allows creating or editing menu items, checking or unchecking checkboxes but nothing happen in Classicmenu-Indicator or Classic Ubuntu session. The checkbox state restores after the next Alacarte starting. All new items are lost. System restart is not helpful. This bug is not a Bug #64264 because the system restart is not helpful. The OS is Ubuntu 13.10 x64 updated from 13.04. With best regards. Viktor. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alacarte 3.10.0-1 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: Sat Feb 8 15:15:15 2014 InstallationDate: Installed on 2014-02-08 (0 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: alacarte UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1277868/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1111884] Re: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT
It is appears that the bug is FIXED in Ubuntu 13.10 x64. (upgraded from 13.04 x64). lspci -k said that the Nouveau is active. Suspend and resume was successful twice. Tested on Lenovo Ideapad Z580A With best regards. Viktor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/884 Title: 10de:0611 nouveau fails at suspend/resume - PAGE_NOT_PRESENT Status in The Linux Kernel: Invalid Status in Accelerated Xorg driver for nVidia cards: Confirmed Status in “xserver-xorg-video-nouveau” package in Ubuntu: Triaged Bug description: Happens when resuming from standby. Can be reproduced. Every time. nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 00449b nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: , e1c: , e20: 0011, e24: 0c03 nouveau E[ PGRAPH][:05:00.0] TRAP nouveau E[ PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d mthd 0x060c data 0x04b0 nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] magic set 0: nouveau E[ PGRAPH][:05:00.0] 0x00408904: 0x20087701 nouveau E[ PGRAPH][:05:00.0] 0x00408908: 0x00449b00 nouveau E[ PGRAPH][:05:00.0] 0x0040890c: 0x8432 nouveau E[ PGRAPH][:05:00.0] 0x00408910: 0x9b00 nouveau E[ PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 0x0003 nouveau E[ PGRAPH][:05:00.0] TRAP ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-core 2:1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 Date: Thu Jan 31 22:17:49 2013 DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2330] MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago) UserGroups: dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.name: P5WD2-Premium dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.19-0ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.6-0ubuntu2 xserver.bootTime: Thu Jan 31 22:30:57 2013 xserver.configfile: /etc/X11/xorg.conf xserver.devices: input
[Desktop-packages] [Bug 872172] Re: libcanberra-gtk0 should recommend Gtk2 and Gtk3 module to fix: Gtk-Message: Failed to load module canberra-gtk-module
This problem may appear in amd64 system trying to use i386 program.
For me the problem solution is:
sudo apt-get install libcanberra-gtk-module:i386 libcanberra-gtk0:i386
If it does not work try reinstalling libcanberra-gtk0 AT YOUR OWN RISK.
The uninstallation causes removing of possibly very important packets
for You. Please analyze a packet list at step 2. If any problems after
step 3 (power loss or bug) POSSIBLE YOU WILL HAVE A SYSTEM WITHOUT A
DESKTOP.
1. Run but don't confirm at prompt [Y/N]
sudo apt-get remove libcanberra-gtk0
2. Carefully analyze apt-get answer and find a list of packets to be
removed. The lines maybe different from computer to computer. For
example:
Packets to be REMOVED:
gnome-session-canberra gnome-session-fallback libcanberra-gtk-module
libcanberra-gtk0 metacity ubuntu-desktop
If You will not restore these packets possibly You will have great
problems.
3. Copy this packet list to Your favorite text editor
4. Answer Y
5. Run the command after replacing list with saved list (with spaces
between elements) of removed packets at step 3:
sudo apt-get install list libcanberra-gtk0
For previous example
sudo apt-get install gnome-session-canberra gnome-session-fallback
libcanberra-gtk-module
libcanberra-gtk0 metacity ubuntu-desktop libcanberra-gtk0
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcanberra in Ubuntu.
https://bugs.launchpad.net/bugs/872172
Title:
libcanberra-gtk0 should recommend Gtk2 and Gtk3 module to fix: Gtk-
Message: Failed to load module canberra-gtk-module
Status in “libcanberra” package in Ubuntu:
Triaged
Bug description:
Trying to run any Gtk 3 application in Oneiric, I am getting the following
message/error:
% ubuntu-bug
Gtk-Message: Failed to load module canberra-gtk-module
libcanberra-gtk-module only ships this file:
/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so
When setting the GTK_PATH explicitly, it fails to load like this:
% export GTK_PATH=:/usr/lib/gtk-2.0
% ubuntu-bug
(apport-gtk:12816): Gtk-WARNING **: GTK+ module
/usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is
not supported.
Gtk-Message: Failed to load module canberra-gtk-module
The fix/workaround appears to be installing libcanberra-gtk3-module,
or removing libcanberra-gtk-module, which is only being installed as a
recommendation for transmission-gtk (in this case):
% aptitude why libcanberra-gtk-module
i libcanberra-gtk0 Recommends libcanberra-gtk-module
% aptitude search '?depends(libcanberra-gtk0)' | awk '{print $2}'
balsa
gnome-panel
gnome-session-canberra
gnubg
gok
libbrasero-media1
libcanberra-gtk-dev
libcanberra-gtk-module
libcanberra-gtk0-dbg
libcheese-gtk18
metacity
transmission-gtk
wallch
xchat-gnome
I think that libcanberra-gtk0 should not only recommend the Gtk 2 module, but
also the Gtk 3 one.
So the Recommends: libcanberra-gtk-module should become Recommends:
libcanberra-gtk-module, libcanberra-gtk3-module.
WORKAROUND:
1. sudo apt-get install libcanberra-gtk3-module
or
2. sudo apt-get purge libcanberra-gtk-module
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: libcanberra-gtk-module 0.28-0ubuntu10
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Tue Oct 11 10:12:05 2011
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1)
ProcEnviron:
LC_TIME=de_DE.UTF-8
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/usr/bin/zsh
SourcePackage: libcanberra
UpgradeStatus: Upgraded to oneiric on 2011-09-29 (11 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/872172/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1111884] Re: nouveau fails at suspend/resume - PAGE_NOT_PRESENT
Workaround options for hybrid video systems: Option 1. In BIOS switch to use only embedded video card (for example UMA only for Lenovo Ideapad Z580A). Option 2. In BIOS use Optimus video and blacklist nouveau: sudo gedit /etc/modprobe.d/blacklist.conf Add a line to the end of file: blacklist nouveau Save, close file and restart. (sudo rmmod nouveau does not helpful becaude nouveau is in use). Now if required optimus graphic You can run (and disable suspend until next reboot because rmmod does not work): sudo modprobe nouveau -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/884 Title: nouveau fails at suspend/resume - PAGE_NOT_PRESENT Status in The Linux Kernel: New Status in Accelerated Xorg driver for nVidia cards: New Status in “xserver-xorg-video-nouveau” package in Ubuntu: Confirmed Bug description: Happens when resuming from standby. Can be reproduced. Every time. nouveau E[ PFB][:05:00.0] trapped read at 0x002001a020 on channel 0x0001fae9 SEMAPHORE_BG/PFIFO_READ/00 reason: PAGE_NOT_PRESENT nouveau E[ PFB][:05:00.0] trapped write at 0x002001a020 on channel 0x0001fae9 PFIFO/PFIFO_READ/SEMAPHORE reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - Unknown fault at address 00449b nouveau E[ PGRAPH][:05:00.0] TRAP_TPDMA_2D - TP 0 - e0c: , e18: , e1c: , e20: 0011, e24: 0c03 nouveau E[ PGRAPH][:05:00.0] TRAP nouveau E[ PGRAPH][:05:00.0] ch 2 [0x001fae9000] subc 2 class 0x502d mthd 0x060c data 0x04b0 nouveau E[ PFB][:05:00.0] trapped write at 0x00449b on channel 0x0001fae9 PGRAPH/PROP/DST2D reason: PAGE_NOT_PRESENT nouveau E[ PGRAPH][:05:00.0] magic set 0: nouveau E[ PGRAPH][:05:00.0] 0x00408904: 0x20087701 nouveau E[ PGRAPH][:05:00.0] 0x00408908: 0x00449b00 nouveau E[ PGRAPH][:05:00.0] 0x0040890c: 0x8432 nouveau E[ PGRAPH][:05:00.0] 0x00408910: 0x9b00 nouveau E[ PGRAPH][:05:00.0] TRAP_TEXTURE - TP0: Unhandled ustatus 0x0003 nouveau E[ PGRAPH][:05:00.0] TRAP ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: xserver-xorg-core 2:1.13.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-2.6-generic 3.8.0-rc4 Uname: Linux 3.8.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.8-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CrashCounter: 1 Date: Thu Jan 31 22:17:49 2013 DistUpgraded: 2013-01-30 03:34:50,679 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G92 [GeForce 8800 GT] [10de:0611] (rev a2) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Device [1682:2330] MachineType: System manufacturer System Product Name MarkForUpload: True ProcCmdline: /usr/bin/X :0 -core -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch -background none ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-2-generic root=UUID=615f02d8-8bf1-4c07-bf26-9f8b2230d6d6 ro pcie_aspm=force Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so ?? () from /usr/lib/xorg/modules/libexa.so Title: Xorg crashed with SIGABRT UpgradeStatus: Upgraded to raring on 2013-01-30 (1 days ago) UserGroups: dmi.bios.date: 12/24/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.name: P5WD2-Premium dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd12/24/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WD2-Premium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.9~daily13.01.25-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.41-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.2-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati
