[Desktop-packages] [Bug 1588197] Re: Can't type anything in search box
I have attached a copy of the output I get with this issue. The first error ```console (evince:25290): IBUS-WARNING **: 10:54:21.331: Unable to connect to ibus: Could not connect: Permission denied ``` happens immediately when I run evince. The second error: ```console (evince:25403): GLib-WARNING **: 10:56:05.731: getpwuid_r(): failed due to unknown user id (1855985172) ``` occurs when I try to add a note to the PDF document. Evince does not accept keyboard input. I can fix the problem by doing: ```console rm -r ~/.config/ibus ``` which is a fix I saw on a duplicate version of this bug on here ** Attachment added: "EvinceError.png" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+attachment/5743054/+files/EvinceError.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1588197 Title: Can't type anything in search box Status in evince package in Ubuntu: Invalid Bug description: Since Ubuntu 16.04, I can't search strings in PDF using Evince viewer. Clicking search button or CTRL+F shows search box, but I can't type anything inside. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1588197/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2024377] Re: Adsys can't fetch GPOs
Hi all, is there any update on the fix being backported to 22.04? I'm
also having this issue and am locked into 22.04.
Thanks!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/2024377
Title:
Adsys can't fetch GPOs
Status in adsys package in Ubuntu:
Fix Released
Bug description:
Bad, maybe no understandable english ahead.
Can't find anything related to this on Github, Canonical Forums,
Reddit or StackOverflow.
On Ubuntu 22.04, I've followed the Wiki tutorial and verified all
steps on Integration Ubuntu Desktop whitepaper. Currently using SSSD
backend, I can log with Active Directory users however when adsys is
installed I can't fetch GPOs. In this version the error is:
ERROR Error from server: error while updating policy: can't get
policies for "ubuntu": can't download all gpos and assets: one or more
error while fetching GPOs and assets: can't download "ubuntuRoot":
can't check if ubuntuRoot needs refreshing: no GPT.INI file: cannot
open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
It happens when using "adsysctl update -m" or "adsysctl update
usern...@domain.com.br /tmp/krb5c_getentId_randomdnumber" and just
"adsysctl update" too.
I've upgrade the machine to 22.10 and the error changed to:
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER').
After upgrade to 23.04 the error persist same as the above.
Full info 22.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
We will only use the defaults, env variables or flags.
DEBUG Connecting as [[2504:109556]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
DEBUG GPO "ubuntuRoot" for "ubuntu" available at
"smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}"
DEBUG Analyzing "assets"
DEBUG Analyzing "ubuntuRoot"
INFO No assets directory with GPT.INI file found on AD, skipping assets
download
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": can't download all gpos and assets: one or more error while fetching
GPOs and assets: can't download "ubuntuRoot": can't check if ubuntuRoot needs
refreshing: no GPT.INI file: cannot open
smb://addc01.domain.com.br/SysVol/domain.com.br/Policies/{DF072E7E-6F2F-46D1-A90F-699415F72F2E}/GPT.INI:
invalid argument
Full info 23.04 (- verbose):
INFO No configuration file: Config File "adsys" Not Found in "[/home/jzprates
/root /etc /usr/sbin]".
DEBUG Connecting as [[58811:006019]]
DEBUG New request /service/UpdatePolicy
DEBUG Requesting with parameters: IsComputer: true, All: false, Target:
ubuntu, Krb5Cc:
DEBUG NormalizeTargetName for "ubuntu", type "computer"
DEBUG Check if grpc request peer is authorized
DEBUG Authorized as being administrator
DEBUG GetPolicies for "ubuntu", type "computer"
DEBUG Getting gpo list with arguments: "--objectclass computer
ldap://addc01.domain.com.br ubuntu"
ERROR Error from server: error while updating policy: can't get policies for
"ubuntu": failed to retrieve the list of GPO (exited with 1): exit status 1
Failed to bind - LDAP client internal error: NT_STATUS_INVALID_PARAMETER
Failed to connect to 'ldap://addc01.domain.com.br' with backend 'ldap': LDAP
client internal error: NT_STATUS_INVALID_PARAMETER
Failed to open session: (1, 'LDAP client internal error:
NT_STATUS_INVALID_PARAMETER')
Additional info:
Domain Controller and machine are on the same subnet without firewall on any
level;
Domain Controller is a Windows Server 2019 updated to the last security
version;
Both machine and user are on the same OU with "no heritage" enabled and just
one policy added to permit usern...@domain.com.br to become root;
The info header directory is "/home/jzprates" on both logs because I've
collected them using the local account using "sudo adsysctl update -m -";
If I disable Adsys login on pam-auth-update, Ubuntu creates a homedir and
enter correctly with domain
[Desktop-packages] [Bug 2016925] Re: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04
This issue was fixed a couple of months later in a regular update. I'm on 23.10 now on the same machine and haven't had any problems with snaps since. The issue can be closed as far as I am concerned. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2016925 Title: [amdgpu] Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2042931] [NEW] Crashing frequently
Public bug reported: Crashing frequetnly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:31:46 2023 GsettingsChanges: InstallationDate: Installed on 2022-09-07 (425 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2042931 Title: Crashing frequently Status in nautilus package in Ubuntu: New Bug description: Crashing frequetnly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:31:46 2023 GsettingsChanges: InstallationDate: Installed on 2022-09-07 (425 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2042931/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
I enabled -proposed on jammy, and updated pcscd to 1.9.5-3ubuntu1. I verified that the socket is now enabled: $ systemctl status pcscd.socket ● pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; enabled; vendor preset: enabled) Active: active (listening) since Fri 2023-07-21 12:57:49 EDT; 6s ago Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) CGroup: /system.slice/pcscd.socket Jul 21 12:57:49 brain systemd[1]: Listening on PC/SC Smart Card Activation Socket. I also verified that when I plug in my Nitrokey HSM2, that it's now recognized by the system: $ sc-hsm-tool Using reader with a card: Nitrokey Nitrokey HSM (...) ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: Fix Committed Status in pcsc-lite source package in Kinetic: Fix Committed Status in pcsc-lite source package in Lunar: Fix Committed Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016925] Re: Firefox window is visually corrupted after upgrading to Ubuntu 23.04
More info: The bug affect all snaps but not ordinary executables. All snaps launch distorted. After a recent reboot I tried several times to launch Firefox, every time the bug appeared, and all my tabs where unreadable. Then I started Thunderbird (which is NOT a snap) and clicked on a link in a mail so that a new tab opened in Firefox. Suddenly Firefox was normal, and all tabs (also the old ones) where readable just fine! Other snaps e.g. chromium still launches with the bug. When staring the snap "openscad-nightly", the initial splash screen (Welcome to OpenScad) is normal, but when I click on e.g. "Open Recent" I get a distorted window. So far I haven't been able to recognize any message on stderr that are common when launching snap programs, but there are plenty of apparmor="DENIED" in dmesg, if that's any clue. I'd be happy to provide log files if someone has any specific request -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2022023] [NEW] package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit stat
Public bug reported: I am using netplan for my network config. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.4-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jun 1 12:05:16 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 8 InstallationDate: Installed on 2020-04-25 (1131 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IpRoute: default via 192.168.56.1 dev enp7s0 proto static 192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2 IwConfig: lono wireless extensions. enp7s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.22ubuntu1 apt 2.7.0 RfKill: SourcePackage: network-manager Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8 UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package mantic third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2022023 Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8 Status in network-manager package in Ubuntu: New Bug description: I am using netplan for my network config. ProblemType: Package DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.4-1ubuntu4 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: unknown Date: Thu Jun 1 12:05:16 2023 ErrorMessage: installed network-manager package post-installation script subprocess returned error exit status 8 InstallationDate: Installed on 2020-04-25 (1131 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IpRoute: default via 192.168.56.1 dev enp7s0 proto static 192.168.56.0/30 dev enp7s0 proto kernel scope link src 192.168.56.2 IwConfig: lono wireless extensions. enp7s0no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Python3Details: /usr/bin/python3.11, Python 3.11.3, python3-minimal, 3.11.2-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.22ubuntu1 apt 2.7.0 RfKill: SourcePackage: network-manager Title: package network-manager 1.42.4-1ubuntu4 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 8 UpgradeStatus: Upgraded to mantic on 2023-06-01 (0 days ago) nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'gen'] failed with exit code 8: Error: NetworkManager is not running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2022023/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020239] [NEW] After update from Kubuntu 22.04 to 23.04 via 22.20 LibreOffice opens with 1 dimensional window
Public bug reported: I upgraded a machine from Kubuntu 22.04 to 23.10 and then immediately to 23.04. After logging on to 23.04 I tried to open LibreOffice documents but only had a vertical line on the screen. After some experimentation I found that this line was a window of zero width and it was possible to use the mouse to widen to a usable window. Opening subsequent documents was OK. I have now recreated this on VirtualBox and it seems that the problem occurs if you don't edit documents at the 23.10 stage. Steps to recreate. 1. Install Kubuntu 22.04, run apt update/dist-upgrade. 2. Close, take snapshot, reload 3. Create LibreOffice documents, eg calc, impress and write, enter random text. 4. Close, take snapshot, reload 5. Upgrade to 22.10 6. Close, take snapshot, reload 7. Log on, edit each document, add more random text. 8. Close, take snapshot, reload 9. Upgrade to 23.04 10. Close, take snapshot, reload 11. Log on and open documents Following the above script which includes document updates under 22.10, the documents open correctly in 23.04. Repeat the above, omitting steps 7 & 8 so the documents aren't edited under 22.10. The documents open as a zero width window in 23.04. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 20 12:21:18 2023 InstallationDate: Installed on 2023-05-19 (0 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: libreoffice UpgradeStatus: Upgraded to lunar on 2023-05-20 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2020239 Title: After update from Kubuntu 22.04 to 23.04 via 22.20 LibreOffice opens with 1 dimensional window Status in libreoffice package in Ubuntu: New Bug description: I upgraded a machine from Kubuntu 22.04 to 23.10 and then immediately to 23.04. After logging on to 23.04 I tried to open LibreOffice documents but only had a vertical line on the screen. After some experimentation I found that this line was a window of zero width and it was possible to use the mouse to widen to a usable window. Opening subsequent documents was OK. I have now recreated this on VirtualBox and it seems that the problem occurs if you don't edit documents at the 23.10 stage. Steps to recreate. 1. Install Kubuntu 22.04, run apt update/dist-upgrade. 2. Close, take snapshot, reload 3. Create LibreOffice documents, eg calc, impress and write, enter random text. 4. Close, take snapshot, reload 5. Upgrade to 22.10 6. Close, take snapshot, reload 7. Log on, edit each document, add more random text. 8. Close, take snapshot, reload 9. Upgrade to 23.04 10. Close, take snapshot, reload 11. Log on and open documents Following the above script which includes document updates under 22.10, the documents open correctly in 23.04. Repeat the above, omitting steps 7 & 8 so the documents aren't edited under 22.10. The documents open as a zero width window in 23.04. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat May 20 12:21:18 2023 InstallationDate: Installed on 2023-05-19 (0 days ago) InstallationMedia: Kubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: libreoffice UpgradeStatus: Upgraded to lunar on 2023-05-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2020239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Description changed: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket - Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) - Active: inactive (dead) -Triggers: ● pcscd.service - Listen: /run/pcscd/pcscd.comm (Stream) + Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) + Active: inactive (dead) + Triggers: ● pcscd.service + Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. + + As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: + - jammy + - kinetic + - lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Status in pcsc-lite source package in Jammy: Triaged Status in pcsc-lite source package in Kinetic: Triaged Status in pcsc-lite source package in Lunar: Triaged Status in pcsc-lite package in Debian: Unknown Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Description changed: - Ubuntu Mate 22.04 with the latest updates. - Problem is present with internal smart-card reader and also external usb smart-card reader. + [ Impact ] - eid-viewer sees no card reader,but When i do: + The pscc-lite package provides an open source implementation of PC/SC, + the de-facto standard to interface Personal Computers with Smart + Cards/Readers. - sudo pcscd -f + This bug is in the upstream debian packaging, and results in the + pcscd.socket being disabled after installation. This prevents automatic + startup of the associated pcscd.service, thus preventing automatic + handling of Smart Cards/Readers w/out manual intervention to enable the + socket (which doesn't persist across reboots). - it is working, also following the tips of Ludovic: - https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html + This is especially painful for users that require Smart Authentication + for login. - sudo systemctl stop pcscd.socket - sudo systemctl start pcscd.socket + [ Test Plan ] - It is working until next restart. + Steps to reproduce: - libacsccid1 version: 1.1.8-1 - libccid version: 1.5.0-2 - pcscd version: 1.9.5-3 - eid-archive version: 2022.3 - eid-mw version: 5.0.28v5.0.28-0u2204-1 - eid-viewer version: 5.0.28v5.0.28-0u2204-1 + 1. If installed, remove and do a fresh install of the package pcscd + (the sole version released for jammy is 1.9.5-3). - In Firefox, my eid card is then also recognized, but only in the ESR - version, but this is a know Mozilla bug. + 2. Verify that the pcscd.socket is disabled: + + $ systemctl status pcscd.socket + ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket + Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) + Active: inactive (dead) +Triggers: ● pcscd.service + Listen: /run/pcscd/pcscd.comm (Stream) + + 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or + Nitrokey) that's known to work on Ubuntu and verify that it fails to + work. + + Repeating the same steps with a package built with the patch attached to + comment #27 should ensure that the socket is enabled, and that + interaction with a Smart Card or Crypto Token should work w/out manual + intervention. + + [ Where problems could occur ] + + This is a back-ported change from upstream and is a result of a bug in + dh_installsystemd (see comment #26). As such the risk is minimal. + + The only potential risk of failure I can come up with is a snap that + stages the old version of the client library, as it would be looking in + the wrong place for the socket. + + [ Other Info ] + + This bug was originally reported against Ubuntu Mate 22.04, however it + applies to all derivatives of Ubuntu Desktop 22.04 LTS. + + Note - while there's some disagreement as to whether this bug occurs + 100% of the time across all 22.04 installations, it's pretty clear from + the upstream Debian bug and subsequent packaging fix that we should land + this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only
[Desktop-packages] [Bug 1971984] Re: pcscd.socket is disabled after installation
** Summary changed: - pcscd 1.9.5-3 do not start automatically, only manual + pcscd.socket is disabled after installation -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016925] Re: Firefox window is visually corrupted after upgrading to Ubuntu 23.04
The issue is intermittent. It happened twice for me after reboot, the first time on first reboot after upgrade to Lunar, then a few days later. On both occasions it disappeared after some time (tens of minutes), but I don't know what I did to fix it.. # Percona Toolkit System Summary Report ## Date | 2023-05-13 14:07:41 UTC (local TZ: CEST +0200) Hostname | Bullen Uptime | 5 days, 3:02, 2 users, load average: 0,72, 0,62, 0,68 Platform | Linux Release | Ubuntu 23.04 (lunar) Kernel | 6.2.0-20-generic Architecture | CPU = 64-bit, OS = 64-bit Threading | NPTL 2.37 SELinux | No SELinux detected Virtualized | No virtualization detected # Processor ## Processors | physical = 1, cores = 12, virtual = 24, hyperthreading = yes Speeds | 1x3462.775, 1x3464.922, 1x3510.290, 1x3564.914, 1x3592.028, 1x3593.501, 1x3596.300, 1x3597.296, 1x3597.434, 1x3597.810, 1x3598.240, 1x3598.367, 1x3599.356, 1x3599.598, 1x3599.606, 1x3599.672, 1x3599.699, 1x3599.822, 1x3599.868, 1x3600.093, 1x3671.525, 1x3690.418, 1x3700.563, 1x4322.343 Models | 24xAMD Ryzen 9 3900X 12-Core Processor Caches | 24x512 KB # Memory # Total | 31,1G ** Attachment added: "Screenshot from 2023-04-30 16-49-06.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+attachment/5672897/+files/Screenshot%20from%202023-04-30%2016-49-06.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
I ran into this bug earlier this week while trying to setup my new Nitrokey HSM2 (https://docs.nitrokey.com/hsm/linux/) on a Thinkpad running 22.04 LTS. I've confirmed that the upstream commit from 1.9.9-2 fixes the problem, and am uploading this as a patch. ** Patch added: "Backported packaging fix from upstream 1.9.9-2" https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+attachment/5672739/+files/0001-Fix-dh_installsystemd-doesn-t-handle-files-in-usr-li.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2017604] [NEW] Firefox cannot use symlinked directories for reading or writing
Public bug reported: My ~/Downloads directory is symlinked to a slower disk. Firefox is unable to save any downloads; they show up as failed. This also happens using 'Save image as ...' Further, if I'm uploading a file to a website, it can't be from a symlinked directory (in my case, ~/tmp). Other context: this is a fresh Kubuntu 22.10 install: Description:Ubuntu 22.10 Release:22.10 Firefox is version 112.0.1+build1-0ubuntu0.22.10.1~mt1 from the Mozilla PPA (not Beta). I didn't have this problem using what I thought was the same lineage of package on the previous desktop. I tried this using a pristine profile, and the problem still remained. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2017604 Title: Firefox cannot use symlinked directories for reading or writing Status in firefox package in Ubuntu: New Bug description: My ~/Downloads directory is symlinked to a slower disk. Firefox is unable to save any downloads; they show up as failed. This also happens using 'Save image as ...' Further, if I'm uploading a file to a website, it can't be from a symlinked directory (in my case, ~/tmp). Other context: this is a fresh Kubuntu 22.10 install: Description:Ubuntu 22.10 Release:22.10 Firefox is version 112.0.1+build1-0ubuntu0.22.10.1~mt1 from the Mozilla PPA (not Beta). I didn't have this problem using what I thought was the same lineage of package on the previous desktop. I tried this using a pristine profile, and the problem still remained. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2017604/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2008540] [NEW] Ubuntu 22.04 freezes suddenly for no apparent reason. it cannot reproduce.
Public bug reported: Ubuntu 22.04 freezes suddenly for no apparent reason. It does not respond to any rescue key combination (Alt + SysRq + R E I S U, Alt + F2, etc). Only with "Alt + SysRq + B" I can do a reset. I have updated the kernel to the next version antonio@antoniormz:/var/crash$ uname -r 5.19.0-051900rc6-generic And I am still testing the stability. Release: antonio@antoniormz:/var/crash$ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Package version: antonio@antoniormz:/var/crash$ apt-cache policy pkgname N: Unable to locate package pkgname Expected behavior: Could you please help me identify what is causing the system freeze and how to fix it? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 5.19.0-051900rc6-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 23:38:28 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (46 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2008540 Title: Ubuntu 22.04 freezes suddenly for no apparent reason. it cannot reproduce. Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04 freezes suddenly for no apparent reason. It does not respond to any rescue key combination (Alt + SysRq + R E I S U, Alt + F2, etc). Only with "Alt + SysRq + B" I can do a reset. I have updated the kernel to the next version antonio@antoniormz:/var/crash$ uname -r 5.19.0-051900rc6-generic And I am still testing the stability. Release: antonio@antoniormz:/var/crash$ lsb_release -rd Description:Ubuntu 22.04.2 LTS Release:22.04 Package version: antonio@antoniormz:/var/crash$ apt-cache policy pkgname N: Unable to locate package pkgname Expected behavior: Could you please help me identify what is causing the system freeze and how to fix it? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 Uname: Linux 5.19.0-051900rc6-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 24 23:38:28 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (46 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2008540/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
This is still an issue in Ubuntu 22.04. I solved it by using apt to remove brltty. Unfortunately this is likely to be temporary as an update will reinstate it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998676] Re: The link to Java has been changed
** Description changed: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1998676 Title: The link to Java has been changed Status in libreoffice package in Ubuntu: New Bug description: I want to produce labels for my Christmas cards. I have added the database for 2022 in Tools > Options > LibreOffice Base > Databases. It is called CardList2022.odb. When I test this new database I do not get an error message. I am using a LibreOffice Spreadsheet CardList2022.ods to hold my list of Cards. The database shows it as a table. I then go File > New > Labels in a Writer document and select the 2022 database. However, when I try to select a Table nothing is shown and there are no Database fields. If I choose 'New Document' nothing is shown. I would expect to have a sheet of names and addresses. The Ubuntu release I am using is 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1998676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998676] Re: The link to Java has been changed
Version of libreoffice used in the snap version 7.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1998676 Title: The link to Java has been changed Status in libreoffice package in Ubuntu: New Bug description: I want to produce labels for my Christmas cards. I have added the database for 2022 in Tools > Options > LibreOffice Base > Databases. It is called CardList2022.odb. When I test this new database I do not get an error message. I am using a LibreOffice Spreadsheet CardList2022.ods to hold my list of Cards. The database shows it as a table. I then go File > New > Labels in a Writer document and select the 2022 database. However, when I try to select a Table nothing is shown and there are no Database fields. If I choose 'New Document' nothing is shown. I would expect to have a sheet of names and addresses. The Ubuntu release I am using is 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1998676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1998676] [NEW] The link to Java has been changed
Public bug reported: I want to produce labels for my Christmas cards. I have added the database for 2022 in Tools > Options > LibreOffice Base > Databases. It is called CardList2022.odb. When I test this new database I do not get an error message. I am using a LibreOffice Spreadsheet CardList2022.ods to hold my list of Cards. The database shows it as a table. I then go File > New > Labels in a Writer document and select the 2022 database. However, when I try to select a Table nothing is shown and there are no Database fields. If I choose 'New Document' nothing is shown. I would expect to have a sheet of names and addresses. The Ubuntu release I am using is 22.04.1 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1998676 Title: The link to Java has been changed Status in libreoffice package in Ubuntu: New Bug description: I want to produce labels for my Christmas cards. I have added the database for 2022 in Tools > Options > LibreOffice Base > Databases. It is called CardList2022.odb. When I test this new database I do not get an error message. I am using a LibreOffice Spreadsheet CardList2022.ods to hold my list of Cards. The database shows it as a table. I then go File > New > Labels in a Writer document and select the 2022 database. However, when I try to select a Table nothing is shown and there are no Database fields. If I choose 'New Document' nothing is shown. I would expect to have a sheet of names and addresses. The Ubuntu release I am using is 22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1998676/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922414] Re: ssh-agent fails to start (has_option: command not found)
Same for me on Ubuntu Mate 22.04 5.15.0-52-generic and Cinnamon 5.2.7 /etc/X11/Xsession.d/30x11-common_xresources: ligne 16: has_option : commande introuvable /etc/X11/Xsession.d/75dbus_dbus-launch: ligne 9: has_option : commande introuvable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983202] Re: Link within email not actioned
Changed 2 to 4 and left everything else unchanged. http and https links now open Firefox. Changed my system default to Chromium and that opened as expected. Now reverted to Firefox. Thank you for your help. Happy to provide anything if you think worthwhile investigating further. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983202 Title: Link within email not actioned Status in thunderbird package in Ubuntu: New Bug description: Accessing a http or https link in an email has no effect. This is true if I left click on the link or right click and select "Open link in browser". My default browser is Firefox. Just to confuse things it does work occasionally, the first time I open a link after loading Thunderbird. The problem still exists in safe mode. I think the problem started after the update to 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Jul 31 11:51:22 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-08 (721 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 169.254.0.0/16 dev enp45s0 scope link metric 1000 192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.0.2 dev enp45s0 proto static scope link metric 100 192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=91.11.0/20220628000715 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-05-16 (75 days ago) dmi.bios.date: 07/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.10:bd07/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983202] Re: Link within email not actioned
/home/tony/.thunderbird/mmhujxko.default/handlers.json
{"defaultHandlersVersion":{},"mimeTypes":{"application/pdf":{"action":3,"extensions":["pdf"]},"audio/x-wav":{"action":2,"handlers":[{"name":"kaffeine","path":"/usr/bin/kaffeine"}],"extensions":["wav"]},"image/jpeg":{"action":2,"handlers":[{"name":"gwenview","path":"/usr/bin/gwenview"}],"extensions":["jpeg","jpg","jpe"]},"application/zip":{"action":4,"extensions":["zip"]},"application/msword":{"action":4,"extensions":["doc","dot"]},"application/vnd.openxmlformats-officedocument.wordprocessingml.document":{"action":4,"ask":true,"extensions":["docx"]},"application/vnd.ms-excel":{"action":4,"ask":true,"extensions":["xls","xlb","xlt"]},"audio/vnd.wave":{"action":4,"ask":true},"image/tiff":{"action":2,"ask":true,"handlers":[{"name":"GNU
Image Manipulation
Program","path":"/usr/bin/gimp-2.8"}],"extensions":["tif","tiff"]},"application/x-xpinstall":{"action":2,"ask":true,"handlers":[{"name":"Thunderbird
Mail","path":"/usr/bin/thunderbird"}],"extensions":["xpi"]},"image/png":{"action":2,"ask":true,"handlers":[{"name":"Okular","path":"/usr/bin/okular"}],"extensions":["png"]},"application/rtf":{"action":4,"ask":true,"extensions":["rtf"]},"application/vnd.oasis.opendocument.text":{"action":4,"ask":true,"extensions":["odt"]},"text/plain":{"action":2,"ask":true,"extensions":["txt","asc","text","pot","brf","srt"],"handlers":[{"name":"Kate","path":"/usr/bin/kate"}]},"application/vnd.ms-word.document.macroenabled.12":{"action":4,"ask":true,"extensions":["docm"]},"application/vnd.oasis.opendocument.spreadsheet":{"action":4,"ask":true,"extensions":["ods"]},"image/*":{"action":0,"ask":true,"handlers":[{"name":"gwenview","path":"/usr/bin/gwenview"}],"extensions":["jpg","jpeg","jpe"]},"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet":{"action":4,"ask":true,"extensions":["xlsx"]},"application/vnd.openxmlformats-officedocument.presentationml.presentation":{"action":4,"ask":true,"extensions":["pptx"]}},"schemes":{"http":{"action":4,"handlers":[{"name":"Firefox
Web Browser","command":"env
%u"},{"name":"thunderbird","path":"/usr/bin/thunderbird"}]},"https":{"action":2,"handlers":[{"name":"Firefox
Web Browser","command":"env
BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/firefox_firefox.desktop
/snap/bin/firefox %u"}]}}}
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1983202
Title:
Link within email not actioned
Status in thunderbird package in Ubuntu:
New
Bug description:
Accessing a http or https link in an email has no effect. This is
true if I left click on the link or right click and select "Open link
in browser". My default browser is Firefox.
Just to confuse things it does work occasionally, the first time I
open a link after loading Thunderbird.
The problem still exists in safe mode. I think the problem started
after the update to 22.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BuildID: 20220628000715
CasperMD5CheckResult: unknown
Channel: Unavailable
CurrentDesktop: KDE
Date: S
[Desktop-packages] [Bug 1983202] Re: Link within email not actioned
Outcome slightly weird. Under "Files & Attachments" there was an entry for content type http. The only options were "Always ask" or "Use Konqueror (default)". I chose Konqueror and now http links in emails open in Firefox! There is no entry for https and https links do not open in anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983202 Title: Link within email not actioned Status in thunderbird package in Ubuntu: New Bug description: Accessing a http or https link in an email has no effect. This is true if I left click on the link or right click and select "Open link in browser". My default browser is Firefox. Just to confuse things it does work occasionally, the first time I open a link after loading Thunderbird. The problem still exists in safe mode. I think the problem started after the update to 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Jul 31 11:51:22 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-08 (721 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 169.254.0.0/16 dev enp45s0 scope link metric 1000 192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.0.2 dev enp45s0 proto static scope link metric 100 192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=91.11.0/20220628000715 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-05-16 (75 days ago) dmi.bios.date: 07/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.10:bd07/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983202] Re: Link within email not actioned
Thank you for responding. I wasn't aware that this was the setting. I would have assumed that it did use the desktop default. I've been doing some searches to work out how to reset this setting without success and would welcome any pointers. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983202 Title: Link within email not actioned Status in thunderbird package in Ubuntu: New Bug description: Accessing a http or https link in an email has no effect. This is true if I left click on the link or right click and select "Open link in browser". My default browser is Firefox. Just to confuse things it does work occasionally, the first time I open a link after loading Thunderbird. The problem still exists in safe mode. I think the problem started after the update to 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Jul 31 11:51:22 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-08 (721 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 169.254.0.0/16 dev enp45s0 scope link metric 1000 192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.0.2 dev enp45s0 proto static scope link metric 100 192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=91.11.0/20220628000715 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-05-16 (75 days ago) dmi.bios.date: 07/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.10:bd07/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1983202/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983202] Re: Link within email not actioned
find ~/.thunderbird -name handlers.json -print -exec cat '{}' \;
/home/tony/.thunderbird/mmhujxko.default/handlers.json
{"defaultHandlersVersion":{},"mimeTypes":{"application/pdf":{"action":3,"extensions":["pdf"]},"audio/x-wav":{"action":2,"handlers":[{"name":"kaffeine","path":"/usr/bin/kaffeine"}],"extensions":["wav"]},"image/jpeg":{"action":2,"handlers":[{"name":"gwenview","path":"/usr/bin/gwenview"}],"extensions":["jpeg","jpg","jpe"]},"application/zip":{"action":4,"extensions":["zip"]},"application/msword":{"action":4,"extensions":["doc","dot"]},"application/vnd.openxmlformats-officedocument.wordprocessingml.document":{"action":4,"ask":true,"extensions":["docx"]},"application/vnd.ms-excel":{"action":4,"ask":true,"extensions":["xls","xlb","xlt"]},"audio/vnd.wave":{"action":4,"ask":true},"image/tiff":{"action":2,"ask":true,"handlers":[{"name":"GNU
Image Manipulation
Program","path":"/usr/bin/gimp-2.8"}],"extensions":["tif","tiff"]},"application/x-xpinstall":{"action":2,"ask":true,"handlers":[{"name":"Thunderbird
Mail","path":"/usr/bin/thunderbird"}],"extensions":["xpi"]},"image/png":{"action":2,"ask":true,"handlers":[{"name":"Okular","path":"/usr/bin/okular"}],"extensions":["png"]},"application/rtf":{"action":4,"ask":true,"extensions":["rtf"]},"application/vnd.oasis.opendocument.text":{"action":4,"ask":true,"extensions":["odt"]},"text/plain":{"action":2,"ask":true,"extensions":["txt","asc","text","pot","brf","srt"],"handlers":[{"name":"Kate","path":"/usr/bin/kate"}]},"application/vnd.ms-word.document.macroenabled.12":{"action":4,"ask":true,"extensions":["docm"]},"application/vnd.oasis.opendocument.spreadsheet":{"action":4,"ask":true,"extensions":["ods"]},"image/*":{"action":0,"ask":true,"handlers":[{"name":"gwenview","path":"/usr/bin/gwenview"}],"extensions":["jpg","jpeg","jpe"]},"application/vnd.openxmlformats-officedocument.spreadsheetml.sheet":{"action":4,"ask":true,"extensions":["xlsx"]},"application/vnd.openxmlformats-officedocument.presentationml.presentation":{"action":4,"ask":true,"extensions":["pptx"]}},"schemes":{"http":{"action":2,"handlers":[{"name":"Firefox
Web Browser","command":"env
%u"},{"name":"thunderbird","path":"/usr/bin/thunderbird"}]},"https":{"action":2,"handlers":[{"name":"Firefox
Web Browser","command":"env
BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/firefox_firefox.desktop
/snap/bin/firefox %u"}]}}}
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1983202
Title:
Link within email not actioned
Status in thunderbird package in Ubuntu:
New
Bug description:
Accessing a http or https link in an email has no effect. This is
true if I left click on the link or right click and select "Open link
in browser". My default browser is Firefox.
Just to confuse things it does work occasionally, the first time I
open a link after loading Thunderbird.
The problem still exists in safe mode. I think the problem started
after the update to 22.04
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1
ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
Uname: Linux 5.15.0-41-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.11-0ub
[Desktop-packages] [Bug 1983202] [NEW] Link within email not actioned
Public bug reported: Accessing a http or https link in an email has no effect. This is true if I left click on the link or right click and select "Open link in browser". My default browser is Firefox. Just to confuse things it does work occasionally, the first time I open a link after loading Thunderbird. The problem still exists in safe mode. I think the problem started after the update to 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Jul 31 11:51:22 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-08 (721 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 169.254.0.0/16 dev enp45s0 scope link metric 1000 192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.0.2 dev enp45s0 proto static scope link metric 100 192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js user.js Profiles: Profile0 (Default) - LastVersion=91.11.0/20220628000715 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to jammy on 2022-05-16 (75 days ago) dmi.bios.date: 07/01/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.10 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B550-A PRO (MS-7C56) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.10:bd07/01/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7C56 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1983202 Title: Link within email not actioned Status in thunderbird package in Ubuntu: New Bug description: Accessing a http or https link in an email has no effect. This is true if I left click on the link or right click and select "Open link in browser". My default browser is Firefox. Just to confuse things it does work occasionally, the first time I open a link after loading Thunderbird. The problem still exists in safe mode. I think the problem started after the update to 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thunderbird 1:91.11.0+build2-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BuildID: 20220628000715 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Jul 31 11:51:22 2022 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-08 (721 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev enp45s0 proto dhcp metric 100 169.254.0.0/16 dev enp45s0 scope link metric 1000 192.168.0.0/24 dev enp45s0 proto kernel scope link src 192.168.0.10 metric 100 192.168.0.2 dev enp45s0 proto static scope link metric 100 192.168.99.0/24 via 192.168.0.2 dev enp45s0 proto static metric 100 Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-95bfd992-10a3-4228-94df-b2a300210101 PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js user.js Profiles: Profile0 (Default) -
[Desktop-packages] [Bug 1981286] Re: Firefox will not start if home folder not in /home
I suppose my point is that Firefox shouldn't have made the decision to move to snap when there was a known problem. We don't usually make changes knowing they make things worse. ** Package changed: snapd (Ubuntu) => firefox (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1981286 Title: Firefox will not start if home folder not in /home Status in firefox package in Ubuntu: Incomplete Bug description: When a user's home directory is not in /home Firefox will not start. If I try to start Firefox from the command line the following message is output. Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. It appears this is a result of the decision to use Snap to install Firefox. If so then this shouldn't have happened until the limitation on Snap had been removed. Kubuntu 22.04 Firefox 102.0.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981286] [NEW] Firefox will not start if home folder not in /home
Public bug reported: When a user's home directory is not in /home Firefox will not start. If I try to start Firefox from the command line the following message is output. Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. It appears this is a result of the decision to use Snap to install Firefox. If so then this shouldn't have happened until the limitation on Snap had been removed. Kubuntu 22.04 Firefox 102.0.1-1 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1981286 Title: Firefox will not start if home folder not in /home Status in firefox package in Ubuntu: New Bug description: When a user's home directory is not in /home Firefox will not start. If I try to start Firefox from the command line the following message is output. Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. It appears this is a result of the decision to use Snap to install Firefox. If so then this shouldn't have happened until the limitation on Snap had been removed. Kubuntu 22.04 Firefox 102.0.1-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944727] Re: Screen shot leaves HP printer in non-working state
Re-installing the printer using the CUPS browser interface solved the issue. There seem to be some difference between this method and using the Ubuntu Settings tool. Issue is resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state Status in gnome-screenshot package in Ubuntu: New Bug description: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output
For the benefit of others I had a similar problem with Kaffeine 2.0.18 on Lubuntu 20.04.3, no video with DVB-T broadcast and only audio working. The upgrade to 21.0.3 broke a system that was stable for about a year. Also Kaffeine will crash changing channels. Running Kaffeine from command prompt shows unable to decode video messages type messages. Finally tracked down this ticket and down leveling to 20.0.4 solved problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1939455 Title: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output Status in mesa package in Ubuntu: New Bug description: Hello! As reported here https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1939447 upgrading mesa-vdpau-drivers package from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video hardware acceleration. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mesa-vdpau-drivers 21.0.3-0ubuntu0.2~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124 Uname: Linux 5.4.0-80-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Aug 11 02:21:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] MachineType: HP HP 245 G5 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic root=UUID=e8820090-c9e5-4245-bcb4-92818bd91e34 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.08 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.14 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.08:bd04/21/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.14:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.sku: Y9Q66PC#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-12T15:11:08.785042 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953629] Re: Failied to mount Windows share: Invalid argument
*** This bug is a duplicate of bug 1953687 *** https://bugs.launchpad.net/bugs/1953687 ** This bug has been marked a duplicate of bug 1953687 Samba connected network devices no longer appear in "Windows Network" folder of Nautilus. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1953629 Title: Failied to mount Windows share: Invalid argument Status in samba package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. Failed to mount Windows share: Invalid argument I would expect access to my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Version table: *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.13.5+dfsg-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 70-snap.firefox.rules Date: Wed Dec 8 14:16:35 2021 InstallationDate: Installed on 2015-06-21 (2362 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: O07KT44AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00: dmi.product.family: IdeaCentre dmi.product.name: 90BX0018UK dmi.product.sku: LENOVO_PN_Lenovo E50-00 dmi.product.version: Lenovo E50-00 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1953629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1953629] Re: Failied to mount Windows share: Invalid argument
** Description changed: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. - Failied to mount Windows share: Invalid argument + Failed to mount Windows share: Invalid argument - I would expect access my NAS. + I would expect access to my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: - Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 - Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 - Version table: - *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 - 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2:4.13.5+dfsg-2ubuntu2 500 - 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages + Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 + Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 + Version table: + *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 + 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2:4.13.5+dfsg-2ubuntu2 500 + 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 70-snap.firefox.rules Date: Wed Dec 8 14:16:35 2021 InstallationDate: Installed on 2015-06-21 (2362 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: O07KT44AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00: dmi.product.family: IdeaCentre dmi.product.name: 90BX0018UK dmi.product.sku: LENOVO_PN_Lenovo E50-00 dmi.product.version: Lenovo E50-00 dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1953629 Title: Failied to mount Windows share: Invalid argument Status in samba package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. Failed to mount Windows share: Invalid argument I would expect access to my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Version table: *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.13.5+dfsg-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules
[Desktop-packages] [Bug 1953629] [NEW] Failied to mount Windows share: Invalid argument
Public bug reported: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. Failied to mount Windows share: Invalid argument I would expect access my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Version table: *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.13.5+dfsg-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 70-snap.firefox.rules Date: Wed Dec 8 14:16:35 2021 InstallationDate: Installed on 2015-06-21 (2362 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/29/2014 dmi.bios.release: 1.68 dmi.bios.vendor: LENOVO dmi.bios.version: O07KT44AUS dmi.board.name: Aptio CRB dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993 WIN dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrO07KT44AUS:bd08/29/2014:br1.68:svnLENOVO:pn90BX0018UK:pvrLenovoE50-00:rvnLENOVO:rnAptioCRB:rvrSDK0F82993WIN:cvnLENOVO:ct3:cvrNone:skuLENOVO_PN_LenovoE50-00: dmi.product.family: IdeaCentre dmi.product.name: 90BX0018UK dmi.product.sku: LENOVO_PN_Lenovo E50-00 dmi.product.version: Lenovo E50-00 dmi.sys.vendor: LENOVO ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1953629 Title: Failied to mount Windows share: Invalid argument Status in samba package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: When trying to access my NAS using Files or to do a backup which saves on my NAS I get this error message. Failied to mount Windows share: Invalid argument I would expect access my NAS. I am using Ubuntu version 21.10 Note that /etc/samba/smb.conf was updated yesterday. samba: Installed: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Candidate: 2:4.13.14+dfsg-0ubuntu0.21.10.3 Version table: *** 2:4.13.14+dfsg-0ubuntu0.21.10.3 500 500 http://gb.archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.13.5+dfsg-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu impish/main amd64 Packages NOTE: Previously when I had the same problem, I added client min protocol = NT1 to smb.conf but it has not cured this problem. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.simplenote.rules 70-snap.qr-code-generator-desktop.rules 70-snap.snap-store.rules 70-snap.chromium.rules 70-snap.easy-openvpn.rules 70-snap.gnome-system-monitor.rules 70-snap.canonical-livepatch.rules 70-snap.firefox.rules Date: Wed Dec 8 14:16:35 2021 InstallationDate: Installed on 2015-06-21 (2362 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 90BX0018UK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=2e321d15-1961-4c45-b1ce-7662ab1eee40 ro quiet splash vt.handoff=7 SourcePackage:
[Desktop-packages] [Bug 1951756] [NEW] 317
Public bug reported: flatpak document portal session opened no listed reason for deployment or operation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: flatpak (not installed) ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 21 18:44:30 2021 InstallationDate: Installed on 2020-04-01 (599 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: flatpak (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1951756 Title: 317 Status in flatpak package in Ubuntu: New Bug description: flatpak document portal session opened no listed reason for deployment or operation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: flatpak (not installed) ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 21 18:44:30 2021 InstallationDate: Installed on 2020-04-01 (599 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: flatpak UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1951756/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1941752]
*** Bug 443651 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1941752]
*** Bug 443069 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Unknown Status in exiv2 package in Ubuntu: Confirmed Status in gwenview package in Ubuntu: Confirmed Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944727] Re: Screen shot leaves HP printer in non-working state
Here's an example file that produces the issue. ** Attachment added: "This file only print once on my HP printer" https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+attachment/5527367/+files/Print-once.odt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state Status in gnome-screenshot package in Ubuntu: New Bug description: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1944727] [NEW] Screen shot leaves HP printer in non-working state
Public bug reported: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. ** Affects: gnome-screenshot (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1944727 Title: Screen shot leaves HP printer in non-working state Status in gnome-screenshot package in Ubuntu: New Bug description: This is a weird bug and difficult to debug. However: I have Ubuntu 21.04 fully updated as of 2021-09-23. Printing something that has been captured by gnome-screenshot will print fine with my HP Color Laserjet Pro M477fdw printer. However, it will leave the printer in a state where any subsequent print will fail, regardless of document or machine. Even printing from a Macbook Air will fail. The printer reports any subsequent file to be printed as corrupt and nothing comes out. The only way to recover from this state is to power-cycle the printer. This ONLY happen with screenshots. It happens BOTH when the screenshot has been pasted into Libre Office, and when the screenshot has been saved to a .png and printed from Image Viewer. This issue does however NOT happen on my CANON Pro 100 inkjet printer. So blame the printer, yes, but I have not been able to repeat it without gnome-screenshot. It's the common factor. Before Ubuntu 21.04 the default screen capture program was different, or at least it looked different, but previously I had no problem. I have been running Ubuntu with this printer for many years. Summary: I can only print screenshots once. I expect to be able to print two screen shots in sequence without requiring to power cycle the printer in between. I can upload an example file (that only print once) if required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1944727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933118] Re: Screen freeze
And it occurred a second time, just a few minutes after I posted the previous message. in case it is useful, I attach the output from dmesg created while the UI was frozen, also the Xorg.log and another copy of the output from journalctl -b-1 > prevboot.txt Again the freeze corresponded with a movement of the USB external mouse. ** Attachment added: "zip contains dmesg, Xorg.0.log and prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+attachment/5506992/+files/info.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Desktop-packages] [Bug 1933118] Re: Screen freeze
As requested I am adding the output from journalctl -b-1 > prevboot.txt Just to add some further info: * I reinstalled my Ubuntu system yesterday back to the same version (my wifi and bluetooth were not working and I could find no way to get them back, so this freeze has happened with a standard install of 20.04 LTS downloaded and installed yesterday afternoon and otherwise is working normally. * The freeze happened immediately after I installed and used Microsoft Teams (64 bit). That might be a coincidence. * The freeze often happens as I move the mouse from my external monitor to my main (laptop) screen. ** Attachment added: "This is the output from journalctl -b-1 > prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1933118/+attachment/5506986/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1933118] Re: Screen freeze
1. Look in /var/crash for crash files There are files in /var/crash but dated June 15 2021, one from _usr_lib_slack_slack and one from _opt_google_chrome_chrome. Nothing from 21 June (yesterday) when the issue last happened. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID There is nothing recent reported on that page. The most recent reports correspond to the Slack (https://errors.ubuntu.com/oops/0b7133f8-cdfb-11eb-9cf8-fa163ee63de6) and Chrome (https://errors.ubuntu.com/oops/1277eade-cdfb-11eb-a58b-fa163e983629) issues from June 15. There is an older gnome-shell error dated 2021-05-21 16:05 with this link: https://errors.ubuntu.com/oops/3373e2ec-ba4b- 11eb-9041-fa163e102db1 and also an even earlier gnome-shell error dated 2021-03-23 14:03 with this link https://errors.ubuntu.com/oops/0bcaf4d6-8be6-11eb-93be-fa163e6cac46 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. I have applied that work around and will follow that advice. * Next time the problem happens, wait 10 seconds, reboot and then run: The next time the issue happens i will attach the output from journalctl. * Check the 'Extensions' app to ensure you don't have any extensions other than the three Ubuntu extensions The only three extensions reported are "Desktop Icons", "Ubuntu AppIndicators", and "Ubuntu Dock" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Screen freeze Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias:
[Desktop-packages] [Bug 1933118] [NEW] Xorg freeze
Public bug reported: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot of work. If I try the 'REISUB' method of shutting down, it usually does not work. If I remote log in and do a shutdown, it takes several minutes to actually shut down - as if waiting for some process to time out. I haven't any obvious errors for this bug, and i don't know where to look for possible error messages. It is possible that if there is a deadlock, there is no error message, unless shutting down causes the process to generate an error message. The bug happens very often, sometimes several times a week. If you could tell me what commands to run when the problem occurs in order to gather more information, I can remote login and run those commands. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 21 15:14:30 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: v4l2loopback, 0.12.3, 5.8.0-53-generic, x86_64: installed v4l2loopback, 0.12.3, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Since before I upgraded GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GK107GLM [Quadro K1100M] [103c:2256] InstallationDate: Installed on 2021-01-11 (161 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ZBook 17 G2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-55-generic root=UUID=62a0870e-1f83-43a4-a2ff-864901a24fb6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2015 dmi.bios.release: 1.12 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.12 dmi.board.name: 2255 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 3.16 dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.12:bd09/23/2015:br1.12:efr3.16:svnHewlett-Packard:pnHPZBook17G2:pvrA3009DD10203:rvnHewlett-Packard:rn2255:rvrKBCVersion03.10:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP ZBook 17 G2 dmi.product.sku: G6Z41AV dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze possible-manual-nvidia-install third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1933118 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: This bug appears to be a deadlock of some kind. It most often happens when I move the mouse (external USB mouse), but it has once happened when I left the computer logged in but idle and has sometimes happened in video conferences. When the problem occurs, the mouse cursor still moves and any audio continues being audible for a while, but the UI is frozen and unresponsive. The fan gets very loud as if the computer is doing a lot
[Desktop-packages] [Bug 1915704] [NEW] Specific pointing device disappear/disconnect when standby
Public bug reported: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport: https://bugs.launchpad.net/ubuntu/+bug/1573454 But it seems not totaly the same, since I've the problem with a pointer and not the other one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Mon Feb 15 12:07:10 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK107 [GeForce GTX 650] [19da:1288] MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=1768f602-2494-474b-970a-2f71d61fca4b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 14.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd07/21/2020:br14.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915704 Title: Specific pointing device disappear/disconnect when standby Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport:
[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
Bug also occurs on gnome software in groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1903286] [NEW] Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative
Public bug reported: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1903286 Title: Pi400 Bluetooth device not being recognised, Bluetooth manager and Bluetooth adaptors commands show no screen output and appear inoperative Status in bluez package in Ubuntu: New Bug description: Trying to use a Bluetooth mouse with Pi400 running latest Mate 20.10 desktop,to save using a USB port. The mouse does not get recognised, double clicking either Bluetooth Adaptors or Bluetooth Manager has no effect. Full update run this morning. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluetooth 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-1006.9-raspi 5.8.14 Uname: Linux 5.8.0-1006-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Nov 6 10:31:06 2020 ImageMediaBuild: 20201028 InterestingModules: bnep bluetooth Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 video=HDMI-A-1:1920x1080M@60 video=HDMI-A-2:1920x1080M@60 smsc95xx.macaddr=DC:A6:32:E0:8E:57 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 net.ifnames=0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) acpidump: hciconfig: rfkill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1903286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1752108] Re: WebKitWebProcess crashed with SIGSEGV in WTFCrash()
Happened when I selected Run for the Groovy live USB boot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1752108 Title: WebKitWebProcess crashed with SIGSEGV in WTFCrash() Status in webkit2gtk package in Ubuntu: Confirmed Bug description: . ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: libwebkit2gtk-4.0-37 2.19.91-1ubuntu1 Uname: Linux 4.15.0-041500rc7-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 10:24:38 2018 ExecutablePath: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess InstallationDate: Installed on 2017-10-20 (129 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 1 38 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f3dde11674c : movl $0x0,(%rax) PC (0x7f3dde11674c) ok source "$0x0" ok destination "(%rax)" (0xbbadbeef) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: webkit2gtk StacktraceTop: WTFCrash () from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-4.0.so.18 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /usr/lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 Title: WebKitWebProcess crashed with SIGSEGV in WTFCrash() UpgradeStatus: Upgraded to bionic on 2017-11-21 (98 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1752108/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
I understand and the solution is better than the one I am used to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
I attempted to drag a language format to the top before the bug report but nothing happened and attempted to drag again recently but it works as long as the green line is visible at the top before releasing the left mouse button. Marked it as invalid. The Language support app's first impression may confuse new users. Marked it as invalid because I am used to selecting a language instead of dragging the language to the top. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] Re: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
** Changed in: language-selector (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: Invalid Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892458] [NEW] Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome
Public bug reported: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system-wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: language-selector (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "language support.png" https://bugs.launchpad.net/bugs/1892458/+attachment/5403323/+files/language%20support.png ** Summary changed: - Cannot change from one langauge format to another in the language tab of language-selector-gnome for example from English US to English UK + Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/1892458 Title: Cannot change from one language format to another for example from English US to English UK in the language tab of language-selector- gnome Status in language-selector package in Ubuntu: New Bug description: Ubuntu automatically sets the English US language as the system language for the region that I reside in which mainly the English UK language as one of its official languages but not the English US language. When using the Language Support app to attempt to change the system language and regional formats to English UK, the English UK option is greyed out and cannot be selected in the Languages tab. To properly change the language in Ubuntu, I used the Gnome settings to change the language and the regional formats, restarted the shell, and used the Language Support app to apply the regional formats system- wide so that it can apply to the display manager as well. In Xubuntu or any other official Ubuntu flavour that uses the Ubiquity installer for installation and only uses the gnome language selector for language and region formats selection. Changing from one format of a language to another for example from English US to English UK is not possible graphically with the Language Support app alone because the desired language format, for example, English UK is greyed out and not selectable. The attached screenshot illustrates the issue but in this case, attempting to change from English UK to English US by using the language support app alone to attempt the language change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: language-selector-gnome 0.204 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Aug 21 08:41:06 2020 InstallationDate: Installed on 2020-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: language-selector UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1892458/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post
[Desktop-packages] [Bug 1890100] [NEW] software-properties-gtk 0.98.9.1 crash
Public bug reported: Software & Updates keeps crashing when I tried to reload software list. It will not work and I have to force to close it. I have sent the bug report using report a bug feature. I do not know how to retrieve the bug. It says it is a duplicate of bugs of 1832057. 1. Description: Ubuntu 20.04.1 LTS Release:20.04 2. software-properties-gtk: Installed: 0.98.9.1 Candidate: 0.98.9.1 Version table: *** 0.98.9.1 500 500 http://jp.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://jp.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9 500 500 http://jp.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://jp.archive.ubuntu.com/ubuntu focal/main i386 Packages 3.Expected to work and function without error ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1890100 Title: software-properties-gtk 0.98.9.1 crash Status in software-properties package in Ubuntu: New Bug description: Software & Updates keeps crashing when I tried to reload software list. It will not work and I have to force to close it. I have sent the bug report using report a bug feature. I do not know how to retrieve the bug. It says it is a duplicate of bugs of 1832057. 1. Description: Ubuntu 20.04.1 LTS Release: 20.04 2. software-properties-gtk: Installed: 0.98.9.1 Candidate: 0.98.9.1 Version table: *** 0.98.9.1 500 500 http://jp.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://jp.archive.ubuntu.com/ubuntu focal-updates/main i386 Packages 100 /var/lib/dpkg/status 0.98.9 500 500 http://jp.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://jp.archive.ubuntu.com/ubuntu focal/main i386 Packages 3.Expected to work and function without error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1890100/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1407928] Re: [phone] Does not auto-switch to available, known WiFi
** Changed in: network-manager (Ubuntu) Assignee: Tony Espy (awe) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1407928 Title: [phone] Does not auto-switch to available, known WiFi Status in Canonical System Image: Confirmed Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Confirmed Bug description: This might not be the place for this bug, please reassign as appropriate. I was only able to reproduce this on mako/rtm, krillin/vivid seems to behave better (but I do remember the same issue there). Steps: * connect to a password-protected WiFi network * go out of range * make sure a GSM connection is established * go back in the WiFi range Expected: * phone connects to the known WiFi automatically Current: * phone does not connect to WiFi Please find attached network-test-session logs from when I toggled WiFi and Plane mode to get some data on the issue. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: indicator-network 0.5.1+15.04.20141215~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Tue Jan 6 12:01:55 2015 InstallationDate: Installed on 2014-12-18 (18 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141218-163635) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered upstart.indicator-network.log: Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered Attempted to unregister path (path[0] = org path[1] = freedesktop) which isn't registered To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880305] Re: Failed to mount Windows share: Software caused connection abort
** No longer affects: nautilus (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1880305 Title: Failed to mount Windows share: Software caused connection abort Status in samba package in Ubuntu: New Bug description: Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS. What happens: In Nautilus (1:3.36.2-0ubuntu1) I do the following 1. Go to Other Locations 2. Click on Windows Network 3. Double Click on WORKGROUP 4. Double Click on DYLAN (the NAS at 192.168.1.5) 5. Double Click on public (a folder that does not require a password) I get the error message 'Unable to access location. Failed to mount windows share: Software caused connection abort'. What should happen: Following the above steps the public folder opens and shows the files and folders in it. My backups using Deja Dup also get this error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 14:13:33 2020 InstallationDate: Installed on 2015-06-21 (1797 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-15 (7 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880305] Re: Failed to mount Windows share: Software caused connection abort
Have created a workaround which works: 1. created directory ~/.smb 2. copied /etc/samba/smb.conf to it 3. added 'client min protocol = NT1' to [global] section. as suggested in bug #1879776 ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1880305 Title: Failed to mount Windows share: Software caused connection abort Status in nautilus package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS. What happens: In Nautilus (1:3.36.2-0ubuntu1) I do the following 1. Go to Other Locations 2. Click on Windows Network 3. Double Click on WORKGROUP 4. Double Click on DYLAN (the NAS at 192.168.1.5) 5. Double Click on public (a folder that does not require a password) I get the error message 'Unable to access location. Failed to mount windows share: Software caused connection abort'. What should happen: Following the above steps the public folder opens and shows the files and folders in it. My backups using Deja Dup also get this error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 14:13:33 2020 InstallationDate: Installed on 2015-06-21 (1797 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-15 (7 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1880305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880305] [NEW] Failed to mount Windows share: Software caused connection abort
Public bug reported: Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS. What happens: In Nautilus (1:3.36.2-0ubuntu1) I do the following 1. Go to Other Locations 2. Click on Windows Network 3. Double Click on WORKGROUP 4. Double Click on DYLAN (the NAS at 192.168.1.5) 5. Double Click on public (a folder that does not require a password) I get the error message 'Unable to access location. Failed to mount windows share: Software caused connection abort'. What should happen: Following the above steps the public folder opens and shows the files and folders in it. My backups using Deja Dup also get this error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 14:13:33 2020 InstallationDate: Installed on 2015-06-21 (1797 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-15 (7 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1880305 Title: Failed to mount Windows share: Software caused connection abort Status in nautilus package in Ubuntu: New Bug description: Since upgrading from 19.10 to 20.04 I cannot access folders on my NAS. What happens: In Nautilus (1:3.36.2-0ubuntu1) I do the following 1. Go to Other Locations 2. Click on Windows Network 3. Double Click on WORKGROUP 4. Double Click on DYLAN (the NAS at 192.168.1.5) 5. Double Click on public (a folder that does not require a password) I get the error message 'Unable to access location. Failed to mount windows share: Software caused connection abort'. What should happen: Following the above steps the public folder opens and shows the files and folders in it. My backups using Deja Dup also get this error. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 23 14:13:33 2020 InstallationDate: Installed on 2015-06-21 (1797 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-05-15 (7 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1880305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877655] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369849/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369846/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369852/+files/Xrandr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369850/+files/ProcModules.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369851/+files/UdevDb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369847/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369853/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369848/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Re: Synaptic Trackpad does not work in Xorg sessions
I should note - I did try out xserver-xorg-input-synaptics yesterday prior to getting your email, it had no effect One thing I did find, I'm not sure if it has any bearing, but my current kernel is: 5.4.0-7626-generic With this kernel, as I mentioned before I could move the trackpad at the login screen, but the buttons didn't work; on login, no mouse input worked. I came across a thread about certain kernels having regression issues with certain trackpads, so I tried the original kernel that came with my distribution: 5.4.0-7625-generic Now, with that kernel, at the login screen I can move the trackpad AND use the trackpad buttons; still once I'm fully logged into the desktop the trackpad doesn't work at all. As I mentioned, not sure if this has any bearing, but I thought I should mention it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140
[Desktop-packages] [Bug 1877655] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369845/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369838/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369844/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369843/+files/Lsusb.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369842/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369840/+files/DpkgLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369841/+files/Lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] DkmsStatus.txt
apport information ** Attachment added: "DkmsStatus.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369839/+files/DkmsStatus.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad does not work in Xorg sessions Status in libinput package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1877655] Re: Synaptic Trackpad does not work in Xorg sessions
apport information ** Tags added: apport-collected ubuntu ** Description changed: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. - There is still an issue with Wayland and the trackpad, but it's - different than Xorg so the problem may be in how Xorg is processing the - trackpad (I honestly don't know) - in Wayland, it will work until I - attempt to run the sofware center. + There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27 + Architecture: amd64 + CasperMD5CheckResult: skip + CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' + CompositorRunning: None + DistUpgraded: Fresh install + DistroCodename: focal + DistroRelease: Pop!_OS 20.04 + DistroVariant: ubuntu + ExtraDebuggingInterest: Yes, if not too technical + GraphicsCard: + Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) +Subsystem: Dell HD Graphics 5300 [1028:066b] + MachineType: Dell Inc. Venue 11 Pro 7140 + Package: xorg-server (not installed) + ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash + ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 + Tags: focal ubuntu ubuntu + Uname: Linux 5.4.0-7626-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/10/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A17 + dmi.board.name: 0XMVMH + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: + dmi.product.name: Venue 11 Pro 7140 + dmi.product.sku: 066B + dmi.sys.vendor: Dell Inc. + version.compiz: compiz N/A + version.libdrm2: libdrm2 2.4.101-2 + version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 + version.libgl1-mesa-glx: libgl1-mesa-glx N/A + version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 + version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A + version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 + version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 + version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Attachment added: "BootLog.txt" https://bugs.launchpad.net/bugs/1877655/+attachment/5369837/+files/BootLog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in
[Desktop-packages] [Bug 1877655] Re: Synaptic Trackpad works until actually logged into Xorg desktop
I have no idea what sub group/package this belongs in. I know it affects Gnome and KDE on Xorg. I don't know if GDM (or whatever now handles the login process) does differently from the full gnome that allows the trackpad to at least partially work (movement, but not button clicks) ** Description changed: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. - When at the login page, the trackpad and keyboard operate as they + When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: - Event type 0 (EV_SYN) - Event type 1 (EV_KEY) - Event code 272 (BTN_LEFT) - Event code 325 (BTN_TOOL_FINGER) - Event code 330 (BTN_TOUCH) - Event code 333 (BTN_TOOL_DOUBLETAP) - Event code 334 (BTN_TOOL_TRIPLETAP) - Event type 3 (EV_ABS) - Event code 0 (ABS_X) - Value483 - Min0 - Max 1056 - Resolution 12 - Event code 1 (ABS_Y) - Value266 - Min0 - Max 516 - Resolution 12 - Event code 47 (ABS_MT_SLOT) - Value 0 - Min0 - Max2 - Event code 53 (ABS_MT_POSITION_X) - Value 0 - Min0 - Max 1056 - Resolution 12 - Event code 54 (ABS_MT_POSITION_Y) - Value 0 - Min0 - Max 516 - Resolution 12 - Event code 55 (ABS_MT_TOOL_TYPE) - Value 0 - Min0 - Max2 - Event code 57 (ABS_MT_TRACKING_ID) - Value 0 - Min0 - Max65535 - Event type 4 (EV_MSC) - Event code 5 (MSC_TIMESTAMP) + Event type 0 (EV_SYN) + Event type 1 (EV_KEY) + Event code 272 (BTN_LEFT) + Event code 325 (BTN_TOOL_FINGER) + Event code 330 (BTN_TOUCH) + Event code 333 (BTN_TOOL_DOUBLETAP) + Event code 334 (BTN_TOOL_TRIPLETAP) + Event type 3 (EV_ABS) + Event code 0 (ABS_X) + Value483 + Min0 + Max 1056 + Resolution 12 + Event code 1 (ABS_Y) + Value266 + Min0 + Max 516 + Resolution 12 + Event code 47 (ABS_MT_SLOT) + Value 0 + Min0 + Max2 + Event code 53 (ABS_MT_POSITION_X) + Value 0 + Min0 + Max 1056 + Resolution 12 + Event code 54 (ABS_MT_POSITION_Y) + Value 0 + Min0 + Max 516 + Resolution 12 + Event code 55 (ABS_MT_TOOL_TYPE) + Value 0 + Min0 + Max2 + Event code 57 (ABS_MT_TRACKING_ID) + Value 0 + Min0 + Max65535 + Event type 4 (EV_MSC) + Event code 5 (MSC_TIMESTAMP) Properties: - Property type 0 (INPUT_PROP_POINTER) - Property type 2 (INPUT_PROP_BUTTONPAD) + Property type 0 (INPUT_PROP_POINTER) + Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) - - I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. + I did try to remove xserver-xorg-input-synaptics, but it is not + installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. ** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: Synaptic Trackpad works until actually logged into Xorg desktop Status in xorg package in Ubuntu: New Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver
[Desktop-packages] [Bug 1875289] Re: Firefox Screen Tearing
The screen tearing only happens with Firefox and video screen tearing only happens in full-screen mode in Firefox. No screen tearing with other browsers and media players. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1875289 Title: Firefox Screen Tearing Status in firefox package in Ubuntu: Incomplete Bug description: Screen tearing on Firefox when watching a video or scrolling down a webpage with a lot of text. Steps to reproduce video screen tearing 1. Open Firefox browser on and go to Youtube 2. Select a video but I recommend a screen tearing video test 3. View the whole video and screen tearing occurs. Steps to reproduce scroll tearing 1. Open a webpage on Firefox that has a lot of text like a Wiki 2. Scroll down the page and tearing is seen when scrolling Tried recording the screen with Kazam to illustrate the issue but it does not record the screen tearing. Tested on Chromium but no screen tearing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tony 1840 F pulseaudio /dev/snd/controlC0: tony 1840 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:33:26 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8444 dmi.board.vendor: HP dmi.board.version: 67.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4UL47EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875289] Re: Firefox Screen Tearing
** This bug is no longer a duplicate of bug 1754284 Fullscreen windows are tearing in Xorg sessions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1875289 Title: Firefox Screen Tearing Status in firefox package in Ubuntu: Incomplete Bug description: Screen tearing on Firefox when watching a video or scrolling down a webpage with a lot of text. Steps to reproduce video screen tearing 1. Open Firefox browser on and go to Youtube 2. Select a video but I recommend a screen tearing video test 3. View the whole video and screen tearing occurs. Steps to reproduce scroll tearing 1. Open a webpage on Firefox that has a lot of text like a Wiki 2. Scroll down the page and tearing is seen when scrolling Tried recording the screen with Kazam to illustrate the issue but it does not record the screen tearing. Tested on Chromium but no screen tearing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tony 1840 F pulseaudio /dev/snd/controlC0: tony 1840 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:33:26 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8444 dmi.board.vendor: HP dmi.board.version: 67.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4UL47EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875289] Re: Firefox Screen Tearing
Yes it occurs in X11 session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1875289 Title: Firefox Screen Tearing Status in firefox package in Ubuntu: Incomplete Bug description: Screen tearing on Firefox when watching a video or scrolling down a webpage with a lot of text. Steps to reproduce video screen tearing 1. Open Firefox browser on and go to Youtube 2. Select a video but I recommend a screen tearing video test 3. View the whole video and screen tearing occurs. Steps to reproduce scroll tearing 1. Open a webpage on Firefox that has a lot of text like a Wiki 2. Scroll down the page and tearing is seen when scrolling Tried recording the screen with Kazam to illustrate the issue but it does not record the screen tearing. Tested on Chromium but no screen tearing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tony 1840 F pulseaudio /dev/snd/controlC0: tony 1840 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:33:26 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8444 dmi.board.vendor: HP dmi.board.version: 67.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4UL47EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1875289/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875289] [NEW] Firefox Screen Tearing
Public bug reported: Screen tearing on Firefox when watching a video or scrolling down a webpage with a lot of text. Steps to reproduce video screen tearing 1. Open Firefox browser on and go to Youtube 2. Select a video but I recommend a screen tearing video test 3. View the whole video and screen tearing occurs. Steps to reproduce scroll tearing 1. Open a webpage on Firefox that has a lot of text like a Wiki 2. Scroll down the page and tearing is seen when scrolling Tried recording the screen with Kazam to illustrate the issue but it does not record the screen tearing. Tested on Chromium but no screen tearing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tony 1840 F pulseaudio /dev/snd/controlC0: tony 1840 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:33:26 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-04-27 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.32 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:733 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=75.0/20200403170909 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.65 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8444 dmi.board.vendor: HP dmi.board.version: 67.33 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.65:bd12/06/2019:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn8444:rvr67.33:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.sku: 4UL47EA#BH5 dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1875289 Title: Firefox Screen Tearing Status in firefox package in Ubuntu: New Bug description: Screen tearing on Firefox when watching a video or scrolling down a webpage with a lot of text. Steps to reproduce video screen tearing 1. Open Firefox browser on and go to Youtube 2. Select a video but I recommend a screen tearing video test 3. View the whole video and screen tearing occurs. Steps to reproduce scroll tearing 1. Open a webpage on Firefox that has a lot of text like a Wiki 2. Scroll down the page and tearing is seen when scrolling Tried recording the screen with Kazam to illustrate the issue but it does not record the screen tearing. Tested on Chromium but no screen tearing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tony 1840 F pulseaudio /dev/snd/controlC0: tony 1840 F pulseaudio BuildID: 20200403170909 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 09:33:26 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensi
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Tried attaching recording of the issue on chrome and chromium and also firefox for comparison but the video cannot be played on this end since it got corrupted here but Ok on my PC and chromium bug report. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Reattached The chromium screencast since the file was corrupted here and comments are not editable ** Attachment removed: "firefox switch.mp4" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+attachment/5358985/+files/firefox%20switch.mp4 ** Attachment removed: "chromium switch lag.mp4" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+attachment/5358976/+files/chromium%20switch%20lag.mp4 ** Attachment added: "chromium switch lag.mp4" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+attachment/5359122/+files/chromium%20switch%20lag.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Screencast of Firefox also attached for comparison ** Attachment added: "firefox switch.mp4" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+attachment/5358985/+files/firefox%20switch.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Attached screencasts of Chromium to demonstrate the issue ** Attachment added: "chromium switch lag.mp4" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+attachment/5358976/+files/chromium%20switch%20lag.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
comment#4 In X11 session and not using any dpi scaling because my laptop's screen does not require scaling. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Updated Chromium snap to Version 81.0.4044.92 (Official Build) snap (64-bit) recently but the switching a youtube video to full-screen and back is still laggy but playback is still smooth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] Re: Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Olivier, Playback is smooth but the switching to full-screen mode and back is laggy. Output of the command is: The authorization page: (https://launchpad.net/+authorize-token?oauth_token=0JLWTDmMkwMH1vNl0trs_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... Package chromium-browser not installed and no hook available, ignoring. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871618] [NEW] Switching playing youtube video to full-screen mode and to default mode lag on Chromium
Public bug reported: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: - The switching of a playing youtube video to fullscreen and also from fullscreen to normal view lags. + The switching of a playing youtube video to fullscreen and also from + fullscreen to normal view lags. + Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen and back is expected to be smooth but instead, the switching is laggy. ** Summary changed: - Switching youtube video to fullscreen and to default view lag on Chromium + Switching playing youtube video to full-screen mode and to default mode lag on Chromium ** Description changed: - The switching of a playing youtube video to fullscreen and also from - fullscreen to normal view lags. + The switching of a playing youtube video to fullscreen mode and also + from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. - When playing a video using chromium the switch to full-screen and back - is expected to be smooth but instead, the switching is laggy. + When playing a video using chromium the switch to full-screen mode and + back is expected to be smooth but instead, the switching is laggy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1871618 Title: Switching playing youtube video to full-screen mode and to default mode lag on Chromium Status in chromium-browser package in Ubuntu: New Bug description: The switching of a playing youtube video to fullscreen mode and also from fullscreen mode to normal mode lags. Ubuntu version: 19:10 Chromium version: 80.0.3987.163 (Official Build) snap (64-bit) Steps to reproduce 1. Launch Chromium and open Youtube. 2. Select/search for a video and play. 3. Switch the playing video to full-screen mode and back to normal view. When playing a video using chromium the switch to full-screen mode and back is expected to be smooth but instead, the switching is laggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1871618/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
@osomon One way to cause Thunderbird to freeze the system except mouse cursor and TTY can be accessed: Try opening a clean/fresh/purged then reinstalled installation of Thunderbird and set up email like yahoo or google, as the emails sync, click on the hamburger/three short parallel horizontal icon on the left, click Preferences, click Toolbar layout, then disable the title bar. After closing the Toolbar layout window, two orange (Ubuntu default theme) dots are still shown on the dock beside the icon. Clicking the icon causes the issue. Issue also occurs also on the snap package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: Incomplete Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
Update to #5 The WiFi always fails to connect in a TTY with the error: rtlwifi: AP off, try to reconnect now. The WiFi card is the Realtek rtl8723de. I can only download/ping from a TTY via Ethernet connection. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: Incomplete Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
The WiFi that I use refuses to connect via the TTY and works with the graphical session. In the graphical session the WiFi connects sometimes instantly, sometimes with a delay or connects when the Airplane mode is turned on then off again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: Incomplete Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870111] Re: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
@osomon I notice that it always causes the system to freeze when WiFi is in use. The WiFi card is rtl8723de which is not in the kernel and I installed it from lwfinger git clone using dkms. With LAN it works fine and does not cause the system to freeze. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: Incomplete Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870111] [NEW] Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch
Public bug reported: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Summary changed: - Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup + Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1870111 Title: Thunderbird freezes graphical session except mouse cursor on second launch or clicking the icon after email setup on the first launch Status in thunderbird package in Ubuntu: New Bug description: When Launching thunderbird (pinned on Favourites) from the dock/dash it shows 2 orange dots on default theme that is one for email setup and the other for the main window. After setting up an email and closing the email config window, the two dots are still shown on the dash/dock before the icon. Thunderbird causes the graphical session except for the mouse cursor to freeze until I switch to a TTY and reboot. Also when closing thunderbird, one dot is shown and when launching the application the graphical session except for mouse cursor freezes. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: thunderbird 1:68.4.1+build1-0ubuntu0.19.10.1 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.7 Architecture: amd64 BuildID: 20200110143530 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 13:26:59 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1141 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2020-03-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=68.4.1/20200110143530 SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1870111/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852874] Re: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled.
I am having this same issue with release 79.0.3945.117; DNS failures on VPN, OK without; attaching log for more info. Chrome and Firefox are Ok on VPN or off. ** Attachment added: "chrome-net-export-log.json" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852874/+attachment/5322195/+files/chrome-net-export-log.json -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1852874 Title: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled. Status in chromium-browser package in Ubuntu: Incomplete Bug description: Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) on Ubuntu 19.10, Intel® Core™ i7-8550U CPU @ 1.80GHz × 8, GeForce GTX 1050/PCIe/SSE2. Since my upgrade to 19.10, snap chromium will not connect when VPN is enabled. Chromium does connect when VPN is disabled. Access NetworkManager service is enabled in chromium snap. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 16 14:52:46 2019 InstallationDate: Installed on 2019-10-05 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: chromium-browser UpgradeStatus: Upgraded to eoan on 2019-10-26 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1852874/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1626731] Re: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized!
For anyone who is still having this problem, hopefully this will help you get your webcam working. I was able to get my webcam working and I am using a Dell Precision 7510 Laptop running Ubuntu 18.04.3. 1.) I issued "$dmesg | grep -i camera" in a terminal window and received "uvcvideo 1-11:1.0: Entity type for entity Camera 1 was not initialized!" which landed me here at this website (FYI I am still receiving that message and my camera works... as laurent.pinchart +bugzilla-kernel pointed out already it is a harmless warning). 2) I did a search for "ubuntu uvcvideo" in google and landed on "https://help.ubuntu.com/community/UVC; which then pointed me to "https://www.berlios.de/software/linux-uvc/#download; which then pointed me to "http://www.ideasonboard.org/uvc/;. 3) From "http://www.ideasonboard.org/uvc/;, if you scroll down to the bottom of it you will see a Downlaod section. Navigate to the "https://www.linuxtv.org/wiki/index.php/How_to_Obtain; webpage and follow the "Basic" User's Approach instructions. 4) You may be asked to install pre-requisites during the build process. I had to issue the following command "$sudo apt install libproc- processtable-perl". 5) Once build is complete, run "$sudo make install". 6) I installed uvcdynctrl as floe suggested. I don't know if this helped or not sorry... 7) I then found and example file to test if the camera was working from "https://linuxtv.org/downloads/v4l-dvb-apis/uapi/v4l/v4l2grab.c.html;. I saved this file and tried to compile it "$gcc -o v4l2grab v4l2grab.c" and received an error that it couldn't find the libv4l2.h header file. So i searched for it using $sudo find / -name "libv4l2.h" and didn't find it. This led me to believe that I didn't have the v4l2 development library installed so I installed it $sudo apt install libv4l-dev. 8) I searched again and found it! I then set C include environment path variable to point to the directory containing the header file $export C_INCLUDE_PATH=/usr/include/ and changed #include "../libv4l/include/libv4l2.h" to just #include "libv4l2.h" 9) Tried to recompile and got a linking error, so I issued $gcc -o v4l2grab v4l2grab.c -lv4l1 -lv4l2 and waula, it compiled. Changed its permssions to be executable $chmod +755 v4l2grab (using octal format where 7 in binary is 111 corresponding to rwx for owner and 5 or 110 rw- for group and other) and ran it ./v4l2grab where then I saw the .ppm files in the directory where the executable was ran from, but this was not good enough I want live feed. 10) I then installed v4l-utils and ran $v4l2-ctl -d /dev/video0 --list- formats-ext. This gave me the parameters that are compatible with my webcam for video capture (width=1280, height=720, format=MJPG, and device index=0). 11) As a final death blow I ran the following v4l2-ctl -V --set-fmt-video=width=1280,height=720,pixelformat=MJPG --stream-mmap --stream-count=-1 --stream-to=test.jpg -d /dev/video0 but only got a single image. I think you need to incude OpenCV. Anyways, I hope this helps you atleast get images off of the webcam. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1626731 Title: uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: [6.453850] uvcvideo 1-1.4:1.0: Entity type for entity Extension 4 was not initialized! [6.453858] uvcvideo 1-1.4:1.0: Entity type for entity Processing 2 was not initialized! [6.453862] uvcvideo 1-1.4:1.0: Entity type for entity Camera 1 was not initialized! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-14-generic 4.8.0-14.15 ProcVersionSignature: Ubuntu 4.8.0-14.15-generic 4.8.0-rc7 Uname: Linux 4.8.0-14-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2032 F...m pulseaudio /dev/snd/controlC0: caravena 2032 F pulseaudio CurrentDesktop: GNOME Date: Thu Sep 22 17:20:51 2016 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (424 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-14-generic N/A linux-backports-modules-4.8.0-14-generic N/A linux-firmware1.161 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
Re: [Desktop-packages] [Bug 1830231] Re: Firefox will not connect to any website
OK - this fixed the problem;
https://askubuntu.com/questions/1145311/internet-is-working-but-firefox-
browser-cannot-connect
Answer 2
2
I was having the same issue. Removing prefs.js did not fix the problem
for me.
Restarting firefox via Menu -> Help -> "Restart with Add-ons Disabled"
and choosing to restart in "safe mode" gave me a working browser.
I opened a regular instance of firefox again and it was still not
working (obviously). I repeated the "Restart with Add-ons Disabled" but
selected "Refresh Firefox" at the final step and it seems to have fixed
the problem.
I went back through the preferences section and have changed back all of
my settings there and I haven't broken the browser yet.
Again, this doesn't get to the root of the problem, but perhaps it
narrows it down some? Maybe someone else knows more about what all gets
reset when you choose "Refresh Firefox"?
So this works - and the problem seems to be something inside Firefox,
possibly due to Add-Ons, the basis of which seems to have been changed.
This bug can be closed.
Regards
Tony Morton
Yes, the same issue. I am using the Opera browser while Firefox is out
of action, and Opera works fine. Does that help pin down a difference?
This problem only began after the Ubuntu update on Tuesday 21st which
was a list of system files, so maybe something that Firefox depends upon
was changed then?
The journalctl package is not installed on my system.
On 23/05/2019 22:01, Sebastien Bacher wrote:
> Thank you for your bug report. do you get the same issue if you start a
> private browsing session? Could you add your journalctl bug?
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1830231
Title:
Firefox will not connect to any website
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Firefox will not connect to any website, it opens properly and will
open files from my PC, there is nothing wrong with my wi-fi or
internet connection. Any request for a web address results in the
continuing spinning icon in the tab and it never connects to any web
address. This follows upon Ubuntu software updates on Tuesday 21st May
2019
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 67.0+build2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tony 2152 F pulseaudio
/dev/snd/controlC0: tony 2152 F pulseaudio
BrokenPermissions:
healthreport/state.json (0o600, wrong owner)
sessionstore.bak (0o600, wrong owner)
BuildID: 20190517140819
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu May 23 15:15:36 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-09-30 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.10 metric 600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0/20190517140819
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0478VN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 660s
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1830231/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1830231] Re: Firefox will not connect to any website
Yes, the same issue. I am using the Opera browser while Firefox is out
of action, and Opera works fine. Does that help pin down a difference?
This problem only began after the Ubuntu update on Tuesday 21st which
was a list of system files, so maybe something that Firefox depends upon
was changed then?
The journalctl package is not installed on my system.
On 23/05/2019 22:01, Sebastien Bacher wrote:
> Thank you for your bug report. do you get the same issue if you start a
> private browsing session? Could you add your journalctl bug?
>
> ** Changed in: firefox (Ubuntu)
> Status: New => Incomplete
>
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1830231
Title:
Firefox will not connect to any website
Status in firefox package in Ubuntu:
Incomplete
Bug description:
Firefox will not connect to any website, it opens properly and will
open files from my PC, there is nothing wrong with my wi-fi or
internet connection. Any request for a web address results in the
continuing spinning icon in the tab and it never connects to any web
address. This follows upon Ubuntu software updates on Tuesday 21st May
2019
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 67.0+build2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tony 2152 F pulseaudio
/dev/snd/controlC0: tony 2152 F pulseaudio
BrokenPermissions:
healthreport/state.json (0o600, wrong owner)
sessionstore.bak (0o600, wrong owner)
BuildID: 20190517140819
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu May 23 15:15:36 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-09-30 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.10 metric 600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0/20190517140819
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0478VN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 660s
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1830231/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1830231] [NEW] Firefox will not connect to any website
Public bug reported:
Firefox will not connect to any website, it opens properly and will open
files from my PC, there is nothing wrong with my wi-fi or internet
connection. Any request for a web address results in the continuing
spinning icon in the tab and it never connects to any web address. This
follows upon Ubuntu software updates on Tuesday 21st May 2019
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 67.0+build2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tony 2152 F pulseaudio
/dev/snd/controlC0: tony 2152 F pulseaudio
BrokenPermissions:
healthreport/state.json (0o600, wrong owner)
sessionstore.bak (0o600, wrong owner)
BuildID: 20190517140819
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu May 23 15:15:36 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-09-30 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.10 metric 600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0/20190517140819
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0478VN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA11:bd10/14/2013:svnDellInc.:pnInspiron660s:pvr:rvnDellInc.:rn0478VN:rvrA00:cvnDellInc.:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Inspiron 660s
dmi.sys.vendor: Dell Inc.
** Affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1830231
Title:
Firefox will not connect to any website
Status in firefox package in Ubuntu:
New
Bug description:
Firefox will not connect to any website, it opens properly and will
open files from my PC, there is nothing wrong with my wi-fi or
internet connection. Any request for a web address results in the
continuing spinning icon in the tab and it never connects to any web
address. This follows upon Ubuntu software updates on Tuesday 21st May
2019
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: firefox 67.0+build2-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tony 2152 F pulseaudio
/dev/snd/controlC0: tony 2152 F pulseaudio
BrokenPermissions:
healthreport/state.json (0o600, wrong owner)
sessionstore.bak (0o600, wrong owner)
BuildID: 20190517140819
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Thu May 23 15:15:36 2019
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@firefox.mozilla.org
English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2018-09-30 (234 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
(20180725)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.10 metric 600
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/firefox/omni.ja:greprefs.js:1151
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=67.0/20190517140819
RunningIncompatibleAddons: True
SourcePackage: firefox
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/14/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dm
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Updated Ubuntu-18.04 LTS, rebooted and problem is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: Confirmed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Confirmed Status in console-setup source package in Cosmic: Confirmed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Status in console-setup source package in Disco: In Progress Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: Confirmed Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Confirmed Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same: $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
It's back! Me too on Ubuntu 18.04.2 LTS. Maybe it was package keyboard-configuration_1.178ubuntu2.8_all.deb? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Attached is Xorg log for the boot of 4.4.0-145 ** Attachment added: "Xorg log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255955/+files/Xorg.0.log.old -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824641] Re: Blank screen after booting 4.4.0-145
Attached is a syslog for the boot of 4.4.0-145 from start up to shut down in the way described above. ** Attachment added: "Syslog from boot of 4.4.0-145" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+attachment/5255939/+files/syslog4.4.0-145 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1824641 Title: Blank screen after booting 4.4.0-145 Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Bug description: Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot this kernel everything is blank. Just a black screen. If I change to a terminal using Ctrl Alt F4 it is still a black screen but I can carefully type in my user name and password and then the shutdown command and it shuts down Using Advanced options in grub neither the upstart or the recovery option work. The screen is still black. The recovery option does, however, display the boot sequence before going black. I can boot the previous kernel 4.4.0-143 and all is OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
