[Desktop-packages] [Bug 1857191] Re: Dark themes don't work well with highlighted current line in gedit
The solution in https://bugs.launchpad.net/ubuntu/+source/gtksourceview4/+bug/1887311 also works for me. Could this please be changed in Ubuntu? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtksourceview4 in Ubuntu. https://bugs.launchpad.net/bugs/1857191 Title: Dark themes don't work well with highlighted current line in gedit Status in GtkSourceView: New Status in gtksourceview4 package in Ubuntu: Triaged Status in yaru-theme package in Ubuntu: Confirmed Bug description: In order to checkout out an old bug report I started gedit, enabled "Highlight current line" and changed the application theme to "Yaru- dark" The current line is highlighted correctly but the text is unreadable because it is too light. The text needs to be much darker. This is not a theme that I would normally use so I'm not too bothered about how the problem is fixed but this configuration makes gedit very difficult to use as you can't actually see the text that you're adding, changing or deleting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 19.10.4 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Dec 21 16:33:03 2019 InstallationDate: Installed on 2019-05-17 (218 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: Upgraded to focal on 2019-11-08 (42 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gtksourceview/+bug/1857191/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@robin Windey
I had no luck with kernel 5.10.2, try 5.9.16
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-40-g
[Desktop-packages] [Bug 1909347] [NEW] Keyboard layout used in the second place breaks keymap
Public bug reported: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1909347 Title: Keyboard layout used in the second place breaks keymap Status in xkeyboard-config package in Ubuntu: New Bug description: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1909347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909347] Re: Keyboard layout used in the second place breaks keymap
** Also affects: gnome-control-center Importance: Undecided Status: New ** No longer affects: xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1909347 Title: Keyboard layout used in the second place breaks keymap Status in gnome-control-center: New Bug description: It's hard to really summarize the issue here. If you use the Neo2 layout somewhere, the keymap becomes garbled in a very specific way (see below). I am not really sure if it affects other keyboard layouts or what happens internally. I have selected gnome-control-center as the affected package, because this is, where it all starts. There are two issues, which are somehow connected. Reproduction steps (first issue): 1. Open "Region & Language Settings" in gnome-control-center 2. In "Input Sources" use "German (no dead keys)" in the FIRST place and "German (Neo 2)" in the second place (order matters!) 3. Open your favorite text editor 4. Use Super+Alt+Backspace to change to the Neo2 layout 5. Press and hold the Mod4 key (right of Left Shift) and 3. 6. You get a 3, expected would be №. Reproduction steps (second issue): 1. Go back to the "Region & Language Settings" and now use "German (Neo 2)" in the FIRST place and "German (no dead keys)" in the SECOND place 2. Open Chromium and open any web page (it does not work with any other application) 3. Use Super+Alt+Backspace to change to "German (no dead keys)" layout 4. Press Ctrl+F 5. Instead of the In-Page-Search opening, you go to the search bar, which means that the input is interpreted as Ctrl+E instead of Ctrl+F. If you press Ctrl+I (which is Ctrl+F on Neo2), the search bar opens, which means that even though Neo2 is selected, the old keymap is still somehow active. Info: 1) Release: Ubuntu 20.04.1 LTS 2) gnome-control-center: Installed: 1:3.36.4-0ubuntu2 3/4) See reproduction steps above To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1909347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909351] [NEW] gnome shell cpu
Public bug reported: >From time to time gnome-shell cpu percentage spikes on Ubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 08:11:11 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (211 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-26 (60 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1909351 Title: gnome shell cpu Status in gnome-shell package in Ubuntu: New Bug description: From time to time gnome-shell cpu percentage spikes on Ubuntu 20.10. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17 Uname: Linux 5.8.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 08:11:11 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-29 (211 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to groovy on 2020-10-26 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1909351/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 820092] Re: Title
** Summary changed: - [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all + Title -- 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/820092 Title: [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all Status in ALSA driver: New Status in alsa-driver package in Ubuntu: Invalid Bug description: My onboard front audio (headphones) does not work in Ubuntu, but does work in Windows. These are my sound devices: == Onboard SigmaTel/IDT STAC9227 audio codec == 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) Subsystem: Intel Corporation Device a201 Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel == Offboard Genius SM-Live Value 5.1 sound card == 04:00.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device Kernel driver in use: C-Media PCI Kernel modules: snd-cmipci ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renato 1485 F pulseaudio /dev/snd/pcmC0D0p: renato 1485 F...m pulseaudio /dev/snd/controlC1: renato 1485 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9020 irq 43' Mixer name : 'SigmaTel STAC9227' Components : 'HDA:83847618,8086a201,00100201' Controls : 26 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'CMI8738'/'C-Media CMI8738 (model 55) at 0x1100, irq 21' Mixer name : 'CMedia PCI' Components : '' Controls : 41 Simple ctrls : 22 CurrentDmesg: [ 30.704011] eth0: no IPv6 routers present Date: Tue Aug 2 19:43:07 2011 PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Áudio interno - HDA Intel Symptom_DevicesInUse: 1485 1485 1485 renatoF...m pulseaudio /dev/snd/controlC1: renatoF pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [, SigmaTel STAC9227, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to natty on 2011-06-19 (44 days ago) dmi.bios.date: 11/07/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: TS94610J.86A.0087.2007.1107.1049 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D946GZIS dmi.board.vendor: Intel Corporation dmi.board.version: AAD66165-301 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrTS94610J.86A.0087.2007.1107.1049:bd11/07/2007:svn:pn:pvr:rvnIntelCorporation:rnD946GZIS:rvrAAD66165-301:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/820092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 818680] Re: Title
** Summary changed: - [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front + Title -- 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/818680 Title: [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front Status in alsa-driver package in Ubuntu: Invalid Bug description: My onboard front audio (headphones) only starts working after plugging in some connector in the rear jacks, then reconnecting the front audio. I can then plug out the rear connector as headphones started working. Doesn't happen in Windows. These are my sound devices: == Onboard SigmaTel/IDT STAC9227 audio codec == 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) Subsystem: Intel Corporation Device a201 Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel == Offboard Genius SM-Live Value 5.1 sound card == 04:00.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device Kernel driver in use: C-Media PCI Kernel modules: snd-cmipci ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: renato 1547 F pulseaudio /dev/snd/pcmC1D0p: renato 1547 F...m pulseaudio /dev/snd/controlC0: renato 1547 F pulseaudio Card0.Amixer.info: Card hw:0 'CMI8738'/'C-Media CMI8738 (model 55) at 0x1100, irq 21' Mixer name : 'CMedia PCI' Components : '' Controls : 41 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'Intel'/'HDA Intel at 0x9020 irq 44' Mixer name : 'SigmaTel STAC9227' Components : 'HDA:83847618,8086a201,00100201' Controls : 26 Simple ctrls : 17 CurrentDmesg: [ 30.040069] eth0: no IPv6 routers present [ 30.160907] Adding 1048572k swap on /swap. Priority:-1 extents:806 across:1262728k Date: Sat Jul 30 20:47:22 2011 PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Áudio interno - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, SigmaTel STAC9227, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to natty on 2011-06-19 (41 days ago) dmi.bios.date: 11/07/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: TS94610J.86A.0087.2007.1107.1049 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D946GZIS dmi.board.vendor: Intel Corporation dmi.board.version: AAD66165-301 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrTS94610J.86A.0087.2007.1107.1049:bd11/07/2007:svn:pn:pvr:rvnIntelCorporation:rnD946GZIS:rvrAAD66165-301:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/818680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 256670] Re: Title
** Summary changed: - When you click a JAR the current directoy should be that of the JAR, not your home + Title -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/256670 Title: When you click a JAR the current directoy should be that of the JAR, not your home Status in Unity: Invalid Status in nautilus package in Ubuntu: New Status in openjdk-7 package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: When I click on a a jar (open it with Java) which reads some external file, it tries to find it under my home instead of the folder where the jar is located (Windows behavior). However, if I run $java -jar app.jar it works. That is: when you click the jar, you'd expect the current directory being that in front of your face, not anywhere else, like your home. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/256670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 256670] Re: When you click a JAR the current directoy should be that of the JAR, not your home
** Summary changed: - Title + When you click a JAR the current directoy should be that of the JAR, not your home -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/256670 Title: When you click a JAR the current directoy should be that of the JAR, not your home Status in Unity: Invalid Status in nautilus package in Ubuntu: New Status in openjdk-7 package in Ubuntu: New Status in unity package in Ubuntu: Invalid Bug description: When I click on a a jar (open it with Java) which reads some external file, it tries to find it under my home instead of the folder where the jar is located (Windows behavior). However, if I run $java -jar app.jar it works. That is: when you click the jar, you'd expect the current directory being that in front of your face, not anywhere else, like your home. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/256670/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 820092] Re: [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all
** Summary changed: - Title + [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all -- 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/820092 Title: [SigmaTel STAC9227, Green Headphone Out, Front] No sound at all Status in ALSA driver: New Status in alsa-driver package in Ubuntu: Invalid Bug description: My onboard front audio (headphones) does not work in Ubuntu, but does work in Windows. These are my sound devices: == Onboard SigmaTel/IDT STAC9227 audio codec == 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) Subsystem: Intel Corporation Device a201 Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel == Offboard Genius SM-Live Value 5.1 sound card == 04:00.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device Kernel driver in use: C-Media PCI Kernel modules: snd-cmipci ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renato 1485 F pulseaudio /dev/snd/pcmC0D0p: renato 1485 F...m pulseaudio /dev/snd/controlC1: renato 1485 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0x9020 irq 43' Mixer name : 'SigmaTel STAC9227' Components : 'HDA:83847618,8086a201,00100201' Controls : 26 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'CMI8738'/'C-Media CMI8738 (model 55) at 0x1100, irq 21' Mixer name : 'CMedia PCI' Components : '' Controls : 41 Simple ctrls : 22 CurrentDmesg: [ 30.704011] eth0: no IPv6 routers present Date: Tue Aug 2 19:43:07 2011 PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Áudio interno - HDA Intel Symptom_DevicesInUse: 1485 1485 1485 renatoF...m pulseaudio /dev/snd/controlC1: renatoF pulseaudio Symptom_Jack: Green Headphone Out, Front Symptom_Type: No sound at all Title: [, SigmaTel STAC9227, Green Headphone Out, Front] No sound at all UpgradeStatus: Upgraded to natty on 2011-06-19 (44 days ago) dmi.bios.date: 11/07/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: TS94610J.86A.0087.2007.1107.1049 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D946GZIS dmi.board.vendor: Intel Corporation dmi.board.version: AAD66165-301 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrTS94610J.86A.0087.2007.1107.1049:bd11/07/2007:svn:pn:pvr:rvnIntelCorporation:rnD946GZIS:rvrAAD66165-301:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/820092/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 818680] Re: [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front
** Summary changed: - Title + [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front -- 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/818680 Title: [SigmaTel STAC9227, Green Headphone Out, Front] Sound only after plugging in connector in the rear then reconnecting front Status in alsa-driver package in Ubuntu: Invalid Bug description: My onboard front audio (headphones) only starts working after plugging in some connector in the rear jacks, then reconnecting the front audio. I can then plug out the rear connector as headphones started working. Doesn't happen in Windows. These are my sound devices: == Onboard SigmaTel/IDT STAC9227 audio codec == 00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 01) Subsystem: Intel Corporation Device a201 Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel == Offboard Genius SM-Live Value 5.1 sound card == 04:00.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) Subsystem: C-Media Electronics Inc CMI8738/C3DX PCI Audio Device Kernel driver in use: C-Media PCI Kernel modules: snd-cmipci ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-base 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7 Uname: Linux 2.6.38-10-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: renato 1547 F pulseaudio /dev/snd/pcmC1D0p: renato 1547 F...m pulseaudio /dev/snd/controlC0: renato 1547 F pulseaudio Card0.Amixer.info: Card hw:0 'CMI8738'/'C-Media CMI8738 (model 55) at 0x1100, irq 21' Mixer name : 'CMedia PCI' Components : '' Controls : 41 Simple ctrls : 22 Card1.Amixer.info: Card hw:1 'Intel'/'HDA Intel at 0x9020 irq 44' Mixer name : 'SigmaTel STAC9227' Components : 'HDA:83847618,8086a201,00100201' Controls : 26 Simple ctrls : 17 CurrentDmesg: [ 30.040069] eth0: no IPv6 routers present [ 30.160907] Adding 1048572k swap on /swap. Priority:-1 extents:806 across:1262728k Date: Sat Jul 30 20:47:22 2011 PackageArchitecture: all ProcEnviron: LANGUAGE=pt_BR:en LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel successful Symptom_Card: Áudio interno - HDA Intel Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [, SigmaTel STAC9227, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to natty on 2011-06-19 (41 days ago) dmi.bios.date: 11/07/2007 dmi.bios.vendor: Intel Corp. dmi.bios.version: TS94610J.86A.0087.2007.1107.1049 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: D946GZIS dmi.board.vendor: Intel Corporation dmi.board.version: AAD66165-301 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrTS94610J.86A.0087.2007.1107.1049:bd11/07/2007:svn:pn:pvr:rvnIntelCorporation:rnD946GZIS:rvrAAD66165-301:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/818680/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909352] [NEW] (1) video hangs or (2) screen goes blank and case fan turns on
Public bug reported: Recover system by press and release reset switch. Log in again. Had these issues with Ubuntu 18.04. Updated to Nvidia drivers and issues resolved. Updated to 20.04.1 and issues have returned. Checked and see that Nvidia drivers newer than those packaged for use. Available at Nvidia / Newest package and in use: GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.45 - Release Date: Tue Nov 17, 2020 GeForce Game Ready Driver LINUX X64 (AMD64/EM64T) DISPLAY DRIVER Driver Version: 455.38 - Release Date: Thu Oct 29, 2020 Hopefully the command ubuntu-bug xorg attached all the information you may need. $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 09:54:40 2020 DistUpgraded: 2020-10-02 13:11:28,665 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-56-generic, x86_64: installed nvidia, 455.38, 5.4.0-58-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2018-03-03 (1029 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Gigabyte Technology Co., Ltd. AB350-Gaming 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=fc7c6eeb-fbb0-4f6c-8815-349d9ff6efd6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-02 (84 days ago) dmi.bios.date: 08/18/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: Default string dmi.board.name: AB350-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd08/18/2017:svnGigabyteTechnologyCo.,Ltd.:pnAB350-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat Dec 26 08:48:35 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1909352 Title: (1) video hangs or (2) screen goes blank and case fan turns on Status in xorg package in Ubuntu: New Bug description: Recover system by press and release reset switch. Log in again. Had these issues with Ubuntu 18.04. Updated to Nvidia drivers and issues resolved. Updated to 20.04.1 and iss
[Desktop-packages] [Bug 1909372] [NEW] PS2 mouse stopped working the upgrade before this one, still not working. FIX IT PLS!
Public bug reported: Last upgrade, having the PS2 mouse connected caused Ubuntu 20.04.1 to lock up the computer on a black screen. ASUS Mobo, Quad core AMD, 64-bit; 1 TB WD HDD. Mobo is a circa 2014 so still well within it's life. Withdrawing support for PS2 equipment at this EARLY stage makes us computer owners wonder why as there's no reason to do that this early. They are still making and selling brand new PS2 mice and keyboards! This bug likely applies to PS2 keyboards as well though I didn't test that. This upgrade, first one since Ubuntu stopped supporting PS2 equipmnet a couple three weeks ago (it's 12/26/20 today), it didn't lock up the computer this time so that was fixed, but PS2 mice still don't work!?? Why?? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 26 13:09:17 2020 InstallationDate: Installed on 2018-05-09 (962 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-26T13:05:25.187611 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1909372 Title: PS2 mouse stopped working the upgrade before this one, still not working. FIX IT PLS! Status in evince package in Ubuntu: New Bug description: Last upgrade, having the PS2 mouse connected caused Ubuntu 20.04.1 to lock up the computer on a black screen. ASUS Mobo, Quad core AMD, 64-bit; 1 TB WD HDD. Mobo is a circa 2014 so still well within it's life. Withdrawing support for PS2 equipment at this EARLY stage makes us computer owners wonder why as there's no reason to do that this early. They are still making and selling brand new PS2 mice and keyboards! This bug likely applies to PS2 keyboards as well though I didn't test that. This upgrade, first one since Ubuntu stopped supporting PS2 equipmnet a couple three weeks ago (it's 12/26/20 today), it didn't lock up the computer this time so that was fixed, but PS2 mice still don't work!?? Why?? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.7-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 26 13:09:17 2020 InstallationDate: Installed on 2018-05-09 (962 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LD_PRELOAD= SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-12-26T13:05:25.187611 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1909372/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1851621] Re: [snap] No KDE file dialogs
1. Is it fixed in 20.10? 2. If not, is there a proper package anywhere instead of a broken snap? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1851621 Title: [snap] No KDE file dialogs Status in chromium-browser package in Ubuntu: Confirmed Bug description: I upgraded from kubuntu 19.04 to 19.10 and noticed that chromium does not integrate anymore. Plasma integration Fails to connect to the native host (suggested google solutions didn't work), Kubuntu mouse pointers change to ugly ones (I bellive GTK fallback), no kde file dialog when opening/saving files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
(In reply to Jeff Gilbert [:jgilbert] from comment #18) > After bug 1680595, it should be more clear to (power) users what they can do > to mitigate this. > > Functionality here is, I think, working as intended now. Unfortunately the > specified behavior causes certain websites (which arguably may have made poor > choices) work worse for our users, whereas before things were maybe slower > than they could have been, but otherwise functional. > > With that in mind, since we're now following failIfMajorPerformanceCaveat > spec properly, it's causing breakage. This bug is tracking the user > pain-point. In order to solve the user pain-point, we might ditch > failIfMajorPerformanceCaveat as accidentally-user=hostile for the time being. > > Two choices: > 1. Call these bad websites, and try outreach/education > 2. Re-evaluate the failIfMajorPerformanceCaveat mechanism entirely Is there a bug/explanation somewhere of what behavior changed with failIfMajorPerformanceCaveat in FF83? -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905054]
> Call these bad websites, and try outreach/education How do I call Google? Also since they haven't fixed it until now, I doubt they ever will. Is there some hack to make it work? An user script? -- 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/1905054 Title: Firefox 83 Breaks WebGL Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Committed Bug description: Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working. Ubuntu 20.10 with Wayland. When I try to launch a webGL game: Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated. Specifically Pixi says: Error: WebGL unsupported in this browser, use "pixi.js-legacy" for fallback canvas2d support. Downgrading to Firefox 82 works. Not sure if this is an Ubuntu build issue or Firefox, so I also filed upstream as well: https://bugzilla.mozilla.org/show_bug.cgi?id=1678652 I need this functionality for work, and pinning to version 82 will be problematic in the long-term. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1905054/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@koen (kmaris) , with kernel 5.10.2 ,you can try #311
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-40-gene
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
and #311 also work with kernel 5.10.3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (#296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work. Before the
release of v5.11, you are suggested to use #189 to save your touchpad.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-40-generic N/A
linux-ba
[Desktop-packages] [Bug 373113]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- 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/373113 Title: [upstream] Writer imports Hebrew Word .doc file and missing some text after page break Status in LibreOffice: Confirmed Status in OpenOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.3.2-1ubuntu5 Candidate: 1:3.3.2-1ubuntu5 Version table: *** 1:3.3.2-1ubuntu5 0 500 http://us.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.3.2-1ubuntu4 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/main i386 Packages 3) What is expected to happen in LibreOffice Writer via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/373113/+attachment/2154880/+files/example.doc && lowriter -nologo example.doc Search for the word "סיכום המחקרים", LO finds it and highlights it. 4) What happens instead is it finds it, but does not highlight it. As well, the text does not appear in the document. WORKAROUND: Convert the document to .odt: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/373113/+attachment/2154880/+files/example.doc && unoconv --listener && unoconv -f odt example.doc && lowriter -nologo example.odt apt-cache policy unoconv unoconv: Installed: 0.3-6 Candidate: 0.3-6 Version table: *** 0.3-6 0 500 http://us.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages 100 /var/lib/dpkg/status Original Reporter Comments: It's a Microsoft Word document. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: openoffice.org-core 1:3.0.1-9ubuntu3 ProcEnviron: PATH=(custom, user) LANG=he_IL.UTF-8 SHELL=/bin/bash SourcePackage: openoffice.org Uname: Linux 2.6.28-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/373113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901538] Re: Output Device selection messed (Line Out <-> HDMI)
[Expired for gnome-control-center (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Expired -- 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/1901538 Title: Output Device selection messed (Line Out <-> HDMI) Status in gnome-control-center package in Ubuntu: Expired Bug description: [System] - Freshly installed Ubuntu 20.04.1 LTS with 3rd party software/drivers enabled - pulseaudio 1:13.99.1-1ubuntu3.7 - NVIDIA graphics card (GeForce GTX 650 Ti Boost) using nvidia-driver-450 - Monitor with build-in (stereo) speakers connected via HDMI to graphics card - External (stereo) speakers connected via audio jack to mainboard [Expected Behavior] 1. Go to "Settings" -> "Sound" -> "Output" -> "Output Device" 2. Switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" 3. The switching should enable the chosen output device. [Bug Description and Behavior] If I switch from "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" to "Line Out - Built-in Audio" and test the output, sound comes still from monitor speakers and not from my external speakers. [Workaround] While "HDMI / DisplayPort 2 - GK106 HDMI Audio Controller" selected, go to "Configuration" and switch from "Digital Stereo (HDMI 2) Output" to "Digital Surround 5.1 (HDMI 2) Output". Instantly "Configuration" row disappears, in Output Device "Line Out - Built-in Audio" is selected and external speakers are active. [Further comments] I'm affected by this bug and the "wrong audio output on every reboot/wake up/login" since upgrade to 20.04 but the latter may be worth another bug report or maybe you could guide me to an active bug report that isn't linked to a previous Ubuntu version and already marked as fixed. At first I thought it may be caused by failed upgrade or my system configurations, but now I tested with a freshly installed Ubuntu on a spare SSD and the problem still exists, so here I am. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 26 13:15:41 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) 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/1901538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901192] Re: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1
[Expired for tex-common (Ubuntu) because there has been no activity for 60 days.] ** Changed in: tex-common (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/1901192 Title: package tex-common 6.13 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 1 Status in tex-common package in Ubuntu: Expired Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: tex-common 6.13 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 23 15:30:29 2020 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2012-08-30 (2976 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: tex-common Title: package tex-common 6.13 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1901192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1897281] Re: evince suicides in 20.04 but not in 18.04
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 Status in evince package in Ubuntu: Expired Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Evince does a suicide trip after unsuccessfully trying to open a CBR file. After a while it is killed. Here is my terminal output: $ evince TheCartoons.cbr Killed $ And between the line "$ evince TheCartoons.cbr" and the final "Killed", are passing many minutes. Please note that I started my report in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060 not knowing exactly what "expired" there means. I did "apport-collect 1785060" there, too. Please note also that my error message (see above) is quite different from seb128 in bug 1785060. In fact, there is no error message just the statement "Killed". What gets me is that in 18.04 it is working so smooth and fast and that in 20.04 it is such a mess! P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, testing), evince loads and opens this CBR file correctly, albeit slowly, but okular (installed in Buster sid) yields a similar error message like that of seb128 with evince in bug 1785060: "Could not open file TheCartoons.cbr. The version of unrar on your system is not suitable for opening comicbooks" Inverted world ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1545103] Re: Xorg crashed with SIGABRT in raise()
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1545103 Title: Xorg crashed with SIGABRT in raise() Status in xorg-server package in Ubuntu: Expired Bug description: Fresh install of Ubuntu MATE 16.04 daily ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1 Uname: Linux 4.4.0-4-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Fri Feb 12 19:03:47 2016 ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2016-02-12 (0 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160212) ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server StacktraceTop: raise () from /lib/x86_64-linux-gnu/libc.so.6 abort () from /lib/x86_64-linux-gnu/libc.so.6 OsAbort () ?? () FatalError () Title: Xorg crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1545103/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543706] Re: Xorg crashed with SIGABRT in OsAbort()
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1543706 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Expired Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CrashCounter: 1 Date: Tue Feb 9 18:52:43 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (284 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x561b1e194f00, argc=11, argv=0x7ffe3ea4ad98, init=, fini=, rtld_fini=, stack_end=0x7ffe3ea4ad88) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Tue Feb 9 18:53:14 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 4380 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543706/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1543141] Re: Xorg crashed with SIGABRT in OsAbort()
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1543141 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Expired Bug description: No idea what happened. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Feb 8 15:13:42 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21da] InstallationDate: Installed on 2015-04-30 (283 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 429149G ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic root=UUID=457973fc-512e-4b6a-b65b-85f15fa85b7b ro console=tty1 console=ttyS0 panic=-1 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x55d6b3954f00, argc=11, argv=0x7fffef9c7a88, init=, fini=, rtld_fini=, stack_end=0x7fffef9c7a78) at libc-start.c:289 SystemImageInfo: Error: command ['system-image-cli', '-i'] failed with exit code 2: Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET46WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 429149G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET46WW(1.16):bd05/18/2011:svnLENOVO:pn429149G:pvrThinkPadX220:rvnLENOVO:rn429149G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 429149G dmi.product.version: ThinkPad X220 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20151211-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.66-2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.1-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.1-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160127-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 xserver.bootTime: Mon Feb 8 15:15:16 2016 xserver.configfile: default xserver.errors: systemd-logind: failed to get session: PID 970 does not belong to any known session xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1543141/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1544252] Re: Xorg crashed with SIGABRT in OsAbort()
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1544252 Title: Xorg crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: Expired Bug description: upgraded from chromeos to a galliumos kernel, then dist-upgrade to stock ubuntu kernel ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.17.3-2ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 Date: Wed Feb 10 14:31:34 2016 ExecutablePath: /usr/lib/xorg/Xorg InstallationDate: Installed on 2016-02-09 (1 days ago) InstallationMedia: GalliumOS 1.0beta1 "Vivid Vervet" - Release amd64 (20151109.1) ProcCmdline: /usr/lib/xorg/Xorg -nolisten tcp -core -auth /var/run/slim.auth Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () __libc_start_main (main=0x55f7df0d4f00, argc=6, argv=0x7ffdc6e3d9a8, init=, fini=, rtld_fini=, stack_end=0x7ffdc6e3d998) at libc-start.c:289 Title: Xorg crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to xenial on 2016-02-10 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1544252/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909387] [NEW] Xorg crash (libinput related) on middle mouse click with firefox icognito window
Public bug reported:
What happens:
==
Xorg crashes, all unsaved data will be lost.
Reproduce
==
I can't reproduce it on demand. But it happens after a while.
- Usually I browse within a Firefox incognito window and use my middle mouse
button.
- In todays particular case, I pressed the middle mouse button to close a
window.
- Note: I have `EasyStroke` setup to run on middle-mouse-button click (Program
to enable mouse gestures). From experience, I strongly believe this is related.
- Maybe `suspend`ing the computer several times is related to this problem.
Backtrace
==
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c0/8b99fc7191c25e710bd8e607615730e39962fe.debug...
[New LWP 1106]
[New LWP 1092]
[New LWP 1094]
[New LWP 1093]
[New LWP 1096]
[New LWP 978]
[New LWP 1097]
[New LWP 1098]
[New LWP 1095]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
570 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7fd057816640 (LWP 1106))]
(gdb) bt full
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
pPointer = 0x0
pScreenPriv = 0x56198f0b2eb0
#1 0x56198e979d2c in miPointerSetPosition
(pDev=pDev@entry=0x56198f5dc280, mode=mode@entry=0,
screenx=screenx@entry=0x7fd057814500, screeny=screeny@entry=0x7fd057814508,
nevents=nevents@entry=0x7fd0578144fc, events=events@entry=0x7fd069d6bc20)
at ../../../../mi/mipointer.c:669
pScreenPriv =
pScreen = 0x56198f0b2810
newScreen = 0x7fd0004d
x = 981
y = 77
switch_screen = 0
should_constrain_barriers = 1
i =
pPointer = 0x56198f2249a0
#2 0x56198e840e90 in positionSprite
(dev=dev@entry=0x56198f5dc280, mode=mode@entry=0,
mask=mask@entry=0x7fd057814550, devx=devx@entry=0x7fd057814510,
devy=devy@entry=0x7fd057814518, screenx=screenx@entry=0x7fd057814500,
screeny=0x7fd057814508, nevents=0x7fd0578144fc, events=0x7fd069d6bc20) at
../../../../dix/getevents.c:961
scr =
tmpx = 981.15761067398421
tmpy = 77.59964237213
#3 0x56198e84141c in positionSprite
(events=0x7fd069d6bc20, nevents=0x7fd0578144fc, screeny=0x7fd057814508,
screenx=0x7fd057814500, devy=0x7fd057814518, devx=0x7fd057814510,
mask=0x7fd057814550, mode=0, dev=0x56198f5dc280) at
../../../../dix/getevents.c:952
scr = 0x56198f0b2810
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
--Type for more, q to quit, c to continue without paging--
num_barrier_events = 0
#4 fill_pointer_events (events=0x7fd069d6bc20,
events@entry=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=6,
buttons=buttons@entry=0, ms=ms@entry=60064638, flags=flags@entry=10,
mask_in=0x7fd057814860) at ../../../../dix/getevents.c:1434
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#5 0x56198e842b60 in GetPointerEvents
(events=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=,
type@entry=6, buttons=buttons@entry=0, flags=10, flags@entry=1,
mask_in=)
at ../../../../dix/getevents.c:1691
ms = 60064638
num_events = 0
nev_tmp =
mask =
{last_bit = 1 '\001', has_unaccelerated = 1 '\001', mask =
"\003\000\000\000", valuators = {-2.399463558197, 1.599642372131, 0
}, unaccelerated = {-3, 2, 0 }}
scroll =
{last_bit = -80 '\260', has_unaccelerated = 10 '\n', mask =
"^\217\031V", valuators = {6.9432427613873832e-310, 6.9432427614211773e-310,
2.0899290387728175e-314, 4.677209760723779e-310, 6.9432533155416236e-310, 0,
-3, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, -2.399463558197, 1.599642372131, 0,
-1.866843107
[Desktop-packages] [Bug 1909387] Re: Xorg crash (libinput related) on middle mouse click with firefox icognito window
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909387/+attachment/5447148/+files/XorgLogOld.txt
--
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/1909387
Title:
Xorg crash (libinput related) on middle mouse click with firefox
icognito window
Status in xorg package in Ubuntu:
New
Bug description:
What happens:
==
Xorg crashes, all unsaved data will be lost.
Reproduce
==
I can't reproduce it on demand. But it happens after a while.
- Usually I browse within a Firefox incognito window and use my middle mouse
button.
- In todays particular case, I pressed the middle mouse button to close a
window.
- Note: I have `EasyStroke` setup to run on middle-mouse-button click
(Program to enable mouse gestures). From experience, I strongly believe this is
related.
- Maybe `suspend`ing the computer several times is related to this problem.
Backtrace
==
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c0/8b99fc7191c25e710bd8e607615730e39962fe.debug...
[New LWP 1106]
[New LWP 1092]
[New LWP 1094]
[New LWP 1093]
[New LWP 1096]
[New LWP 978]
[New LWP 1097]
[New LWP 1098]
[New LWP 1095]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
570 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7fd057816640 (LWP 1106))]
(gdb) bt full
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
pPointer = 0x0
pScreenPriv = 0x56198f0b2eb0
#1 0x56198e979d2c in miPointerSetPosition
(pDev=pDev@entry=0x56198f5dc280, mode=mode@entry=0,
screenx=screenx@entry=0x7fd057814500, screeny=screeny@entry=0x7fd057814508,
nevents=nevents@entry=0x7fd0578144fc, events=events@entry=0x7fd069d6bc20)
at ../../../../mi/mipointer.c:669
pScreenPriv =
pScreen = 0x56198f0b2810
newScreen = 0x7fd0004d
x = 981
y = 77
switch_screen = 0
should_constrain_barriers = 1
i =
pPointer = 0x56198f2249a0
#2 0x56198e840e90 in positionSprite
(dev=dev@entry=0x56198f5dc280, mode=mode@entry=0,
mask=mask@entry=0x7fd057814550, devx=devx@entry=0x7fd057814510,
devy=devy@entry=0x7fd057814518, screenx=screenx@entry=0x7fd057814500,
screeny=0x7fd057814508, nevents=0x7fd0578144fc, events=0x7fd069d6bc20) at
../../../../dix/getevents.c:961
scr =
tmpx = 981.15761067398421
tmpy = 77.59964237213
#3 0x56198e84141c in positionSprite
(events=0x7fd069d6bc20, nevents=0x7fd0578144fc, screeny=0x7fd057814508,
screenx=0x7fd057814500, devy=0x7fd057814518, devx=0x7fd057814510,
mask=0x7fd057814550, mode=0, dev=0x56198f5dc280) at
../../../../dix/getevents.c:952
scr = 0x56198f0b2810
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
--Type for more, q to quit, c to continue without paging--
num_barrier_events = 0
#4 fill_pointer_events (events=0x7fd069d6bc20,
events@entry=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=6,
buttons=buttons@entry=0, ms=ms@entry=60064638, flags=flags@entry=10,
mask_in=0x7fd057814860) at ../../../../dix/getevents.c:1434
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#5 0x56198e842b60 in GetPointerEvents
(events=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=,
type@entry=6, buttons=buttons@entry=0, flags=10, flags@entry=1,
mask_in=)
at ../../../../dix/
[Desktop-packages] [Bug 1909387] Re: Xorg crash (libinput related) on middle mouse click with firefox icognito window
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909387/+attachment/5447149/+files/XorgLog.txt
--
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/1909387
Title:
Xorg crash (libinput related) on middle mouse click with firefox
icognito window
Status in xorg package in Ubuntu:
New
Bug description:
What happens:
==
Xorg crashes, all unsaved data will be lost.
Reproduce
==
I can't reproduce it on demand. But it happens after a while.
- Usually I browse within a Firefox incognito window and use my middle mouse
button.
- In todays particular case, I pressed the middle mouse button to close a
window.
- Note: I have `EasyStroke` setup to run on middle-mouse-button click
(Program to enable mouse gestures). From experience, I strongly believe this is
related.
- Maybe `suspend`ing the computer several times is related to this problem.
Backtrace
==
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c0/8b99fc7191c25e710bd8e607615730e39962fe.debug...
[New LWP 1106]
[New LWP 1092]
[New LWP 1094]
[New LWP 1093]
[New LWP 1096]
[New LWP 978]
[New LWP 1097]
[New LWP 1098]
[New LWP 1095]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
570 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7fd057816640 (LWP 1106))]
(gdb) bt full
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
pPointer = 0x0
pScreenPriv = 0x56198f0b2eb0
#1 0x56198e979d2c in miPointerSetPosition
(pDev=pDev@entry=0x56198f5dc280, mode=mode@entry=0,
screenx=screenx@entry=0x7fd057814500, screeny=screeny@entry=0x7fd057814508,
nevents=nevents@entry=0x7fd0578144fc, events=events@entry=0x7fd069d6bc20)
at ../../../../mi/mipointer.c:669
pScreenPriv =
pScreen = 0x56198f0b2810
newScreen = 0x7fd0004d
x = 981
y = 77
switch_screen = 0
should_constrain_barriers = 1
i =
pPointer = 0x56198f2249a0
#2 0x56198e840e90 in positionSprite
(dev=dev@entry=0x56198f5dc280, mode=mode@entry=0,
mask=mask@entry=0x7fd057814550, devx=devx@entry=0x7fd057814510,
devy=devy@entry=0x7fd057814518, screenx=screenx@entry=0x7fd057814500,
screeny=0x7fd057814508, nevents=0x7fd0578144fc, events=0x7fd069d6bc20) at
../../../../dix/getevents.c:961
scr =
tmpx = 981.15761067398421
tmpy = 77.59964237213
#3 0x56198e84141c in positionSprite
(events=0x7fd069d6bc20, nevents=0x7fd0578144fc, screeny=0x7fd057814508,
screenx=0x7fd057814500, devy=0x7fd057814518, devx=0x7fd057814510,
mask=0x7fd057814550, mode=0, dev=0x56198f5dc280) at
../../../../dix/getevents.c:952
scr = 0x56198f0b2810
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
--Type for more, q to quit, c to continue without paging--
num_barrier_events = 0
#4 fill_pointer_events (events=0x7fd069d6bc20,
events@entry=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=6,
buttons=buttons@entry=0, ms=ms@entry=60064638, flags=flags@entry=10,
mask_in=0x7fd057814860) at ../../../../dix/getevents.c:1434
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#5 0x56198e842b60 in GetPointerEvents
(events=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=,
type@entry=6, buttons=buttons@entry=0, flags=10, flags@entry=1,
mask_in=)
at ../../../../dix/geteve
[Desktop-packages] [Bug 1909387] Re: Xorg crash (libinput related) on middle mouse click with firefox icognito window
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909387/+attachment/5447147/+files/CurrentDmesg.txt
--
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/1909387
Title:
Xorg crash (libinput related) on middle mouse click with firefox
icognito window
Status in xorg package in Ubuntu:
New
Bug description:
What happens:
==
Xorg crashes, all unsaved data will be lost.
Reproduce
==
I can't reproduce it on demand. But it happens after a while.
- Usually I browse within a Firefox incognito window and use my middle mouse
button.
- In todays particular case, I pressed the middle mouse button to close a
window.
- Note: I have `EasyStroke` setup to run on middle-mouse-button click
(Program to enable mouse gestures). From experience, I strongly believe this is
related.
- Maybe `suspend`ing the computer several times is related to this problem.
Backtrace
==
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c0/8b99fc7191c25e710bd8e607615730e39962fe.debug...
[New LWP 1106]
[New LWP 1092]
[New LWP 1094]
[New LWP 1093]
[New LWP 1096]
[New LWP 978]
[New LWP 1097]
[New LWP 1098]
[New LWP 1095]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth
/var/run/lightdm/root/:0 -noliste'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
570 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7fd057816640 (LWP 1106))]
(gdb) bt full
#0 miPointerMoveNoEvent (pDev=pDev@entry=0x56198f5dc280,
pScreen=pScreen@entry=0x56198f0b2810, x=981, y=77)
at ../../../../mi/mipointer.c:570
pPointer = 0x0
pScreenPriv = 0x56198f0b2eb0
#1 0x56198e979d2c in miPointerSetPosition
(pDev=pDev@entry=0x56198f5dc280, mode=mode@entry=0,
screenx=screenx@entry=0x7fd057814500, screeny=screeny@entry=0x7fd057814508,
nevents=nevents@entry=0x7fd0578144fc, events=events@entry=0x7fd069d6bc20)
at ../../../../mi/mipointer.c:669
pScreenPriv =
pScreen = 0x56198f0b2810
newScreen = 0x7fd0004d
x = 981
y = 77
switch_screen = 0
should_constrain_barriers = 1
i =
pPointer = 0x56198f2249a0
#2 0x56198e840e90 in positionSprite
(dev=dev@entry=0x56198f5dc280, mode=mode@entry=0,
mask=mask@entry=0x7fd057814550, devx=devx@entry=0x7fd057814510,
devy=devy@entry=0x7fd057814518, screenx=screenx@entry=0x7fd057814500,
screeny=0x7fd057814508, nevents=0x7fd0578144fc, events=0x7fd069d6bc20) at
../../../../dix/getevents.c:961
scr =
tmpx = 981.15761067398421
tmpy = 77.59964237213
#3 0x56198e84141c in positionSprite
(events=0x7fd069d6bc20, nevents=0x7fd0578144fc, screeny=0x7fd057814508,
screenx=0x7fd057814500, devy=0x7fd057814518, devx=0x7fd057814510,
mask=0x7fd057814550, mode=0, dev=0x56198f5dc280) at
../../../../dix/getevents.c:952
scr = 0x56198f0b2810
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
--Type for more, q to quit, c to continue without paging--
num_barrier_events = 0
#4 fill_pointer_events (events=0x7fd069d6bc20,
events@entry=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=6,
buttons=buttons@entry=0, ms=ms@entry=60064638, flags=flags@entry=10,
mask_in=0x7fd057814860) at ../../../../dix/getevents.c:1434
num_events = 2
event =
raw = 0x7fd069d6b010
screenx = 981.15761067398421
screeny = 77.59964237213
devx = 981.15761067398421
devy = 77.59964237213
sx =
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {981.15761067398421, 77.59964237213, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#5 0x56198e842b60 in GetPointerEvents
(events=0x7fd069d6b010, pDev=pDev@entry=0x56198f5dc280, type=,
type@entry=6, buttons=buttons@entry=0, flags=10, flags@entry=1,
mask_in=)
at ../../../../
