[Desktop-packages] [Bug 1983527] [NEW] package libreoffice-common 1:7.3.5-0ubuntu0.22.04.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice-common, o script post-installation
Public bug reported: atualizando o repositorio apt ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.5-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Aug 3 20:55:38 2022 ErrorMessage: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2022-06-30 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.5-0ubuntu0.22.04.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/1983527 Title: package libreoffice-common 1:7.3.5-0ubuntu0.22.04.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice- common, o script post-installation retornou erro do status de saída 10 Status in libreoffice package in Ubuntu: New Bug description: atualizando o repositorio apt ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libreoffice-common 1:7.3.5-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Aug 3 20:55:38 2022 ErrorMessage: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 InstallationDate: Installed on 2022-06-30 (34 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, unpackaged PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 SourcePackage: libreoffice Title: package libreoffice-common 1:7.3.5-0ubuntu0.22.04.1 failed to install/upgrade: o subprocesso instalado, do pacote libreoffice-common, o script post-installation retornou erro do status de saída 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1983527/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 3127] Re: Firefox language settings incorrect for Aus & NZ users
can we close this issue? -- 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/3127 Title: Firefox language settings incorrect for Aus & NZ users Status in firefox package in Ubuntu: Confirmed Bug description: I use a fully updated Dapper Beta. The languages which are in the list by default in Firefox are en-us and en. For New Zealand they should be (in this order): en-nz en-gb en en-us Perhaps the "System -> Administration -> Languages" can be used to prioritise languages etc. to improve the 'one setting, one place' philosophy which Ubuntu is attempting (for example with OOo localisations etc.). Even if the system setting was only used if a profile did not already exist it would be a great start. Two approaches could be taken to this: * the user could manually rank variants of 'English' so that I could set (in System -> Administration -> Languages) the above rankings; or * New Zealand users have the above languages set up for them; or * a section in the languages could allow the ranking manually *and* they default to the above for New Zealanders. Obviously I would like to see the same philosophy applied to all languages. One advantage in doing this may be that programs (synaptic?) could install alternative dictionaries etc. if your first choice was missing. Questions or clarifications, just ask. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/3127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720224] Re: cannot arrange the monitors differently
** Changed in: gnome-control-center (Ubuntu) Status: New => Fix Released -- 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/1720224 Title: cannot arrange the monitors differently Status in gnome-control-center package in Ubuntu: Fix Released Bug description: in the widget display arrangement, one cannot drag a monitor in order to position it on the other side or below the primary screen (using 2 screens) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 21:30:04 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-24 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) 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-control-center/+bug/1720224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716160] Re: System goes to sleep with external monitor and lid closed after login
@khurshid-alam I don't think that a normal user should have to disable stuff after a fresh install i.o. to make ubuntu work. I believe that this should be patched here and the patch should be forwarded upstream. @cagara You seem to have the same problem as I have. Though my problem is deterministic: after login (enter password and enter) I see the desktop for 1 second and then the external monitor & laptop goes sleep. You can wake up the computer by pressing the power button on the docking station. You then have to enter the password and enter again to get into the desktop. The laptop should not sleep anymore. Hope it helps until this is fixed -- 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/1716160 Title: System goes to sleep with external monitor and lid closed after login Status in gdm3 package in Ubuntu: Invalid Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Artful: Invalid Status in gnome-settings-daemon source package in Artful: Fix Released Status in gnome-shell source package in Artful: Invalid Bug description: Using a laptop with lid closed and an external monitor, you can boot. Bios will show on the external monitor, as well as gdm when boot is finished. You can then choose a user and type in your password, which is accepted. But then, system goes to sleep (as the lid is cloesd I guess). Going out of sleep with the power button shows the gnome shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716160] Re: System goes to sleep with external monitor and lid closed after login
Basically is the same issue: I have a life book h760 with a docking station attached to it. The laptop is closed and two external monitors are attached to the docking station. After booting, the GDM appears on the correct monitors. After entering the password, one gets to gnome desktop and the desktop then goes into standby. One has to press the turn on button on the docking station to wake up the laptop. All settings are default. All updates done. As far as I understood this is the exactly reported bug here. The gnome tweak tool is also set to default settings (done nothing there) -- 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/1716160 Title: System goes to sleep with external monitor and lid closed after login Status in gdm3 package in Ubuntu: Invalid Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Artful: Invalid Status in gnome-settings-daemon source package in Artful: Fix Released Status in gnome-shell source package in Artful: Invalid Bug description: Using a laptop with lid closed and an external monitor, you can boot. Bios will show on the external monitor, as well as gdm when boot is finished. You can then choose a user and type in your password, which is accepted. But then, system goes to sleep (as the lid is cloesd I guess). Going out of sleep with the power button shows the gnome shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716160] Re: System goes to sleep with external monitor and lid closed after login
This bug does not seem to be fixed with the release of gnome-settings- daemon (3.26.1-0ubuntu3) artful; urgency=medium Running ubuntu 17.10 will all updates installed and after login with gdm the laptop goes into sleep. Loggin in to Xorg as I have a Nvidia card. Within the gnome tweak tool the setting is to not suspend when the lid is closed. -- 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/1716160 Title: System goes to sleep with external monitor and lid closed after login Status in gdm3 package in Ubuntu: Invalid Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Invalid Status in gdm3 source package in Artful: Invalid Status in gnome-settings-daemon source package in Artful: Fix Released Status in gnome-shell source package in Artful: Invalid Bug description: Using a laptop with lid closed and an external monitor, you can boot. Bios will show on the external monitor, as well as gdm when boot is finished. You can then choose a user and type in your password, which is accepted. But then, system goes to sleep (as the lid is cloesd I guess). Going out of sleep with the power button shows the gnome shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720224] [NEW] cannot arrange the monitors differently
Public bug reported: in the widget display arrangement, one cannot drag a monitor in order to position it on the other side or below the primary screen (using 2 screens) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 21:30:04 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-24 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Picture showing the window" https://bugs.launchpad.net/bugs/1720224/+attachment/4958239/+files/Screenshot%20from%202017-09-28%2021-33-08.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1720224 Title: cannot arrange the monitors differently Status in gnome-control-center package in Ubuntu: New Bug description: in the widget display arrangement, one cannot drag a monitor in order to position it on the other side or below the primary screen (using 2 screens) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 21:30:04 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-09-24 (3 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919) 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-control-center/+bug/1720224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705122] Re: Installed snaps do not appear among other apps in menus when using Wayland
One should also add, that happens to all snap apps, not only telegram. In my case, with atom, and libreoffice packaged by snapcrafters -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705122 Title: Installed snaps do not appear among other apps in menus when using Wayland Status in snapd package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: I installed the snap telegram-sergiusens but it doesn't appear among the other applications in the menu and I can't search for it from the Activities menu (GNOME Shell). I'm trying this from a Wayland session, I don't know if this can be related in any way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: snapd 2.26.10+17.10 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 22:39:57 2017 InstallationDate: Installed on 2015-03-21 (850 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) SourcePackage: snapd UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705122] Re: Installed snaps do not appear among other apps in menus when using Wayland
This is also happening with Ubuntu Gnome 17.04. Only in wayland session, in x11 its okay -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1705122 Title: Installed snaps do not appear among other apps in menus when using Wayland Status in snapd package in Ubuntu: Confirmed Status in wayland package in Ubuntu: Confirmed Bug description: I installed the snap telegram-sergiusens but it doesn't appear among the other applications in the menu and I can't search for it from the Activities menu (GNOME Shell). I'm trying this from a Wayland session, I don't know if this can be related in any way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: snapd 2.26.10+17.10 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 18 22:39:57 2017 InstallationDate: Installed on 2015-03-21 (850 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150321) SourcePackage: snapd UpgradeStatus: Upgraded to artful on 2017-07-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1705122/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1210470] Re: Switching to integrated card with vgaswitcheroo makes the kernel to hang, until pulseaudio is killed
Okay, switching off the HDMI sound card in pavucontrol works for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1210470 Title: Switching to integrated card with vgaswitcheroo makes the kernel to hang, until pulseaudio is killed Status in The Linux Kernel: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I have a dual-GPU notebook, with a Intel Ironlake integrated GPU and a AMD 5650m dedicated GPU (muxed system). The AMD gpu is also connected to an HDMI port that implies an audio card (I'm running radeon module with radeon.audio=1). If I switch to the integrated card after that the UI is up and pulseaudio is loaded, as soon as I exit from lightdm (both to reload X or to shutdown the PC) the kernel hangs (both in 12.10, 13.04 and 13.10): [ 489.177732] hda-intel :01:00.1: Disabling via VGA-switcheroo [ 489.297129] hda-intel :01:00.1: Cannot lock devices! [ 489.297139] radeon: switched off [ 489.300356] [drm] Disabling audio support [ 489.319552] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0015e418 and cpu addr 0xc90009df0418 [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0 [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C3DC (len 871, WS 0, PS 0) @ 0xC439 [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.514458] init: tty1 main process (2460) killed by QUIT signal [ 699.514489] init: tty1 main process ended, respawning [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 At the contrary, if once lightdm starts I go to tty1 → sudo service lighdm stop → sudo killall pulseaudio → echo OFF| sudo tee /sys/kernel/debug/vgaswitcheroo/switch #switch to integrated card Everything works well instead. So it seems that pulseaudio should disable the powered-off card on switch (or is this something that the kernel should do?). To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1210470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1310260] Re: Pulseaudio fails to detect card (probably due to hybrid graphics)
I found the simplest workaround: switching off the HDMI sound card in pavucontrol. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1310260 Title: Pulseaudio fails to detect card (probably due to hybrid graphics) Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: Hi, I wanted to install Trusty on my Elitebook 850 G1 with hybrid graphics (Intel / AMD) but pulseaudio goes nuts on me as soon as I try to play any music / sound, try to change volume, etc. I've tried it with Ubuntu, Kubuntu and now with Xubuntu with the same result everytime. My guess is that pulseaudio has problems with the AMD GPU and it's sound processor being switched off automatically as enabled by Kernel 3.13 (formerly achieved by adding the radeon.runpm=1 kernel parameter) (http://lists.freedesktop.org/archives/dri-devel/2013-September/045650.html) root@HP-EliteBook-850-G1:~# cat /sys/kernel/debug/vgaswitcheroo/switch 0:IGD:+:Pwr::00:02.0 1:DIS: :DynOff::03:00.0 2:DIS-Audio: :Off::03:00.1 As you can see, the AMD GPU has been turned off automatically. Pulseaudio, the (X)Ubuntu volume applet and KMix on the other hand list it as still available. Based on that I asume pulseaudio tries to access a switched-off device and fails. I've followed the steps listed here: https://wiki.ubuntu.com/DebuggingSoundProblems and here: https://wiki.ubuntu.com/PulseAudio/Log I'll attach the logs right away. (pulseverbose1.log and my dmesg output) Pusleverbose is full of messages like this one: ( 0.013| 0.000) I: [pulseaudio] alsa-util.c: Error opening PCM device hw:0: No such file or directory This output of dmesg also caught my attention: [ 354.927935] HDMI ATI/AMD: no speaker allocation for ELD [ 357.695010] hda-intel :03:00.1: Disabling via VGA-switcheroo One thing I noticed using Kubuntu is that after pulseaudio becomes unresponsive the taskmanager lists 4 pulseaudio processes two of which are active on harddrive (Aktiv auf Festplatte). Those two processes cannot be killed even as root. Currently being on Xubuntu the same thing is true, although it lists only one process in the taskmanager that cannot be killed. I hope you can help me. Best regards, Paul ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC2', '/dev/snd/hwC2D0', '/dev/snd/pcmC2D3p', '/dev/snd/pcmC2D7p', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Sun Apr 20 13:47:09 2014 InstallationDate: Installed on 2014-04-20 (0 days ago) InstallationMedia: Xubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [HP EliteBook 850 G1, IDT 92HD91BXX, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.08 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.54 dmi.chassis.asset.tag: CNU345BY96 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.08:bd02/19/2014:svnHewlett-Packard:pnHPEliteBook850G1:pvrA3008CC10003:rvnHewlett-Packard:rn198F:rvrKBCVersion15.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 850 G1 dmi.product.version: A3008CC10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1310260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1210470] Re: Switching to integrated card with vgaswitcheroo makes the kernel to hang, until pulseaudio is killed
I am currently experiencing the issue described by Garri. Any fix or workaround yet? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1210470 Title: Switching to integrated card with vgaswitcheroo makes the kernel to hang, until pulseaudio is killed Status in The Linux Kernel: Confirmed Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: I have a dual-GPU notebook, with a Intel Ironlake integrated GPU and a AMD 5650m dedicated GPU (muxed system). The AMD gpu is also connected to an HDMI port that implies an audio card (I'm running radeon module with radeon.audio=1). If I switch to the integrated card after that the UI is up and pulseaudio is loaded, as soon as I exit from lightdm (both to reload X or to shutdown the PC) the kernel hangs (both in 12.10, 13.04 and 13.10): [ 489.177732] hda-intel :01:00.1: Disabling via VGA-switcheroo [ 489.297129] hda-intel :01:00.1: Cannot lock devices! [ 489.297139] radeon: switched off [ 489.300356] [drm] Disabling audio support [ 489.319552] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x0015e418 and cpu addr 0xc90009df0418 [ 489.973886] ACPI: \_SB_.PCI0: ACPI_NOTIFY_BUS_CHECK event: unsupported [ 489.973903] _handle_hotplug_event_root: Bus check notify on \_SB_.PCI0 [ 678.992375] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 678.992453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996303] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 683.996377] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 683.996453] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing C3DC (len 871, WS 0, PS 0) @ 0xC439 [ 689.000275] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 689.000349] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 694.004285] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 694.004363] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.008330] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 699.008414] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 699.514458] init: tty1 main process (2460) killed by QUIT signal [ 699.514489] init: tty1 main process ended, respawning [ 704.012405] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 704.012492] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 [ 709.016515] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting [ 709.016596] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CD0C (len 62, WS 0, PS 0) @ 0xCD28 At the contrary, if once lightdm starts I go to tty1 → sudo service lighdm stop → sudo killall pulseaudio → echo OFF| sudo tee /sys/kernel/debug/vgaswitcheroo/switch #switch to integrated card Everything works well instead. So it seems that pulseaudio should disable the powered-off card on switch (or is this something that the kernel should do?). To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1210470/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
@Chris Done: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1080882 -- 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/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window Status in “xorg-server” package in Ubuntu: In Progress Status in “xorg-server” source package in Precise: In Progress Status in “xorg-server” source package in Quantal: In Progress Bug description: When I plug my SB Arena USB headset in, I can't click the mouse in any window besides the one with focus. The current window works ok, but any other doesn't register the click. Also, I get a BUG in the X logs. This on Precise, xserver-xorg-input-evdev version 1:2.7.0-0ubuntu1 /var/log/Xorg.0.log: on device insert: [252903.181] (II) config/udev: Adding input device Creative Technology SB Arena Headset (/dev/input/event9) [252903.181] (**) Creative Technology SB Arena Headset: Applying InputClass evdev keyboard catchall [252903.181] (II) Using input driver 'evdev' for 'Creative Technology SB Arena Headset' [252903.181] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [252903.181] (**) Creative Technology SB Arena Headset: always reports core events [252903.181] (**) evdev: Creative Technology SB Arena Headset: Device: /dev/input/event9 [252903.181] (--) evdev: Creative Technology SB Arena Headset: Vendor 0x41e Product 0x403 [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found 8 mouse buttons [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found keys [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as mouse [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as keyboard [252903.181] (**) evdev: Creative Technology SB Arena Headset: YAxisMapping: buttons 4 and 5 [252903.181] (**) evdev: Creative Technology SB Arena Headset: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [252903.181] (**) Option config_info udev:/sys/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.3/input/input18/event9 [252903.181] (II) XINPUT: Adding extended input device Creative Technology SB Arena Headset (type: KEYBOARD, id 15) [252903.181] (**) Option xkb_rules evdev [252903.181] (**) Option xkb_model pc105 [252903.181] (**) Option xkb_layout us [252903.191] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [252903.191] Backtrace: [252903.192] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866] [252903.192] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe] [252903.192] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d] [252903.192] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202] [252903.192] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d] [252903.192] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed] [252903.192] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1486989000+0x5f48) [0x7f148698ef48] [252903.192] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07] [252903.192] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a] [252903.192] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) [0x7f148d8a0cb0] [252903.192] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f148c7f0803] [252903.192] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b] [252903.192] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2] [252903.192] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa] [252903.192] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f148c72676d] [252903.192] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d] on removal: [252937.048] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [252937.048] Backtrace: [252937.048] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866] [252937.048] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe] [252937.048] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d] [252937.048] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202] [252937.048] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d] [252937.048] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed] [252937.048] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1486989000+0x5f48) [0x7f148698ef48] [252937.048] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07] [252937.048] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a] [252937.048] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) [0x7f148d8a0cb0] [252937.048] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f148c7f0803] [252937.048] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b] [252937.049] 12: /usr/bin/X
[Desktop-packages] [Bug 1080882] [NEW] Creative HS-950 USB headset causes X BUG, can't click outside window
Public bug reported: Bug is similar to this one: https://bugs.launchpad.net/ubuntu/+source /xorg-server/+bug/1007575 Pulseaudio usually crashes on login (if the headset is plugged) or when a sound is played. The only way to be able to click outside the active window is to unplug the headset. /var/log/Xorg.0.log: [34.792] (II) config/udev: Adding input device Creative Technology Creative USB Headset (/dev/input/event6) [34.792] (**) Creative Technology Creative USB Headset: Applying InputClass evdev keyboard catchall [34.792] (II) Using input driver 'evdev' for 'Creative Technology Creative USB Headset' [34.792] (**) Creative Technology Creative USB Headset: always reports core events [34.792] (**) evdev: Creative Technology Creative USB Headset: Device: /dev/input/event6 [34.792] (--) evdev: Creative Technology Creative USB Headset: Vendor 0x41e Product 0x400 [34.792] (--) evdev: Creative Technology Creative USB Headset: Found 8 mouse buttons [34.792] (--) evdev: Creative Technology Creative USB Headset: Found keys [34.792] (II) evdev: Creative Technology Creative USB Headset: Forcing relative x/y axes to exist. [34.792] (II) evdev: Creative Technology Creative USB Headset: Configuring as mouse [34.792] (II) evdev: Creative Technology Creative USB Headset: Configuring as keyboard [34.792] (**) evdev: Creative Technology Creative USB Headset: YAxisMapping: buttons 4 and 5 [34.792] (**) evdev: Creative Technology Creative USB Headset: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [34.792] (**) Option config_info udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input14/event6 [34.793] (II) XINPUT: Adding extended input device Creative Technology Creative USB Headset (type: KEYBOARD, id 11) [34.793] (**) Option xkb_rules evdev [34.793] (**) Option xkb_model pc105 [34.793] (**) Option xkb_layout pt [35.200] (II) config/udev: removing device Creative Technology Creative USB Headset [35.204] (II) evdev: Creative Technology Creative USB Headset: Close [35.204] (II) UnloadModule: evdev [35.552] (II) config/udev: Adding input device Creative Technology Creative USB Headset (/dev/input/event6) [35.552] (**) Creative Technology Creative USB Headset: Applying InputClass evdev keyboard catchall [35.552] (II) Using input driver 'evdev' for 'Creative Technology Creative USB Headset' [35.552] (**) Creative Technology Creative USB Headset: always reports core events [35.552] (**) evdev: Creative Technology Creative USB Headset: Device: /dev/input/event6 [35.552] (--) evdev: Creative Technology Creative USB Headset: Vendor 0x41e Product 0x400 [35.552] (--) evdev: Creative Technology Creative USB Headset: Found 8 mouse buttons [35.552] (--) evdev: Creative Technology Creative USB Headset: Found keys [35.552] (II) evdev: Creative Technology Creative USB Headset: Forcing relative x/y axes to exist. [35.552] (II) evdev: Creative Technology Creative USB Headset: Configuring as mouse [35.552] (II) evdev: Creative Technology Creative USB Headset: Configuring as keyboard [35.552] (**) evdev: Creative Technology Creative USB Headset: YAxisMapping: buttons 4 and 5 [35.552] (**) evdev: Creative Technology Creative USB Headset: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [35.552] (**) Option config_info udev:/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.3/input/input15/event6 [35.552] (II) XINPUT: Adding extended input device Creative Technology Creative USB Headset (type: KEYBOARD, id 11) [35.552] (**) Option xkb_rules evdev [35.552] (**) Option xkb_model pc105 [35.552] (**) Option xkb_layout pt [ 2988.170] (II) config/udev: removing device Creative Technology Creative USB Headset [ 2988.172] (II) evdev: Creative Technology Creative USB Headset: Close [ 2988.172] (II) UnloadModule: evdev [ 2989.779] (II) config/udev: Adding input device Creative Technology Creative USB Headset (/dev/input/event6) [ 2989.779] (**) Creative Technology Creative USB Headset: Applying InputClass evdev keyboard catchall [ 2989.779] (II) Using input driver 'evdev' for 'Creative Technology Creative USB Headset' [ 2989.779] (**) Creative Technology Creative USB Headset: always reports core events [ 2989.779] (**) evdev: Creative Technology Creative USB Headset: Device: /dev/input/event6 [ 2989.780] (--) evdev: Creative Technology Creative USB Headset: Vendor 0x41e Product 0x400 [ 2989.780] (--) evdev: Creative Technology Creative USB Headset: Found 8 mouse buttons [ 2989.780] (--) evdev: Creative Technology Creative USB Headset: Found keys [ 2989.780] (II) evdev: Creative Technology Creative USB Headset: Forcing relative x/y axes to exist. [ 2989.780] (II) evdev: Creative Technology Creative USB Headset: Configuring as mouse [ 2989.780] (II) evdev: Creative
[Desktop-packages] [Bug 1007575] Re: SB Arena USB headset causes X BUG, can't click outside window
I have the same issue with a Creative HS-950 headset, should I report a new bug? -- 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/1007575 Title: SB Arena USB headset causes X BUG, can't click outside window Status in “xorg-server” package in Ubuntu: In Progress Status in “xorg-server” source package in Precise: In Progress Status in “xorg-server” source package in Quantal: In Progress Bug description: When I plug my SB Arena USB headset in, I can't click the mouse in any window besides the one with focus. The current window works ok, but any other doesn't register the click. Also, I get a BUG in the X logs. This on Precise, xserver-xorg-input-evdev version 1:2.7.0-0ubuntu1 /var/log/Xorg.0.log: on device insert: [252903.181] (II) config/udev: Adding input device Creative Technology SB Arena Headset (/dev/input/event9) [252903.181] (**) Creative Technology SB Arena Headset: Applying InputClass evdev keyboard catchall [252903.181] (II) Using input driver 'evdev' for 'Creative Technology SB Arena Headset' [252903.181] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so [252903.181] (**) Creative Technology SB Arena Headset: always reports core events [252903.181] (**) evdev: Creative Technology SB Arena Headset: Device: /dev/input/event9 [252903.181] (--) evdev: Creative Technology SB Arena Headset: Vendor 0x41e Product 0x403 [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found 8 mouse buttons [252903.181] (--) evdev: Creative Technology SB Arena Headset: Found keys [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as mouse [252903.181] (II) evdev: Creative Technology SB Arena Headset: Configuring as keyboard [252903.181] (**) evdev: Creative Technology SB Arena Headset: YAxisMapping: buttons 4 and 5 [252903.181] (**) evdev: Creative Technology SB Arena Headset: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 [252903.181] (**) Option config_info udev:/sys/devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.3/input/input18/event9 [252903.181] (II) XINPUT: Adding extended input device Creative Technology SB Arena Headset (type: KEYBOARD, id 15) [252903.181] (**) Option xkb_rules evdev [252903.181] (**) Option xkb_model pc105 [252903.181] (**) Option xkb_layout us [252903.191] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [252903.191] Backtrace: [252903.192] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866] [252903.192] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe] [252903.192] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d] [252903.192] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202] [252903.192] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d] [252903.192] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed] [252903.192] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1486989000+0x5f48) [0x7f148698ef48] [252903.192] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07] [252903.192] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a] [252903.192] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) [0x7f148d8a0cb0] [252903.192] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f148c7f0803] [252903.192] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b] [252903.192] 12: /usr/bin/X (0x7f148e56b000+0x4e4f2) [0x7f148e5b94f2] [252903.192] 13: /usr/bin/X (0x7f148e56b000+0x3d6aa) [0x7f148e5a86aa] [252903.192] 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xed) [0x7f148c72676d] [252903.192] 15: /usr/bin/X (0x7f148e56b000+0x3d99d) [0x7f148e5a899d] on removal: [252937.048] BUG: triggered 'if (!dev-valuator || dev-valuator-numAxes 2)' BUG: ../../dix/getevents.c:850 in scale_to_desktop() [252937.048] Backtrace: [252937.048] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f148e6f3866] [252937.048] 1: /usr/bin/X (0x7f148e56b000+0x621fe) [0x7f148e5cd1fe] [252937.048] 2: /usr/bin/X (0x7f148e56b000+0x62e6d) [0x7f148e5cde6d] [252937.048] 3: /usr/bin/X (GetPointerEvents+0xe2) [0x7f148e5cf202] [252937.048] 4: /usr/bin/X (QueuePointerEvents+0x1d) [0x7f148e5cf65d] [252937.048] 5: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f148e60b5ed] [252937.048] 6: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1486989000+0x5f48) [0x7f148698ef48] [252937.048] 7: /usr/bin/X (0x7f148e56b000+0x8ae07) [0x7f148e5f5e07] [252937.048] 8: /usr/bin/X (0x7f148e56b000+0xb0d4a) [0x7f148e61bd4a] [252937.048] 9: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f148d891000+0xfcb0) [0x7f148d8a0cb0] [252937.048] 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f148c7f0803] [252937.048] 11: /usr/bin/X (WaitForSomething+0x19b) [0x7f148e6f0c4b] [252937.049] 12: /usr/bin/X
