[Touch-packages] [Bug 1954742] Re: Sound starts delayed (4sec) when using HDMI audio
Apparently there was a problem with the sample output rate. I had to `set both default-sample-rate and alternate-sample-rate to 48000 in /etc/pulse/daemon.conf` Apparently switching the output sample rate for devices takes about 4 seconds. Details: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305#note_1197529 My personal problem is solved by applying the specific configuration. Open questions: (1) Could the problem of "it takes 4 seconds to change output sampling rate" be a general problem that should be solved (where? in pulseaudio?). (2) Or should Ubuntu deliver with a defined output sample rate in `/etc/pulse/daemon.conf`? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1954742 Title: Sound starts delayed (4sec) when using HDMI audio Status in pulseaudio package in Ubuntu: New Bug description: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1954742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954742] Re: Sound starts delayed (4sec) when using HDMI audio
Thank you (especially for the direct link)! https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305 (btw: Would be nice, if ubuntu-bug or launchpad could propose upstream reporting when trying to create an issue.) ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #1305 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1305 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1954742 Title: Sound starts delayed (4sec) when using HDMI audio Status in pulseaudio package in Ubuntu: New Bug description: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1954742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1954742] [NEW] Sound starts delayed (4sec) when using HDMI audio
Public bug reported: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description:Ubuntu 21.10 Release:21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1954742 Title: Sound starts delayed (4sec) when using HDMI audio Status in pulseaudio package in Ubuntu: New Bug description: Reproduce: - Connect notebook to external monitor via HDMI - Start random video in youtube / vlc player Actual: - Sound starts with about 4secs of delay Reproducible: always Misc: The package is just a guess. lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 apt-cache policy pulseaudio pulseaudio: Installed: 1:15.0+dfsg1-1ubuntu2.2 Candidate: 1:15.0+dfsg1-1ubuntu2.2 Version table: *** 1:15.0+dfsg1-1ubuntu2.2 1 (phased 20%) 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1:15.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nimono 2373 F pulseaudio /dev/snd/pcmC0D3p: nimono 2373 F...m pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Tue Dec 14 15:20:56 2021 SourcePackage: pulseaudio UpgradeStatus: Upgraded to impish on 2021-12-08 (6 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:sku: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2021-12-08T10:02:48.239277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1954742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)
I set it to new. I had the same problem. I feel this should be universally solved. Related question: https://askubuntu.com/questions/1379811/usrmerge-of- bin-sbin-lib-how-is-the-system-supposed-to-be Perhaps related bug: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=945582 - Is `/usr/lib/usrmerge/convert-usrmerge` really the solution users are supposed to run? - Some systems have the whole directory /bin linked to /usr/bin, this is not what convert-usrmerge appears to do. This inconsistence should be explained and the "right" solution should be announced. I worked around my failing upgrade via - edit `/var/lib/dpkg/info/systemd.postinst` by hand - find the line `systemd-machine-id-setup` - comment it out - run `sudo dpkg --configure -a` again ** Bug watch added: Debian Bug tracker #945582 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945582 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1938065 Title: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10) Status in systemd package in Ubuntu: New Bug description: This happened when trying to upgrade from 21.04 to 21.10. Setting up systemd (248.3-1ubuntu2) ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 Processing triggers for initramfs-tools (0.140ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic Processing triggers for libc-bin (2.33-0ubuntu7) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for dbus (1.12.20-2ubuntu1) ... Errors were encountered while processing: systemd I reverted to old version by manualing installing the hirsute's debs (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb systemd_247.3-3ubuntu3.4_amd64.deb libnss- systemd_247.3-3ubuntu3.4_amd64.deb libsystemd- dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb libpam-systemd_247.3-3ubuntu3.4_amd64.deb libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev- dev_247.3-3ubuntu3.4_amd64.deb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)
** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1938065 Title: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10) Status in systemd package in Ubuntu: New Bug description: This happened when trying to upgrade from 21.04 to 21.10. Setting up systemd (248.3-1ubuntu2) ... systemd-machine-id-setup: error while loading shared libraries: libsystemd-shared-247.so: cannot open shared object file: No such file or directory dpkg: error processing package systemd (--configure): installed systemd package post-installation script subprocess returned error exit status 127 Processing triggers for initramfs-tools (0.140ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic Processing triggers for libc-bin (2.33-0ubuntu7) ... Processing triggers for man-db (2.9.4-2) ... Processing triggers for dbus (1.12.20-2ubuntu1) ... Errors were encountered while processing: systemd I reverted to old version by manualing installing the hirsute's debs (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb systemd_247.3-3ubuntu3.4_amd64.deb libnss- systemd_247.3-3ubuntu3.4_amd64.deb libsystemd- dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb libpam-systemd_247.3-3ubuntu3.4_amd64.deb libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev- dev_247.3-3ubuntu3.4_amd64.deb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935786] Re: `systemctl list-units --type=service` does not list user services
1) The help says `list-units [PATTERN...] List units currently in memory`. I would interpret this as "list all services" 2) General/OT Is there any specific reason, why there is no direct command so far, that lists all services? The differentiation between user and non-user here looks to me like a technical one, instead of a UX-driven one. In case (1) is not seen as a valid argument, perhaps a feature request is a good idea? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1935786 Title: `systemctl list-units --type=service` does not list user services Status in systemd package in Ubuntu: Invalid Bug description: Steps to reproduce: - (on XUbuntu) - Install redshift - Remove redshift (gtk) from autostart ( Menu -> session and startup -> Application Autostart ) - [Redshift will be installed as a service under `/usr/lib/systemd/user`] - Reboot - [Redshift will be started in the background] - Run `systemctl list-units --type=service` - EXPECTED: redshift is inside the list ACTUAL: redshift is not listed - FYI (perhaps another bug): Also, `systemctl --user disable redshift.service` wouldn't help disabling it. Description: Ubuntu 21.04 Release: 21.04 systemd: Installed: 247.3-3ubuntu3.2 Candidate: 247.3-3ubuntu3.2 Version table: *** 247.3-3ubuntu3.2 500 500 http://archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 247.3-3ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 247.3-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.2 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Jul 12 08:09:32 2021 MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-24-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows 2015" resume=UUID=bdfdad69-4c0d-4b99-a962-d88c977da8a3 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-06-05 (36 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1935786] [NEW] `systemctl list-units --type=service` does not list user services
Public bug reported: Steps to reproduce: - (on XUbuntu) - Install redshift - Remove redshift (gtk) from autostart ( Menu -> session and startup -> Application Autostart ) - [Redshift will be installed as a service under `/usr/lib/systemd/user`] - Reboot - [Redshift will be started in the background] - Run `systemctl list-units --type=service` - EXPECTED: redshift is inside the list ACTUAL: redshift is not listed - FYI (perhaps another bug): Also, `systemctl --user disable redshift.service` wouldn't help disabling it. Description:Ubuntu 21.04 Release:21.04 systemd: Installed: 247.3-3ubuntu3.2 Candidate: 247.3-3ubuntu3.2 Version table: *** 247.3-3ubuntu3.2 500 500 http://archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 247.3-3ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 247.3-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.2 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Jul 12 08:09:32 2021 MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-24-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows 2015" resume=UUID=bdfdad69-4c0d-4b99-a962-d88c977da8a3 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-06-05 (36 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1935786 Title: `systemctl list-units --type=service` does not list user services Status in systemd package in Ubuntu: New Bug description: Steps to reproduce: - (on XUbuntu) - Install redshift - Remove redshift (gtk) from autostart ( Menu -> session and startup -> Application Autostart ) - [Redshift will be installed as a service under `/usr/lib/systemd/user`] - Reboot - [Redshift will be started in the background] - Run `systemctl list-units --type=service` - EXPECTED: redshift is inside the list ACTUAL: redshift is not listed - FYI (perhaps another bug): Also, `systemctl --user disable redshift.service` wouldn't help disabling it. Description: Ubuntu 21.04 Release: 21.04 systemd: Installed: 247.3-3ubuntu3.2 Candidate: 247.3-3ubuntu3.2 Version table: *** 247.3-3ubuntu3.2 500 500 http://archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 Packages 100 /var/lib/dpkg/status 247.3-3ubuntu3.1 500 500 http://archive.ubuntu.com/ubuntu hirsute-updates/main amd64 Packages 247.3-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu hirsute/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.3-3ubuntu3.2 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Mon Jul 12 08:09:32 2021 MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-24-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows 2015" resume=UUID=bdfdad69-4c0d-4b99-a962-d88c977da8a3 SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2021-06-05 (36 days ago) dmi.bios.date: 01/23/2018 dmi.bios.release: 1.7 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:br1.7:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935786/+subscriptions -- Mailing list: https:
[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart
+ Added the PPA and installed, now ibus stays "on" after openning the dialog. 👍️ - `ibus restart` still doesnt work: "Can't connect to IBus" Would be nice to also have a cmd-line option working for this case. FYI: Btw: here's another reason for quitting/restarting ibus: if I call `killall python3` on my machine, ibus/anthy (?) seems to get into an inconsistent state, which prevents input on certain apps. I guess the reason for this is somehow connected to what I've described earlier. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927813] Re: Whoopsie working is blocking shutdown
I'd like to emphasize, that this bug results in the disability to shutdown and therefore enforces a hardware shutdown in certain situation. I reported it a little while ago, but it's present for several years. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1927813 Title: Whoopsie working is blocking shutdown Status in whoopsie package in Ubuntu: New Bug description: Summary In case there is a crashing application as a result of the shutdown command (Menu -> shutdown ), the shutdown process hangs with the message: `A stop job is running for crash report submission daemon ( [x]s / 1min 30s)` Steps to reproduce == - Start an application, that will crash on computer-shutdown (I use easystrokes or VIPole). - Shutdown computer via menu (not command line (might work as well, but untested)) - EXPECTED: computer shuts down quickly; possible crash reports will be sent the next time the computer gets shut down - or EXPECTED WORKAROUND: The waiting process can be canceled by Ctrl+C - ACTUAL: The user can only wait. Cancellation (Ctrl+C / Ctrl+\) won't work. Only hardware shutdown can cancel the process. Note Aside from whoopsie specifically, this waiting period with no cancellation is a general problem, I think. In case several processes prevent the shutdown like whoopsie does, the user has to wait several minutes (about 15min in one extreme case). A solution for this general problem would be the introduction of a screen to allow users to hard-shutdown any program (like MS Windows does). lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 apt-cache policy whoopsie === whoopsie: Installed: 0.2.72.2 Candidate: 0.2.72.2 Version table: *** 0.2.72.2 500 500 http://archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu groovy-security/main amd64 Packages 100 /var/lib/dpkg/status 0.2.72 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72.2 ProcVersionSignature: Ubuntu 5.8.0-52.59-generic 5.8.18 Uname: Linux 5.8.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat May 8 16:01:13 2021 RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1927813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1927813] [NEW] Whoopsie working is blocking shutdown
Public bug reported: Summary In case there is a crashing application as a result of the shutdown command (Menu -> shutdown ), the shutdown process hangs with the message: `A stop job is running for crash report submission daemon ( [x]s / 1min 30s)` Steps to reproduce == - Start an application, that will crash on computer-shutdown (I use easystrokes or VIPole). - Shutdown computer via menu (not command line (might work as well, but untested)) - EXPECTED: computer shuts down quickly; possible crash reports will be sent the next time the computer gets shut down - or EXPECTED WORKAROUND: The waiting process can be canceled by Ctrl+C - ACTUAL: The user can only wait. Cancellation (Ctrl+C / Ctrl+\) won't work. Only hardware shutdown can cancel the process. Note Aside from whoopsie specifically, this waiting period with no cancellation is a general problem, I think. In case several processes prevent the shutdown like whoopsie does, the user has to wait several minutes (about 15min in one extreme case). A solution for this general problem would be the introduction of a screen to allow users to hard-shutdown any program (like MS Windows does). lsb_release -rd === Description:Ubuntu 20.10 Release:20.10 apt-cache policy whoopsie === whoopsie: Installed: 0.2.72.2 Candidate: 0.2.72.2 Version table: *** 0.2.72.2 500 500 http://archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu groovy-security/main amd64 Packages 100 /var/lib/dpkg/status 0.2.72 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72.2 ProcVersionSignature: Ubuntu 5.8.0-52.59-generic 5.8.18 Uname: Linux 5.8.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat May 8 16:01:13 2021 RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug autoreport-true groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1927813 Title: Whoopsie working is blocking shutdown Status in whoopsie package in Ubuntu: New Bug description: Summary In case there is a crashing application as a result of the shutdown command (Menu -> shutdown ), the shutdown process hangs with the message: `A stop job is running for crash report submission daemon ( [x]s / 1min 30s)` Steps to reproduce == - Start an application, that will crash on computer-shutdown (I use easystrokes or VIPole). - Shutdown computer via menu (not command line (might work as well, but untested)) - EXPECTED: computer shuts down quickly; possible crash reports will be sent the next time the computer gets shut down - or EXPECTED WORKAROUND: The waiting process can be canceled by Ctrl+C - ACTUAL: The user can only wait. Cancellation (Ctrl+C / Ctrl+\) won't work. Only hardware shutdown can cancel the process. Note Aside from whoopsie specifically, this waiting period with no cancellation is a general problem, I think. In case several processes prevent the shutdown like whoopsie does, the user has to wait several minutes (about 15min in one extreme case). A solution for this general problem would be the introduction of a screen to allow users to hard-shutdown any program (like MS Windows does). lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 apt-cache policy whoopsie === whoopsie: Installed: 0.2.72.2 Candidate: 0.2.72.2 Version table: *** 0.2.72.2 500 500 http://archive.ubuntu.com/ubuntu groovy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu groovy-security/main amd64 Packages 100 /var/lib/dpkg/status 0.2.72 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: whoopsie 0.2.72.2 ProcVersionSignature: Ubuntu 5.8.0-52.59-generic 5.8.18 Uname: Linux 5.8.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat May 8 16:01:13 2021 RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1927813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-p
[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart
Awesome! Thank you very much for reporting upstream! I'll try to test it as soon as hirusute is available and report back! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart Status in ibus: Unknown Status in ibus package in Ubuntu: Confirmed Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart
This is the icon I have in my task bar. Right clicking opens a menu with: - Preferences - Emoji Choice - About - Restart - Quit ** Attachment added: "ibus task item" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+attachment/5483691/+files/ibus%20task%20icon.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: Incomplete Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922186] Re: ibus very difficult to restart
> It's not clear to me why you would want to kill the ibus-daemon process in the first place I would say that's no valid argument because: 1) It has a "Quit" option. If you should not quit it, there should be no "Quit" option in the menu. 2) ibus is not system critical. Non-system critical processes should be restartable > it differs depending on the desktop environment. I appreciate the commands, but why should I as user need to care about that? > In situations where ibus crashes somehow, and IM inputting stops working, you > normally can do: > ibus restart 1) I did not have crashes since 20.04. However, in crashes in 18.xx I remember that `ibus restart` would simply tell me "there is no running instance" and do nothing. 2) Why can't this happen, when I call ibus from application menu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: Incomplete Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1922186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1922186] [NEW] ibus very difficult to restart
Public bug reported: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description:Ubuntu 20.10 Release:20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ibus 1.5.23-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18 Uname: Linux 5.8.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 1 15:33:00 2021 RebootRequiredPkgs: linux-image-5.8.0-48-generic linux-base linux-image-5.8.0-49-generic linux-base SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1922186 Title: ibus very difficult to restart Status in ibus package in Ubuntu: New Bug description: After closing ibus by task bar -> icon -> rightclick -> `Close` it seems to be impossible to restart it. Here some ways that should work and how they fail: 1) Menu -> ibus - - opens iBus settings - starts ibus service Problems: - No keyboard input is actually processed; I.e. cannot use keyboard then. - Service is not daemonized; I.e. as soon as the iBus settings window is closed, the services quits. Suggestion: - No keyboard input possible seems to be a bug -> should be fixed. - Service should be daemonized at this point 2) terminal -> `ibus start` --- Problems: - This command does not exist. One has to know, that `ibus-daemon` is the one they are searching for. Suggestions: - Implement this command to start the daemon from here 3) terminal -> `ibus-daemon &` / `ibus-daemon -d` - - brings up ibus with usable keyboard (good) Problems: - As soon as terminal gets closed, ibus-daemon quits 4) terminal -> `nohup ibus-daemon &` - - brings up ibus with usable keyboard (good) Problem: - As soon as terminal gets closed, ibus-daemon quits (very strange. something I wouldn't expect from a `nohup` call, by the way). System === - I use ibus in conjunction with ibus-anthy lsb_release -rd -- Description: Ubuntu 20.10 Release: 20.10 apt-cache policy ibus -- ibus: Installed: 1.5.23-0ubuntu1 Candidate: 1.5.23-0ubuntu1 Version table: *** 1.5.23-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status apt-cache policy ibus-anthy -- ibus-anthy: Installed: 1.5.11-1build1 Candidate: 1.5.11-1build1 Version table: *** 1.5.11-1build1 500 500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug
[Touch-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 Ubuntu
Touch seeded 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 ../../../.
[Touch-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 Ubuntu
Touch seeded 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 ../.
[Touch-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 Ubuntu
Touch seeded 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
[Touch-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
[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus
Please re-set the status in case "Fix Commited" does not seem appropriate. ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus Status in ibus: New Status in ibus package in Ubuntu: Fix Committed Bug description: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901789] Re: Release upgrade 20.04 -> 20.10 removed input method from ibus
Yes I could get it back; It works as expected now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1901789 Title: Release upgrade 20.04 -> 20.10 removed input method from ibus Status in ibus: New Status in ibus package in Ubuntu: Incomplete Bug description: What happened: === I'm using iBus as input "method" with - Japanese (Anthy) // primary - German set up. I upgraded from ubuntu 20.04 to 20.10. EXPECTED: No changes regarding input. ACTUAL: German input method was removed lsb_release -rd === Description: Ubuntu 20.10 Release: 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.12 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: XFCE Date: Wed Oct 28 11:10:04 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-24 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1901789/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes
** Attachment added: "text/plain; charset="utf-8""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418339/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1898713
Title:
Xorg crashes sometimes with Easystrokes
Status in xorg package in Ubuntu:
New
Bug description:
Xorg crashes, session closes, all unsaved data is gone.
What I did / Reproducing
===
It happens when I use Easystrokes to emulate `Ctrl+F4` or
`Ctrl+PageUp/Down`.
So far it happened about 5 recognized times, 3 recorded within the
last 3(?) month. twice during tab switching in incognito Firefox and
once in VSCode.
Reproducability
I feel it's very consistent in crashing in Firefox incognito. But it's not
purposely reproducible 100%.
I would give more information, but the stacktrace of the crashdump
does not tell much. I installed debug symbols for xorg, but they made
no change viewing it.
Here is the (obscured) stack trace:
```
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
[New LWP 100716]
[New LWP 100705]
[New LWP 100704]
[New LWP 100707]
[New LWP 100709]
[New LWP 100708]
[New LWP 100706]
[New LWP 100711]
[New LWP 100710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type for more, q to quit, c to continue without paging--
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 0x55a0da61fe9c in miPointerSetPosition (
pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570,
screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
at ../../../../mi/mipointer.c:610
610 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
(gdb)
(gdb)
(gdb) bt full
#0 0x55a0da61fe9c in miPointerSetPosition
(pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at
../../../../mi/mipointer.c:610
pScreenPriv =
pScreen =
newScreen = 0x254
x = 802
y = 596
switch_screen = 0
should_constrain_barriers = 0
i =
pPointer = 0x0
#1 0x55a0da4ec840 in positionSprite
(dev=dev@entry=0x55a0dc969400, mode=mode@entry=0,
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580,
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570,
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at
../../../../dix/getevents.c:961
scr =
tmpx = 801.02961125081322
tmpy = 595.47038874918678
#2 0x55a0da4ecf4d in positionSprite
(events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578,
scre--Type for more, q to quit, c to continue without paging--
enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580,
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at
../../../../dix/getevents.c:952
scr = 0x0
num_events = 2
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#3 fill_pointer_events (events=0x7f708d903c20,
events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400,
type=, buttons=buttons@entry=0, ms=ms@entry=289728198,
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at
../../../../dix/getevents.c:1434
num_events = 2
--Type for more, q to quit, c to continue without paging--
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#4 0x55a0da4ee620 in GetPointerEvents
(events=0x7f708d
[Touch-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes
** Attachment added: "text/plain; charset="utf-8""
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418340/+files/XorgLog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1898713
Title:
Xorg crashes sometimes with Easystrokes
Status in xorg package in Ubuntu:
New
Bug description:
Xorg crashes, session closes, all unsaved data is gone.
What I did / Reproducing
===
It happens when I use Easystrokes to emulate `Ctrl+F4` or
`Ctrl+PageUp/Down`.
So far it happened about 5 recognized times, 3 recorded within the
last 3(?) month. twice during tab switching in incognito Firefox and
once in VSCode.
Reproducability
I feel it's very consistent in crashing in Firefox incognito. But it's not
purposely reproducible 100%.
I would give more information, but the stacktrace of the crashdump
does not tell much. I installed debug symbols for xorg, but they made
no change viewing it.
Here is the (obscured) stack trace:
```
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
[New LWP 100716]
[New LWP 100705]
[New LWP 100704]
[New LWP 100707]
[New LWP 100709]
[New LWP 100708]
[New LWP 100706]
[New LWP 100711]
[New LWP 100710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type for more, q to quit, c to continue without paging--
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 0x55a0da61fe9c in miPointerSetPosition (
pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570,
screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
at ../../../../mi/mipointer.c:610
610 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
(gdb)
(gdb)
(gdb) bt full
#0 0x55a0da61fe9c in miPointerSetPosition
(pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at
../../../../mi/mipointer.c:610
pScreenPriv =
pScreen =
newScreen = 0x254
x = 802
y = 596
switch_screen = 0
should_constrain_barriers = 0
i =
pPointer = 0x0
#1 0x55a0da4ec840 in positionSprite
(dev=dev@entry=0x55a0dc969400, mode=mode@entry=0,
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580,
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570,
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at
../../../../dix/getevents.c:961
scr =
tmpx = 801.02961125081322
tmpy = 595.47038874918678
#2 0x55a0da4ecf4d in positionSprite
(events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578,
scre--Type for more, q to quit, c to continue without paging--
enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580,
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at
../../../../dix/getevents.c:952
scr = 0x0
num_events = 2
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#3 fill_pointer_events (events=0x7f708d903c20,
events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400,
type=, buttons=buttons@entry=0, ms=ms@entry=289728198,
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at
../../../../dix/getevents.c:1434
num_events = 2
--Type for more, q to quit, c to continue without paging--
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#4 0x55a0da4ee620 in GetPointerEvents
(events=0x7f708d903
[Touch-packages] [Bug 1898713] [NEW] Xorg crashes sometimes with Easystrokes
Public bug reported:
Xorg crashes, session closes, all unsaved data is gone.
What I did / Reproducing
===
It happens when I use Easystrokes to emulate `Ctrl+F4` or
`Ctrl+PageUp/Down`.
So far it happened about 5 recognized times, 3 recorded within the last
3(?) month. twice during tab switching in incognito Firefox and once in
VSCode.
Reproducability
I feel it's very consistent in crashing in Firefox incognito. But it's not
purposely reproducible 100%.
I would give more information, but the stacktrace of the crashdump does
not tell much. I installed debug symbols for xorg, but they made no
change viewing it.
Here is the (obscured) stack trace:
```
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
[New LWP 100716]
[New LWP 100705]
[New LWP 100704]
[New LWP 100707]
[New LWP 100709]
[New LWP 100708]
[New LWP 100706]
[New LWP 100711]
[New LWP 100710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type for more, q to quit, c to continue without paging--
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 0x55a0da61fe9c in miPointerSetPosition (
pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570,
screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
at ../../../../mi/mipointer.c:610
610 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
(gdb)
(gdb)
(gdb) bt full
#0 0x55a0da61fe9c in miPointerSetPosition
(pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at
../../../../mi/mipointer.c:610
pScreenPriv =
pScreen =
newScreen = 0x254
x = 802
y = 596
switch_screen = 0
should_constrain_barriers = 0
i =
pPointer = 0x0
#1 0x55a0da4ec840 in positionSprite
(dev=dev@entry=0x55a0dc969400, mode=mode@entry=0,
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580,
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570,
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at
../../../../dix/getevents.c:961
scr =
tmpx = 801.02961125081322
tmpy = 595.47038874918678
#2 0x55a0da4ecf4d in positionSprite
(events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578,
scre--Type for more, q to quit, c to continue without paging--
enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580,
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at
../../../../dix/getevents.c:952
scr = 0x0
num_events = 2
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#3 fill_pointer_events (events=0x7f708d903c20,
events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400,
type=, buttons=buttons@entry=0, ms=ms@entry=289728198,
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at
../../../../dix/getevents.c:1434
num_events = 2
--Type for more, q to quit, c to continue without paging--
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#4 0x55a0da4ee620 in GetPointerEvents
(events=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400, type=, type@entry=6, buttons=buttons@entry=0, flags=10, mask_in=)
at ../../../../dix/getevents.c:1691
ms = 289728198
num_events = 0
nev_tmp =
mask =
{last_bit = 1 '\001', has_unaccelerated = 1 '\001', mask =
"\003\000--Type for more, q to quit, c to continue without paging--
\000\000", valuators = {-1, -1.5, 0 }, unaccelerated = {-2,
-3, 0 }}
scroll =
{last_bit = -128 '\200', has_unaccelerated = 4 '\004', mask =
"eݠU", valuators = {6.9229118033614265e-310, 6.9229013081954128e-310,
6.922
[Touch-packages] [Bug 1898713] Re: Xorg crashes sometimes with Easystrokes
** Attachment added: "text utf8"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418338/+files/LightdmDisplayLog.txt
** Attachment removed: "LightdmLog.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418321/+files/LightdmLog.txt
** Attachment removed: "XorgLog.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418333/+files/XorgLog.txt
** Attachment removed: "XorgLogOld.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898713/+attachment/5418334/+files/XorgLogOld.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1898713
Title:
Xorg crashes sometimes with Easystrokes
Status in xorg package in Ubuntu:
New
Bug description:
Xorg crashes, session closes, all unsaved data is gone.
What I did / Reproducing
===
It happens when I use Easystrokes to emulate `Ctrl+F4` or
`Ctrl+PageUp/Down`.
So far it happened about 5 recognized times, 3 recorded within the
last 3(?) month. twice during tab switching in incognito Firefox and
once in VSCode.
Reproducability
I feel it's very consistent in crashing in Firefox incognito. But it's not
purposely reproducible 100%.
I would give more information, but the stacktrace of the crashdump
does not tell much. I installed debug symbols for xorg, but they made
no change viewing it.
Here is the (obscured) stack trace:
```
Reading symbols from /usr/lib/xorg/Xorg...
Reading symbols from
/usr/lib/debug/.build-id/c1/54f39135c0adc1b59f5b6dd49a73301b4311c8.debug...
[New LWP 100716]
[New LWP 100705]
[New LWP 100704]
[New LWP 100707]
[New LWP 100709]
[New LWP 100708]
[New LWP 100706]
[New LWP 100711]
[New LWP 100710]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
--Type for more, q to quit, c to continue without paging--
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 0x55a0da61fe9c in miPointerSetPosition (
pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570,
screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20)
at ../../../../mi/mipointer.c:610
610 ../../../../mi/mipointer.c: No such file or directory.
[Current thread is 1 (Thread 0x7f707b57f700 (LWP 100716))]
(gdb)
(gdb)
(gdb) bt full
#0 0x55a0da61fe9c in miPointerSetPosition
(pDev=pDev@entry=0x55a0dc969400, mode=mode@entry=0,
screenx=screenx@entry=0x7f707b57d570, screeny=screeny@entry=0x7f707b57d578,
nevents=nevents@entry=0x7f707b57d56c, events=events@entry=0x7f708d903c20) at
../../../../mi/mipointer.c:610
pScreenPriv =
pScreen =
newScreen = 0x254
x = 802
y = 596
switch_screen = 0
should_constrain_barriers = 0
i =
pPointer = 0x0
#1 0x55a0da4ec840 in positionSprite
(dev=dev@entry=0x55a0dc969400, mode=mode@entry=0,
mask=mask@entry=0x7f707b57d5c0, devx=devx@entry=0x7f707b57d580,
devy=devy@entry=0x7f707b57d588, screenx=screenx@entry=0x7f707b57d570,
screeny=0x7f707b57d578, nevents=0x7f707b57d56c, events=0x7f708d903c20) at
../../../../dix/getevents.c:961
scr =
tmpx = 801.02961125081322
tmpy = 595.47038874918678
#2 0x55a0da4ecf4d in positionSprite
(events=0x7f708d903c20, nevents=0x7f707b57d56c, screeny=0x7f707b57d578,
scre--Type for more, q to quit, c to continue without paging--
enx=0x7f707b57d570, devy=0x7f707b57d588, devx=0x7f707b57d580,
mask=0x7f707b57d5c0, mode=0, dev=0x55a0dc969400) at
../../../../dix/getevents.c:952
scr = 0x0
num_events = 2
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.47038874918678
devx = 801.02961125081322
devy = 595.47038874918678
sx = 0
sy = 0
mask =
{last_bit = 1 '\001', has_unaccelerated = 0 '\000', mask =
"\003\000\000\000", valuators = {801.02961125081322, 595.47038874918678, 0
}, unaccelerated = {0 }}
scr =
num_barrier_events = 0
#3 fill_pointer_events (events=0x7f708d903c20,
events@entry=0x7f708d903010, pDev=pDev@entry=0x55a0dc969400,
type=, buttons=buttons@entry=0, ms=ms@entry=289728198,
flags=flags@entry=10, mask_in=0x7f707b57d8d0) at
../../../../dix/getevents.c:1434
num_events = 2
--Type for more, q to quit, c to continue without paging--
event =
raw = 0x7f708d903010
screenx = 801.02961125081322
screeny = 595.4703887
[Touch-packages] [Bug 1896756] [NEW] tracker* startup is defined multiple times
Public bug reported:
This is about
- tracker-miner-fs
- tracker-extract
- tracker-store
Actual Behavior
=
Their startup is defined in
- ${XDG_CONFIG_HOME}/autostart ( more info:
https://wiki.archlinux.org/index.php/XDG_Autostart )
- /usr/lib/systemd/user/tracker*.service
Expected Behavior
===
Startup is only defined in one place.
Reason:
- Managing the software does not get confusing
lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Sep 23 20:39:33 2020
MachineType: FUJITSU FMVWB3U27
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows
2015" pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-07-24 (61 days ago)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB2BB
dmi.board.vendor: FUJITSU
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:
dmi.product.family: LIFEBOOK-JR
dmi.product.name: FMVWB3U27
dmi.sys.vendor: FUJITSU
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1896756
Title:
tracker* startup is defined multiple times
Status in systemd package in Ubuntu:
New
Bug description:
This is about
- tracker-miner-fs
- tracker-extract
- tracker-store
Actual Behavior
=
Their startup is defined in
- ${XDG_CONFIG_HOME}/autostart ( more info:
https://wiki.archlinux.org/index.php/XDG_Autostart )
- /usr/lib/systemd/user/tracker*.service
Expected Behavior
===
Startup is only defined in one place.
Reason:
- Managing the software does not get confusing
lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.2
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Wed Sep 23 20:39:33 2020
MachineType: FUJITSU FMVWB3U27
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic
root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro acpi_osi=! "acpi_osi=Windows
2015" pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d
SourcePackage: systemd
SystemdDelta:
[EXTENDED] /lib/systemd/system/rc-local.service →
/lib/systemd/system/rc-local.service.d/debian.conf
[EXTENDED] /lib/systemd/system/user@.service →
/lib/systemd/system/user@.service.d/timeout.conf
2 overridden configuration files found.
UpgradeStatus: Upgraded to focal on 2020-07-24 (61 days ago)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: FUJITSU // Insyde Software Corp.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB2BB
dmi.board.vendor: FUJITSU
dmi.board.version: A2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr:
dmi.product.family: LIFEBOOK-JR
dmi.product.name: FMVWB3U27
dmi.sys.vendor: FUJITSU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1896756/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1817559] Re: update-notifier ignores software-properties's settings
This bug is still present int 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1817559 Title: update-notifier ignores software-properties's settings Status in software-properties package in Ubuntu: Triaged Bug description: > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu $ lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 > 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center $ apt-cache policy update-manager update-manager: Installed: 1:16.04.15 Candidate: 1:16.04.15 Version table: *** 1:16.04.15 500 500 https://mirror.one.com/ubuntu xenial-updates/main amd64 Packages 500 https://mirror.one.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 1:16.04.12 500 500 https://mirror.one.com/ubuntu xenial-security/main amd64 Packages 500 https://mirror.one.com/ubuntu xenial-security/main i386 Packages 1:16.04.3 500 500 https://mirror.one.com/ubuntu xenial/main amd64 Packages 500 https://mirror.one.com/ubuntu xenial/main i386 Packages Steps to reproduce: - Run `update-manager' manually, via `update-manager' from a terminal for example - Press "Settings..." button - Configure the following settings to hide all update-manager's pop-ups respectively: Automatically check for updates: Never When there are security updates: When there are other updates: Display every two weeks Notify me of a new Ubuntu version: Never - Close settings - Exit `update-manager' Expected behaviour: - update-manager won't be checking any updates at all - but even if there are some "other updates" then it must be displayed not more often than "every two weeks" Actual behaviour: - update-manager checks for updates from time to time by itself - update-manager shows notifications *all* *the* *time*: every single day and much more times per day than even twice - update-manager keeps to show notifications even if it has been seen & closed manually (just because there wasn't time for maintenance window currently, for example) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: update-manager 1:16.04.15 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Mon Feb 25 16:32:29 2019 GsettingsChanges: b'com.ubuntu.update-manager' b'show-details' b'true' b'com.ubuntu.update-manager' b'window-height' b'365' b'com.ubuntu.update-manager' b'first-run' b'false' b'com.ubuntu.update-manager' b'window-width' b'303' b'com.ubuntu.update-manager' b'launch-time' b'int64 1551101458' InstallationDate: Installed on 2016-07-19 (951 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1817559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar
I think I got a better picture. Thank you very much for your help! I set this bug to Invalid. I filed a new bug explicitly going after the shortcut settings in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885749 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: Invalid Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1885749] [NEW] Enhancement: Remove default Emoji shortcuts
Public bug reported: Current Situation === (1) Per default ibus preferences are hidden in Ubuntu (I would say it's very difficult to reach ibus feature) (2) ibus has two default shortcuts, apparently for Emoji-something: - Ctrl+shift+e - Ctrl+shift+u (2.1) These shortcuts can prevent shortcuts from other applications being used (one example: VSCode's "show files" (2.2) Because of (1) it's extremely difficult to change these shortcuts, if they cause any problems - Especially because of (2.3). (2.3) The user has no way of knowing that ibus introduced these shortcuts (because they would only use Settings->Region & Language, which does not show any shortcut options) (3) I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason (guess): The normal user would not understand what to do after pressing the shortcut) Suggestion Remove shortcuts as a default setting Misc - Why is this bug not filed in github.com/ibus/ibus/issues? -> Because in ibus as standalone, where the user has a direction connection to it, it might make sense to keep the shortcuts. For the moment I would say this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the dialog gui even installed, if we don't was to show it? ...) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 [modified: usr/share/applications/org.freedesktop.IBus.Setup.desktop] ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 00:55:25 2020 InstallationDate: Installed on 2020-06-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1885749 Title: Enhancement: Remove default Emoji shortcuts Status in ibus package in Ubuntu: New Bug description: Current Situation === (1) Per default ibus preferences are hidden in Ubuntu (I would say it's very difficult to reach ibus feature) (2) ibus has two default shortcuts, apparently for Emoji-something: - Ctrl+shift+e - Ctrl+shift+u (2.1) These shortcuts can prevent shortcuts from other applications being used (one example: VSCode's "show files" (2.2) Because of (1) it's extremely difficult to change these shortcuts, if they cause any problems - Especially because of (2.3). (2.3) The user has no way of knowing that ibus introduced these shortcuts (because they would only use Settings->Region & Language, which does not show any shortcut options) (3) I guess the Emoji shortcuts ( (2) ) have no benefit for a normal user. Reason (guess): The normal user would not understand what to do after pressing the shortcut) Suggestion Remove shortcuts as a default setting Misc - Why is this bug not filed in github.com/ibus/ibus/issues? -> Because in ibus as standalone, where the user has a direction connection to it, it might make sense to keep the shortcuts. For the moment I would say this is a Ubuntu related issue, as ubuntu is hiding the dialog. (... why is the dialog gui even installed, if we don't was to show it? ...) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-2ubuntu2 [modified: usr/share/applications/org.freedesktop.IBus.Setup.desktop] ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 1 00:55:25 2020 InstallationDate: Installed on 2020-06-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1885749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar
** Changed in: ibus (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: Invalid Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar
Profound question: Where would an upstream bug be filed? I thought launchpad.net/ubuntu is already the source? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: Opinion Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar
Thank you for pointing out, that this is a configuration problem of Ubuntu. What would be the way of promoting that? Problem: Detailed settings for ibus-anthy cannot be done. Problems of that problem: (1) Ctrl+Alt+e- shortcut cannot be configured ( should do something about emojis (never worked here)) (2) Ctrl+Alt+u- shortcut cannot be configured ( allows to set a unicode point (never worked here)) (3) (Font size of Kanji-convertion suggestions cannot be changed) Annotation: perhaps it's worth setting the default shortcuts (1) and (2) to null -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: New Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar
** Changed in: ibus (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: New Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875592] [NEW] Xorg: High CPU usage when USB mic is plugged in after hibernation
Public bug reported: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage Remarks = I could not safely reproduce this behaviour on purpose simply by starting and hibernating. But I experience it on a week to week basis. I'm not suspending or some kind of suspend+hibernate. It's pure hibernation I experience this problem, I think, in 16 (started here), (never tried 17), 18, 19.10 I used perftop with flamegraph the other day. It revealed - DeletePassiveGrabFromList with 3 ~ 5% - ResourceClientBits: around 5% - GrabMatchesSecond: 3 ~ 5% - trace_raw_output_kvm_inj_virq: around 7 ~ 8% System === lsb_release -rd --- Description:Ubuntu 19.10 Release:19.10 apt-cache policy xorg -- xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Misc - 12GB RAM - Core i5 4 cores Debugging -- I can help collecting data, but I need assistance ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 28 17:29:02 2020 DistUpgraded: 2019-12-01 10:19:03,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. UHD Graphics 620 [10cf:1959] MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-12-01 (149 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875592 Title: Xorg: High CPU usage when USB mic is plugged in after hibernation Status in xorg package in Ubuntu: New Bug description: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage
[Touch-packages] [Bug 1875592] Re: Xorg: High CPU usage when USB mic is plugged in after hibernation
** Attachment added: "XorgLogOld" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+attachment/5362310/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875592 Title: Xorg: High CPU usage when USB mic is plugged in after hibernation Status in xorg package in Ubuntu: New Bug description: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage Remarks = I could not safely reproduce this behaviour on purpose simply by starting and hibernating. But I experience it on a week to week basis. I'm not suspending or some kind of suspend+hibernate. It's pure hibernation I experience this problem, I think, in 16 (started here), (never tried 17), 18, 19.10 I used perftop with flamegraph the other day. It revealed - DeletePassiveGrabFromList with 3 ~ 5% - ResourceClientBits: around 5% - GrabMatchesSecond: 3 ~ 5% - trace_raw_output_kvm_inj_virq: around 7 ~ 8% System === lsb_release -rd --- Description: Ubuntu 19.10 Release: 19.10 apt-cache policy xorg -- xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Misc - 12GB RAM - Core i5 4 cores Debugging -- I can help collecting data, but I need assistance ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 28 17:29:02 2020 DistUpgraded: 2019-12-01 10:19:03,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. UHD Graphics 620 [10cf:1959] MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-12-01 (149 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1875592] Re: Xorg: High CPU usage when USB mic is plugged in after hibernation
** Attachment added: "Screenshot of Resources at USB mic plugin" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+attachment/5362308/+files/2020-04-28_17-24.png ** Attachment removed: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+attachment/5362304/+files/XorgLog.txt ** Attachment removed: "XorgLogOld.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+attachment/5362305/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875592 Title: Xorg: High CPU usage when USB mic is plugged in after hibernation Status in xorg package in Ubuntu: New Bug description: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage Remarks = I could not safely reproduce this behaviour on purpose simply by starting and hibernating. But I experience it on a week to week basis. I'm not suspending or some kind of suspend+hibernate. It's pure hibernation I experience this problem, I think, in 16 (started here), (never tried 17), 18, 19.10 I used perftop with flamegraph the other day. It revealed - DeletePassiveGrabFromList with 3 ~ 5% - ResourceClientBits: around 5% - GrabMatchesSecond: 3 ~ 5% - trace_raw_output_kvm_inj_virq: around 7 ~ 8% System === lsb_release -rd --- Description: Ubuntu 19.10 Release: 19.10 apt-cache policy xorg -- xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Misc - 12GB RAM - Core i5 4 cores Debugging -- I can help collecting data, but I need assistance ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 28 17:29:02 2020 DistUpgraded: 2019-12-01 10:19:03,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. UHD Graphics 620 [10cf:1959] MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-12-01 (149 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+subscrip
[Touch-packages] [Bug 1875592] Re: Xorg: High CPU usage when USB mic is plugged in after hibernation
** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+attachment/5362309/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1875592 Title: Xorg: High CPU usage when USB mic is plugged in after hibernation Status in xorg package in Ubuntu: New Bug description: Problem: = When I plug in a USB microphone after one, two or three hibernations with work in between* the Xorg process is "going crazy" at around 100% - 130% CPU usage. (please see the attached chart) Steps (to hopefulle reproduce): === - start pc - do some usual work for a couple of hours - hibernate - wake up - do some usual work for a couple of hours - hibernate - wake up ( you might need more repetitions here) - do some usual work for a couple of hours - plug in USB microphone Actual: - Xorg has high CPU usage Expected: - Xorg has usual CPU usage Remarks = I could not safely reproduce this behaviour on purpose simply by starting and hibernating. But I experience it on a week to week basis. I'm not suspending or some kind of suspend+hibernate. It's pure hibernation I experience this problem, I think, in 16 (started here), (never tried 17), 18, 19.10 I used perftop with flamegraph the other day. It revealed - DeletePassiveGrabFromList with 3 ~ 5% - ResourceClientBits: around 5% - GrabMatchesSecond: 3 ~ 5% - trace_raw_output_kvm_inj_virq: around 7 ~ 8% System === lsb_release -rd --- Description: Ubuntu 19.10 Release: 19.10 apt-cache policy xorg -- xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status Misc - 12GB RAM - Core i5 4 cores Debugging -- I can help collecting data, but I need assistance ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 28 17:29:02 2020 DistUpgraded: 2019-12-01 10:19:03,497 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-40-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. UHD Graphics 620 [10cf:1959] MachineType: FUJITSU FMVWB3U27 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=fe637d00-125b-4a54-adce-3711830d450b ro pci=nomsi acpi_osi=Linuxs resume=UUID=8fa6d40f-c23d-497e-9846-f6f26536690d SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-12-01 (149 days ago) dmi.bios.date: 01/23/2018 dmi.bios.vendor: FUJITSU // Insyde Software Corp. dmi.bios.version: Version 1.07 dmi.board.name: FJNB2BB dmi.board.vendor: FUJITSU dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//InsydeSoftwareCorp.:bvrVersion1.07:bd01/23/2018:svnFUJITSU:pnFMVWB3U27:pvr:rvnFUJITSU:rnFJNB2BB:rvrA2:cvnFUJITSU:ct10:cvr: dmi.product.family: LIFEBOOK-JR dmi.product.name: FMVWB3U27 dmi.sys.vendor: FUJITSU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~19.10.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1875592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793222] Re: Mousepad doesn't take input after canceled save dialog
After Ubuntu 19.10 I couldn't reproduce on any system. I set the report to "invalid". ** Changed in: ibus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1793222 Title: Mousepad doesn't take input after canceled save dialog Status in ibus package in Ubuntu: Invalid Bug description: 1 Open Mousepad 2 Write something 3 Ctrl+S for save -> dialog opens 4 Exit dialog with ESC -> Mousepad will not take any keyboard input anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mousepad 0.4.0-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 19 07:17:27 2018 InstallationDate: Installed on 2018-02-12 (218 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: mousepad UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1793222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1660619] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B
It seems like the newly opened bug (by Llord Llama) is not exactly the same as this one here. I'm also affected by this one. I don't seem to have any visible problems but the syslog is spammed by these errors. Package: xorg Architecture: amd64 Version: 1:7.7+19ubuntu12 Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan ProblemType: Bug DistroRelease: Ubuntu 19.10 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE UpgradeStatus: Upgraded to eoan on 2019-12-01 (0 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1660619 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B Status in xorg package in Ubuntu: Invalid Bug description: I've a dual monitor setup and I'm running latest version of kubuntu. After a few days of uptime the desktop becomes so slow that I've to reboot it. In the log I find those errors, I don't know if they are related: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=150051 end=150052) time 110 us, min 1073, max 1079, scanline start 1072, end 1080 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 31 14:06:17 2017 DistUpgraded: 2016-10-16 19:45:53,200 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-30-generic, x86_64: installed bbswitch, 0.8, 4.8.0-32-generic, x86_64: installed bbswitch, 0.8, 4.8.0-34-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7978] InstallationDate: Installed on 2013-04-25 (1376 days ago) InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: MSI MS-7978 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic root=UUID=f848f2e6-9d53-4c75-823a-fa97cfe10aa6 ro SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2016-10-16 (106 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: Z170A GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnZ170AGAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Jan 28 11:57:37 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1793222] Re: Mousepad doesn't take input after canceled save dialog
Indeed. I took some hours to try it myself on a fresh installation. The bug didn't appear. I will try to find out more about the environment and post infos as soon as I have them. Maybe it's something that only happens through the upgrade... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1793222 Title: Mousepad doesn't take input after canceled save dialog Status in ibus package in Ubuntu: New Bug description: 1 Open Mousepad 2 Write something 3 Ctrl+S for save -> dialog opens 4 Exit dialog with ESC -> Mousepad will not take any keyboard input anymore. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mousepad 0.4.0-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Sep 19 07:17:27 2018 InstallationDate: Installed on 2018-02-12 (218 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: mousepad UpgradeStatus: Upgraded to bionic on 2018-08-25 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1793222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
