[Desktop-packages] [Bug 271216] Re: Firefox prints one page only of long doc in a frame
This was fixed in Firefox 85. ** Changed in: firefox (Ubuntu) Status: Triaged => Fix Released -- 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/271216 Title: Firefox prints one page only of long doc in a frame Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Binary package hint: mozilla-firefox Firefox 3.01 printing: I have two frames, one containing a document that should take many pages to print. Firefox only prints one page, losing the rest. Typical site: http://www.cict.bhtafe.edu.au/subjects/ict321/bug.html It also prints one page for multi-frame documents from web access to M/S Exchange such as http://www.cict.bhtafe.edu.au/subjects/bug/MicrosoftOutlookWebAccess.html Another problem site is http://septemberfestival.com.au/index.php?option=com_content&task=view&id=4&Itemid=4 which prints three pages but still loses a lot of content Package is Ubuntu 8.10 alpha5, but problem has occurred in many other distros and earlier versions of firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/271216/+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 1969901] Re: network-manager fails to renew ipv6 address
** Tags added: patch
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => Triaged
--
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/1969901
Title:
network-manager fails to renew ipv6 address
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
Triaged
Bug description:
[Impact]
* This affects Ubuntu 18.04 where Network Manager version 1.10.6 is
used.
* Network manager might kill dhclient(6) and fail to start it again
causing the IPv6 address to be lost on a network that uses mixed
IPv4/IPV6.
The network status will still be seen as online in gnome since ipv4
is still active.
The user then have to manually remove the dhcpv6 lease files and
restart ipv6 connection/restart network manager to regain IPv6
connectivity.
* This is a cherry-pick from Network manager 1.10.8 (Ubuntu's version
is based on 1.10.6):
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7fbbe7ebee99785e38d39c37e515a64a28edef0f
* Upstream bug:
https://bugzilla.gnome.org/show_bug.cgi?id=783391
[Test Plan]
The test requires three computers
* one computer runing isc dhcpd server (with network configured static)
* one computer running patched network manager
* one computer running vanilla ubuntu
The idea is to execute on an isolated network and trigger the error by
changing
ip range handed out by the dhcp-server to force a nack response back to the
clients.
Expected result
* patched network keeps dhclient6 alive
* vanilla network manager will fail to keep dhclient6 alive
in network manager logs dhcp6 will expire and not be restarted
ON THE SERVER
# Disable app-armor, as it has rules restricting dhcpd
aa-teardown
# install isc dhcpserver
isc-dhcp-server
# configure network static
sudo nmcli connection modify "${CONNECTION_NAME}" \
ipv4.method "manual" \
ipv4.addresses "192.168.1.1/24" \
ipv4.gateway "192.168.1.254" \
ipv4.dns "192.168.1.1" \
ipv6.method "manual" \
ipv6.addresses "2001:db8:0:1::1/64" \
ipv6.gateway "2001:db8:0:1::ffbb" \
ipv6.dns "2001:db8:0:1::1/64"
mkdir -p tmp
touch tmp/dhcpd4_a.leases
touch tmp/dhcpd4_b.leases
touch tmp/dhcpd6_a.leases
touch tmp/dhcpd6_b.leases
Then it is time to execute dhcpd
-f - run in foreground
-d - print errors to stderr instead of syslog
# Start in separate terminals
dhcpd -f -d -4 -cf dhcp_v4_a.conf -lf tmp/dhcpd4_a.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_a.conf -lf tmp/dhcpd6_a.leases enp0s31f6
Press ctrl-C to kill servers, then restart with the b configurations
dhcpd -f -d -4 -cf dhcp_v4_b.conf -lf tmp/dhcpd4_b.leases enp0s31f6
dhcpd -f -d -6 -cf dhcp_v6_b.conf -lf tmp/dhcpd6_b.leases enp0s31f6
Then leases to expire (check for clients that kills dhclient)
Press ctrl-C to kill servers, then restart with the a configurations
ON THE CLIENTS
Setup:
Configure ipv6 network in settings to use dhcp (using the gui)
Test:
check that dhcp clients are still running:
ps aux|grep dhclient
Expected in output
one client for dhcpv4
one client for dhcpv6
Also check network manager status :
journalctl -u NetworkManager.service
journalctl -u NetworkManager.service|grep dhcp6 # to only view dhclient6
journalctl -u NetworkManager.service|grep dhcp4 # to only view dhclient4
if dhclient is not running:
stop network in gui
remove lease files (/var/lib/NetworkManager/dhclient*.lease). Only remove the
lease for the client not running.
start network in gui
if dhclients are running:
wait additional ten minutes, repeat from beginning of test
[Where problems could occur]
* The change is in the dchp lease expiration handling so verify that
there is no regression in dhcp renewals on different type of
configuration include IPv6
[Other Info]
* We have tested this patch on a couple of clients where we have seen this
this problem. If this patch is feasible to include in Ubuntu 18.04 we
could request more users to test.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1969901/+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 1987976] Re: firefox black window on wayland
** No longer affects: firefox (Ubuntu) -- 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/1987976 Title: firefox black window on wayland Status in Mozilla Firefox: Unknown Status in Mutter: New Status in Release Notes for Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Bug description: [ Impact ] On some systems, when you open the Firefox snap right after having logged in into an Ubuntu on Wayland session, you are met by a black window. This happens because the FF snap is run under Xwayland, and Xwayland may not be enabled early enough to handle the start of the application properly. You can easily reproduce the issue in a Wayland session: * Close Firefox * Run the command "killall Xwayland" in terminal * Open Firefox An upstream mutter change addresses this issue, and the proposed lunar change cherry picks that upstream change as a patch. [ Test Plan ] On an updated Ubuntu 23.04: * Install the mutter related binaries from lunar-proposed * Reboot and log in to an Ubuntu on Wayland session * Run the command "killall Xwayland" * Open the Firefox snap, and find that it starts normally [ Where problems could occur ] This is the upstream merge request in question: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2970 The changes (except for the test related ones) are small, and specifically intended to address issues like the one reported in this bug. There are also reviews by a couple of experienced GNOME devs. So even if the proposed change is not well tested yet, it seems to me that the risk for adverse side effects is limited. [ Original description ] nicolas@nicolas-fixe:~$ lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 nicolas@nicolas-fixe:~$ apt-cache policy firefox firefox: Installé : 1:1snap1-0ubuntu2 Candidat : 1:1snap1-0ubuntu2 Table de version : *** 1:1snap1-0ubuntu2 500 500 http://fr.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status When I boot Ubuntu and start Firefox, the Firefox's window is totally black. See attachment. I am at your disposal to answer any question you have. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Aug 28 12:42:29 2022 InstallationDate: Installed on 2022-08-25 (2 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Snap.Changes: aucun changement trouvé SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1987976/+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 1993318] Re: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes
** No longer affects: zsys (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1993318 Title: ZFS + Encryption installations of Ubuntu Desktop do not come up correctly on first boot, systemd unmounts many of the zfs volumes Status in Ubuntu Manual Tests: New Status in Release Notes for Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in ubiquity source package in Jammy: Fix Released Bug description: This is *probably* the wrong package, but it's the best I can figure for this, so here goes. Hardware: Kubuntu Focus XE, 32 GB RAM, 1 TB SSD, 11th Gen Intel Core i5, UEFI, no secure boot. Testing done in GNOME Boxes, BIOS, 4 GB RAM, 50 GB disk space . OS is Ubuntu Desktop, Kinetic Final ISO. [Testcase] tl;dr encrypted-zfs, firstboot, `systemctl daemon-reload` must not unmount half of mountpoints, ie. /var/lib. Steps to reproduce: 1. Boot the Ubuntu desktop ISO. 2. Select "Install Ubuntu" and proceed with the installation process. 3. When you get to the "Installation type" screen, select "Advanced Options", and enable ZFS + Encryption. 4. Proceed with the rest of the installation as normal. 5. Reboot into the newly installed system. 6. Log in. 7. Run "sudo apt update" in a terminal. Expected result: The package database should be updated normally. Actual result: You are presented with the following errors at the end of the apt output: Reading package lists... Error! E: flAbsPath on /var/lib/dpkg/status failed - realpath (2: No such file or directory) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. Notes: Switching to a TTY will print a crash error message related to the same missing /var/lib/dpkg/status file. Running "sudo touch /var/lib/dpkg/status" will allow "sudo apt update" to function and fix the crashed process in the TTY. [End Testcase] Once you log in, you'll notice that Firefox is missing (bug #1993279), and you will likely be presented with a ton of error messages and other scary junk. At least one of those error messages was related to update-manager in my experience, and another one was from "check-new- release-gtk". ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 18 09:55:27 2022 InstallationDate: Installed on 2022-10-18 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221018) ProcEnviron: TERM=xterm-256color PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1993318/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** No longer affects: linux-raspi (Ubuntu Kinetic) ** No longer affects: linux-raspi (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-settings source package in Jammy: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+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 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Changed in: xorg-server (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Jammy) Status: New => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: xserver-xorg-video-nouveau (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Changed in: gdm3 (Ubuntu Focal)
Status: Incomplete => Triaged
** Changed in: gdm3 (Ubuntu Impish)
Status: Incomplete => Triaged
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => Medium
** Changed in: gdm3 (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: gdm3 (Ubuntu Impish)
Importance: Undecided => Medium
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Fix Released
Status in gdm3 package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in gdm3 source package in Focal:
Triaged
Status in ubuntu-drivers-common source package in Focal:
Fix Released
Status in gdm3 source package in Impish:
Triaged
Status in ubuntu-drivers-common source package in Impish:
Fix Released
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to m
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO
** Changed in: ubuntu-drivers-common (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Focal)
Importance: Undecided => High
** Changed in: ubuntu-drivers-common (Ubuntu Impish)
Importance: Undecided => High
--
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/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/iss
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+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 1942789] Re: On-demand and RTD3 need to be separated
** Changed in: nvidia-prime (Ubuntu Hirsute) Status: Invalid => Won't Fix ** Changed in: nvidia-prime (Ubuntu Focal) Importance: Undecided => High ** Changed in: nvidia-prime (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+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 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland
** No longer affects: x11-utils (Ubuntu) ** No longer affects: x11-utils (Ubuntu Focal) ** No longer affects: x11-utils (Ubuntu Impish) ** No longer affects: x11-utils (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-utils in Ubuntu. https://bugs.launchpad.net/bugs/1952947 Title: ubuntu-bug -w (using xprop) doesn't work under wayland Status in apport package in Ubuntu: Fix Released Status in apport source package in Focal: Triaged Status in apport source package in Impish: Triaged Status in apport source package in Jammy: Fix Released Bug description: [Impact] This bug makes it more difficult for Wayland users to report bugs with apport. When a Wayland user tries to use the -w,--window option, apport fails silently. We do not want users to face a high barrier to submitting bug reports. The patch for this bug adds a message explaining that the -w,--window option cannot be used on Wayland, and suggests a method for finding the window's PID instead. [Test Plan] * Log on to Ubuntu on Wayland. You can check that $XDG_SESSION_TYPE=="wayland" in your current session. * Open a terminal, and run `ubuntu-bug -w`. * Click on any other window, and observe that the apport UI will not respond. [Where problems could occur] The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to 'wayland'. If either of these strings in the patch were wrong, or the environment variable was not used in the target release, the condition would likely never be true. [Original Description] I want to report a Bug about the application Studio Controls. As I did it already quite a few times, I run "ubuntu-bug -w", get a message that I can select the window of the app I want to report a bug about after closing this message. I close the message with a click on the appropriate button. I click on the window of the application "Studio Controls" that I want to report a bug about. Nothing happens. I wait for a few minutes. Still nothing happens. In the console where I started ubuntu-bug -w I see the following message: (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384: gdk_wayland_window_set_dbus_properties_libgtk_only: assertion 'GDK_IS_WAYLAND_WINDOW (window)' failed What I expect: Usaully when I use this procedure, after a relatively short while a new message window pops up asking me if the bug should be reported and showing me the data that is sent to Launchpad. I tried other applications, too, same effect. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: apport 2.20.11-0ubuntu71 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 20:01:23 2021 InstallationDate: Installed on 2020-04-12 (597 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+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 1921398] Re: No dns resolution after closing a vpn/sstp connection
** Changed in: ppp (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1921398 Title: No dns resolution after closing a vpn/sstp connection Status in ppp package in Ubuntu: New Bug description: The fix for the following issue closes it for nm-pptp-service-* connections, however; it is still a problem for users using network- manager-sstp. You use network-manager-sstp, connect to your VPN server. Then disconnect and you now can't lookup any hostnames. Original problem #1778946 No dns resolution after closing a vpn/pptp connection This is still a problem for sstp users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1921398/+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 1955044] Re: [SRU] /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected unqualified-id before ‘)’ token (with GCC 11 in C++20 mode)
** Changed in: glibmm2.4 (Ubuntu)
Importance: Undecided => Medium
** Changed in: glibmm2.4 (Ubuntu Impish)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glibmm2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1955044
Title:
[SRU] /usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected
unqualified-id before ‘)’ token (with GCC 11 in C++20 mode)
Status in glibmm2.4 package in Ubuntu:
Fix Released
Status in glibmm2.4 source package in Impish:
Triaged
Bug description:
Impact
==
It's not possible to build using the header under C++20 with the
default compiler, GCC 11. This is interfering with being able to build
telegram-desktop.
This was fixed for Ubuntu 22.04 LTS with 2.66.1
Demonstration of the Issue
==
$ g++ -x c++ -std=gnu++20 -include glibmm.h - <<< 'int main(){}' `pkg-config
--cflags --libs glibmm-2.4` -o /dev/null
In file included from
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
from /usr/include/glibmm-2.4/glibmm.h:92,
from :
/usr/include/glibmm-2.4/glibmm/variant.h:956:24: error: expected
unqualified-id before ‘)’ token
956 | Variant();
|^
/usr/include/glibmm-2.4/glibmm/variant.h:1017:25: error: expected
unqualified-id before ‘)’ token
1017 | Variant< Variant >();
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1070:26: error: expected
unqualified-id before ‘)’ token
1070 | Variant();
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1240:24: error: expected
unqualified-id before ‘)’ token
1240 | Variant();
|^
/usr/include/glibmm-2.4/glibmm/variant.h:1286:30: error: expected
unqualified-id before ‘)’ token
1286 | Variant< std::pair >()
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1335:29: error: expected
unqualified-id before ‘)’ token
1335 | Variant< std::vector >()
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1404:41: error: expected
unqualified-id before ‘)’ token
1404 | Variant< std::vector >();
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1530:39: error: expected
unqualified-id before ‘)’ token
1530 | Variant< std::vector >();
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1606:29: error: expected
unqualified-id before ‘)’ token
1606 | Variant< std::map >()
| ^
/usr/include/glibmm-2.4/glibmm/variant.h:1679:33: error: expected
unqualified-id before ‘)’ token
1679 | Variant>()
| ^
In file included from /usr/include/glibmm-2.4/glibmm/variant.h:1742,
from
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
from /usr/include/glibmm-2.4/glibmm.h:92,
from :
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:23:17: error: expected
unqualified-id before ‘)’ token
23 | Variant()
| ^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:66:26: error: expected
unqualified-id before ‘)’ token
66 | Variant()
| ^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:109:19: error: expected
unqualified-id before ‘)’ token
109 | Variant()
| ^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:152:20: error: expected
unqualified-id before ‘)’ token
152 | Variant()
|^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:195:19: error: expected
unqualified-id before ‘)’ token
195 | Variant()
| ^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:244:20: error: expected
unqualified-id before ‘)’ token
244 | Variant()
|^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:287:19: error: expected
unqualified-id before ‘)’ token
287 | Variant()
| ^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:330:20: error: expected
unqualified-id before ‘)’ token
330 | Variant()
|^
/usr/include/glibmm-2.4/glibmm/variant_basictypes.h:373:19: error: expected
unqualified-id before ‘)’ token
373 | Variant()
| ^
In file included from
/usr/include/glibmm-2.4/glibmm/containerhandle_shared.h:23,
from /usr/include/glibmm-2.4/glibmm/arrayhandle.h:21,
from /usr/include/glibmm-2.4/glibmm.h:92,
from
[Desktop-packages] [Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
** No longer affects: firefox (Ubuntu) ** Bug watch removed: Mozilla Bugzilla #1722369 https://bugzilla.mozilla.org/show_bug.cgi?id=1722369 ** Changed in: gtk+3.0 (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Impish: Fix Committed Bug description: * Impact The clipboard copies from GTK based software sometime stop working under wayland * Test Case - in a wayland session try to copy text between software, from firefox to gedit for example, it should work in a consistent manner alternative testcase inspired from the gitlab ticket - install wl-clipboard - use evince to open a pdf - select and copy some content - on a cmdline do $ wl-paste -t TEXT - try to paste then in another software, gedit for example the copied text should be pasted * Regression potential The changes are in the wayland selection source so the impact should only be for wayland users and limited to clipboard interactions -- Running Firefox 84.0.2 for Ubuntu Canonical-1.0 on Ubuntu 20.04.1 LTS, on Wayland native Version 84.0.2 Build ID 20210105180113 Window Protocol wayland Desktop Environment gnome DESCRIPTION OF THE PROBLEM: If I copy text from a web page and try to paste it into another Firefox page, the text is pasted correctly. If I copy text from a web page and try to paste it in [gedit, libreoffice, thunderbird, terminal, slack (electron)] nothing happens. The Gnome Clipboard extension stays empty when content is copied from Firefox Wayland. Pasting *from* another app *to* Firefox works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Changed in: wpa (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Released
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1875015] Re: Displaylink is extremely slow
** Bug watch removed: gitlab.gnome.org/GNOME/mutter/-/issues #2005 https://gitlab.gnome.org/GNOME/mutter/-/issues/2005 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1065126]
This was fixed by bug 1710941 when browser.download.improvements_to_download_panel=true. That pref is enabled by default in Firefox 97 and later. -- 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/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Fix Released Status in One Hundred Papercuts: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+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 1065126] Re: "Always do this from now on" does not work
Fixed in Firefox 97. ** Changed in: hundredpapercuts Status: Confirmed => Fix Released ** Changed in: firefox (Ubuntu) Status: Confirmed => Fix Released -- 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/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
Fixed in wpa version 2:2.9.0+git2026+0b853303ae31-1
** Changed in: wpa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Committed
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Fixed in gwenview version 21.12.1. --- gwenview (4:21.12.1-0ubuntu1) jammy; urgency=medium * New upstream release (21.12.1) -- Rik Mills Thu, 06 Jan 2022 10:21:02 + ** Changed in: gwenview (Ubuntu) Importance: Undecided => Medium ** Changed in: gwenview (Ubuntu) Status: Confirmed => Fix Released -- 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: Fix Released Status in exiv2 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Fix Released 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] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
** Changed in: exiv2 (Ubuntu) Importance: Undecided => High -- 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: Fix Released 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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: github.com/DisplayLink/evdi/issues #181 https://github.com/DisplayLink/evdi/issues/181 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.
** Also affects: network-manager (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu) Status: Confirmed => Fix Released -- 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/1955797 Title: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems. Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Focal: New Bug description: [Impact] Some 4G/5G mobile networks(for ex., AT&T) requires a specific MTU setting, this setting will be exposed by the ModemManager for network- manger to configure the MTU of the modem network interface . The current modem-manager v1.22.10-1ubuntu2.2 in focal can’t pass AT&T’s modem system certification. [Fix] This upstream patch can resolve this bug: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631 [Test Plan] 1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an AT&T SIM card in US 2. Enable 4G modem and connect to AT&T apn $ sudo mmcli -i 0 --pin= $ sudo mmcli --modem 0 --enable $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome" $ sudo nmcli radio wwan on $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn emome $ sudo nmcli connection up id mymodem 3. Check if the MTU got from the following results are the same: $ sudo mmcli --bearer 5 | mtu $ ifconfig mhi_mbim0 | grep mtu * Expected result: Both MTUs are the same value 1430 * Actual tested result: Different values (one is 1430 , another is 1500) [Where problems could occur] Very low. This is a simple fix: network-manager gets the MTU from the ModemManager then sets the MTU of the modem interface. [Other info] 1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+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 1955566] Re: iris driver doesn't load correctly on intel pci_id 0x4688
** Changed in: mesa (Ubuntu) Importance: Undecided => Low -- 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/1955566 Title: iris driver doesn't load correctly on intel pci_id 0x4688 Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: New Bug description: [Impact] * iris driver doesn't load with pci_id 4688. Instead, it uses llvm. we expect the Intel GPU uses iris driver. [Test Plan] * $ DISPLAY=:0 glxinfo | grep -i opengl OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits) ... OpenGL version string: 3.1 Mesa 21.0.3 * After applying the fix, it shows: * $ DISPLAY=:0 glxinfo | grep -i opengl OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (ADL-S GT1) ... OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 (git-d4975a0dbc) [Where problems could occur] * This patch is backport the PCI ID mapping for enabling iris driver which is expected when users have a GPU. * If there is any issue occur then we need to fix it with iris driver. [Other Info] * It already in upstream and we have a platform which using ADL-HX in OEM project. Thus, we need to enable iris on it at least on focal. * The patch is simple as to add "CHIPSET(0x4688, adl_gt1, "ADL-S GT1", "Intel(R) Graphics")" in "include/pci_ids/iris_pci_ids.h". * Patch backported from df5b14969f9869f363bcc8b2a564c85aaa481597 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955566/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Fix Released
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Released
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1350038] Re: HPLIP Status Service doesn't work with plasma5 system tray
** Summary changed: - Regression: systray needs compatibility adjustments to work with plasma5 + HPLIP Status Service doesn't work with plasma5 system tray -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1350038 Title: HPLIP Status Service doesn't work with plasma5 system tray Status in hplip package in Ubuntu: Fix Released Bug description: plasma5 does no longer support the ancient xembed systray but instead requires a status-notifier-item. to transparently allow for qt4 applications using qsystemtray to continue working in plasma5 a compatibility patch + runtime binary is recommended by the plasma developers. currently hp-systray is not compatbile with this and requires a patch that allows for receiving qsignals while waiting for a systray to become available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1350038/+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 1350038] Re: Regression: systray needs compatibility adjustments to work with plasma5
This is fixed in Ubuntu Xenial and later. --- hplip (3.16.3+repack0-1) unstable; urgency=medium * Imported Upstream version 3.16.3 -- Julian Andres Klode Sat, 19 Mar 2016 11:38:01 +0100 ** Changed in: hplip (Ubuntu) Status: New => Fix Released ** Bug watch removed: bugzilla.suse.com/ #908358 https://bugzilla.suse.com/show_bug.cgi?id=908358 ** Tags added: regression-release -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1350038 Title: Regression: systray needs compatibility adjustments to work with plasma5 Status in hplip package in Ubuntu: Fix Released Bug description: plasma5 does no longer support the ancient xembed systray but instead requires a status-notifier-item. to transparently allow for qt4 applications using qsystemtray to continue working in plasma5 a compatibility patch + runtime binary is recommended by the plasma developers. currently hp-systray is not compatbile with this and requires a patch that allows for receiving qsignals while waiting for a systray to become available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1350038/+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 1302437] Re: hplip cups backends crash constantly
** Project changed: hplip => ubuntu ** No longer affects: ubuntu ** Tags added: patch-accepted-debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1302437 Title: hplip cups backends crash constantly Status in hplip package in Ubuntu: Fix Released Bug description: Easily provoked by e.g. "lpinfo -v". ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: hplip 3.14.3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CupsErrorLog: E [04/Apr/2014:02:04:30 -0700] Unable to bind socket for address [v1.::1]:631 - Cannot assign requested address. E [04/Apr/2014:02:10:40 -0700] [CGI] Failed to initialize libusb (-99) E [04/Apr/2014:02:10:40 -0700] [cups-deviced] PID 3148 (hp) crashed on signal 11! E [04/Apr/2014:02:10:40 -0700] [cups-deviced] PID 3157 (hpfax) crashed on signal 11! E [04/Apr/2014:02:10:41 -0700] [cups-deviced] PID 3142 (gutenprint52+usb) stopped with status 4! Date: Fri Apr 4 02:10:40 2014 ExecutablePath: /usr/lib/cups/backend/hp InstallationDate: Installed on 2014-03-28 (6 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter ProcCmdline: hp ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-22-generic root=UUID=82a9f05f-32d0-45f7-b302-894b3fdfe56e ro find_preseed=/preseed.cfg noprompt quiet SegvAnalysis: Segfault happened at: 0x7f4e43472414 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi PC (0x7f4e43472414) ok source "0x10(%rdi)" (0x0030) not located in a known VMA region (needed readable region)! destination "%esi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: hplip StacktraceTop: __GI___pthread_mutex_lock (mutex=0x0) at ../nptl/pthread_mutex_lock.c:66 libusb_get_device_list () from /lib/x86_64-linux-gnu/libusb-1.0.so.0 ?? () from /usr/lib/libhpmud.so.0 hpmud_probe_devices () from /usr/lib/libhpmud.so.0 ?? () Title: hp crashed with SIGSEGV in __GI___pthread_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 07/02/2012 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2012:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1302437/+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 1298194] Re: HP LaserJet 4000 PostScript PPD buggy
This is fixed in Ubuntu Trusty and later. --- hplip (3.14.3-0ubuntu2) trusty; urgency=low * debian/local/HP-LaserJet_4000-PostScript-PPD.patch, debian/rules: Patch PPD file for the HP LaserJet 4000 to use the same JobPatchFile as the LaserJet 4050. It seems that the 4000 has the same PS interpreter bug to work around. Note that it is not possible to use the standard mechanisms for patches as HP ships all PPDs compressed (Closed: #742766). -- Till KamppeterThu, 27 Mar 2014 17:20:00 +0100 ** Project changed: hplip => hplip (Ubuntu) ** Changed in: hplip (Ubuntu) Status: New => Fix Released ** Tags added: patch patch-accepted-debian -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1298194 Title: HP LaserJet 4000 PostScript PPD buggy Status in hplip package in Ubuntu: Fix Released Status in hplip package in Debian: New Bug description: When I upgraded my Debian system from Squeeze to Wheezy, I had two problems with printing. My printer is a HP LaserJet 4000, with a JetDirect card and plenty of memory (384KB). I'm using the PostScript PPD, because the other PPDs don't allow me to select most printer options. The printer was working fine in Squeeze. I had to fix two problems to make my printer work in the new version of CUPS (1.5.3) and hp-drivers (3.12.6). The first problem is an issue I had already fixed in Squeeze, and needed to fix again. The PPD for the HP LaserJet 4000 is misisng a critical postscript workaround. The HP LaserJet 4000 and HP LaserJet 4050 are effectively the same printer, just a faster processor (I know, I also have a 4050). The fix was to extract the workaround from the PPD for the 4050 and insert that in the PPD for the 4000. The other differences between the PPDs are related to job storage, and I don't use that which is why I did not try to backport it. The patch for the PPD for the 4000 is attached. The original file name seems to be HP4000_5.PPD. The second problem, which is new is Wheezy, is that PDF to PS renderer need to be changed. The default, GostScript, absolutely choke the printer. After many minutes, either the printer print an error message, or just stop processing witout printing anything. To change the renderer, I needed to do : lpadmin -p -o pdftops-renderer-default=pdftops The documentation claim that changing the rendered will loose color accuracy, which is most likely not an issue for a black and white printer. I hope it's possible to change the default renderer for all those old printers so that printer drivers work out of the box, because tracking down those things takes time. Thanks ! Jean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1298194/+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 244295] Re: PATCH ATTACHED: Short-edge duplex does not work with HPIJS if duplex is PJL-controlled (most non-PostScript laser printers)
** Project changed: hplip => hplip (Ubuntu) ** Changed in: hplip (Ubuntu) Status: Confirmed => Fix Released ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/244295 Title: PATCH ATTACHED: Short-edge duplex does not work with HPIJS if duplex is PJL-controlled (most non-PostScript laser printers) Status in hplip package in Ubuntu: Fix Released Bug description: I am using the HP Color LaserJet 3600 with HPLIP 2.8.6 on Ubuntu Intrepid. Problem is that the duplex orientation is not respected. Independent if I choose long-edge or short-edge, I get always the duplex orientation for long-edge-bound (portrait) documents. The problem is not caused by broken PostScript input nor by a bug in foomatic-rip, as the Ghostscript command line is reported as follows in error_log (CUPS in debug mode): gs -sstdout=%stderr -dBATCH -dPARANOIDSAFER -dQUIET -dNOPAUSE -sDEVICE=ijs -sIjsServer=hpijs -sDeviceManufacturer="HEWLETT-PACKARD" -sDeviceModel="hp color LaserJet 3600" -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dDuplex=true -dTumble=true -r600 -sIjsParams=Quality:Quality=2,Quality:ColorMode=2,Quality:MediaType=0,Quality:PenSet=2,PS:MediaPosition=7 -dIjsUseOutputFD -sOutputFile=%stdout - It contains the "-dTumble=true" which tells the driver to use short- edge orientation. I have tested only with the HP Color LaserJet 3600 (PPD of the proprietary plug-in). Please test also with other printer device classes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/244295/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: github.com/DisplayLink/evdi/issues #181 https://github.com/DisplayLink/evdi/issues/181 ** Bug watch removed: github.com/DisplayLink/evdi/issues #61 https://github.com/DisplayLink/evdi/issues/61 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1931547] Re: DisplayLink displays are black after Mesa update
** Bug watch removed: github.com/DisplayLink/evdi/issues #279 https://github.com/DisplayLink/evdi/issues/279 ** Tags removed: fixed-upstream verification-needed ** Tags added: patch-accepted-upstream ** Tags added: regression-update -- 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/1931547 Title: DisplayLink displays are black after Mesa update Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Fix Released Status in xorg-server source package in Impish: Fix Released Bug description: [Impact] On Mesa versions before 21.0.x glamor_egl_init failed which then (luckily) disabled reverse_prime_offload_mode. But now with the new Mesa the GL_RENDERER has changed and glamor_egl_init succeeds and then enables reverse_prime_offload_mode. This backported commit disables reverse_prime_offload_mode for good for DisplayLink (udl, evdi) devices. [Test case] Update xserver, check that DisplayLink device (udl and/or evdi as available) works fine. [Where things could go wrong] This commit only disables reverse_prime_offload_mode for udl, evdi devices, other devices will not be affected. 'udl' is used by old USB2 based DisplayLink devices that have a native kernel driver 'evdi' is used by newer USB3 based devices that use an out-of-tree driver provided by Displaylink both need the same change, as they are otherwise similar at least evdi devices (as found on some laptop docks) have been tested to work with this -- Please incorporate xorg-server fix for issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 It was already merged in to xserver master and xserver-1.20-branch branches. https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/681 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/683 This is reported by our users reports on Ubuntu 20.10 with Xserver-1.20.9 and on Ubuntu 21.04 with XServer-1.20.11 If it is required i am willing to help with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1931547/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/-/issues #1183 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1183 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1350038] Re: Regression: systray needs compatibility adjustments to work with plasma5
** Project changed: hplip => hplip (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1350038 Title: Regression: systray needs compatibility adjustments to work with plasma5 Status in hplip package in Ubuntu: New Bug description: plasma5 does no longer support the ancient xembed systray but instead requires a status-notifier-item. to transparently allow for qt4 applications using qsystemtray to continue working in plasma5 a compatibility patch + runtime binary is recommended by the plasma developers. currently hp-systray is not compatbile with this and requires a patch that allows for receiving qsignals while waiting for a systray to become available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1350038/+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 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
xorg-server (2:1.20.11-1ubuntu1~20.04.2) focal; urgency=medium * modesetting-disable-reverse-prime-offload-udl.diff: Fix a regression on displaylink devices after mesa update. (LP: #1931547) xorg-server (2:1.20.11-1ubuntu1~20.04.1) focal; urgency=medium * Backport to focal. (LP: #1925320) - don't disable building xwayland -- Timo Aaltonen Tue, 06 Jul 2021 13:17:51 +0300 ** Also affects: xorg-server (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu Focal) Status: New => Fix Released ** Changed in: xorg-server (Ubuntu Focal) Importance: Undecided => Medium -- 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/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+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 1824260] Re: wrong kerning in SS-5 PDF form fields
** Project changed: poppler => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Remote watch: gitlab.freedesktop.org/poppler/poppler/issues #753 => None ** No longer affects: ubuntu ** Bug watch removed: gitlab.freedesktop.org/poppler/poppler/issues #753 https://gitlab.freedesktop.org/poppler/poppler/issues/753 ** Bug watch removed: gitlab.gnome.org/GNOME/evince/issues #1127 https://gitlab.gnome.org/GNOME/evince/issues/1127 ** Bug watch added: gitlab.freedesktop.org/fontconfig/fontconfig/-/issues #262 https://gitlab.freedesktop.org/fontconfig/fontconfig/-/issues/262 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1824260 Title: wrong kerning in SS-5 PDF form fields Status in Fontconfig: Unknown Status in fontconfig package in Ubuntu: Fix Released Bug description: What I expected to happen: I am filling out the SS-5 Social Security Administration form (see attached). I entered "John Jacob Smith" into the "First", "Full Middle Name", and "Last" fields on page 5. What happened instead: I can enter the text without issue, but some of the letters are wrongly positioned, i.e. the kerning is wrong. For example, the letter "i" overlaps with the letter "m" in "Smith" (see attached image). It looks like the font in the fields might be displaying a variable width font when it is supposed to be a fixed-wdith font. Discussion: Since this bug is also present in xpdf and Okular (but not mupdf), I'm guessing this isn't a bug in Evince itself. However, I am reporting it here as a courtesy to other users (since Evince is the default PDF reader) and because I'm not sure which dependency is responsible. (I'm also not sure if it's a direct dependency problem or if it's something else like a font configuration issue.) Here is the output for pdffonts ss-5.pdf: name type encoding emb sub uni object ID - --- --- --- - IHPIKC+ArialMT CID TrueType Identity-H yes yes yes824 0 ArialMT TrueType WinAnsi no no no 826 0 Arial-BoldMT TrueType WinAnsi no no no 828 0 CourierStd Type 1WinAnsi no no no 145 0 HelveticaType 1WinAnsi no no no 197 0 MyriadPro-RegularType 1WinAnsi no no no 198 0 ZapfDingbats Type 1ZapfDingbats no no no 199 0 I asked about this in an Ask Ubuntu question nearly a year ago, but received no response, so I am reporting a bug now instead: https://askubuntu.com/questions/1031235/wrong-letter-positioning-and- font-in-pdf-form Ubuntu version: Description: Ubuntu 18.04.2 LTS Release: 18.04 evince version: $ apt-cache policy evince evince: Installed: 3.28.4-0ubuntu1 Candidate: 3.28.4-0ubuntu1 Version table: *** 3.28.4-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.2-1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 10 21:27:11 2019 InstallationDate: Installed on 2018-12-12 (119 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/1824260/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Bug watch added: gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues #37 https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/37 ** Also affects: xf86-video-amd via https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/-/issues/37 Importance: Unknown Status: Unknown ** Tags removed: fixed-upstream ** Tags added: patch-accepted-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in Nouveau Xorg driver: Unknown Status in OEM Priority Project: New Status in xf86-video-amd: Unknown Status in X.Org X server: Unknown Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: In Progress Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Released Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+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 1950214] Re: raspi 64 bit Impish image fails update-initramfs with OOM on zstd
** Changed in: ubuntu-settings (Ubuntu Impish) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu Jammy) Importance: Undecided => High ** Changed in: ubuntu-settings (Ubuntu Impish) Importance: High => Medium ** Changed in: ubuntu-settings (Ubuntu Jammy) Importance: High => Medium ** No longer affects: initramfs-tools (Ubuntu Jammy) ** No longer affects: initramfs-tools (Ubuntu Impish) ** No longer affects: initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1950214 Title: raspi 64 bit Impish image fails update-initramfs with OOM on zstd Status in ubuntu-settings package in Ubuntu: Confirmed Status in ubuntu-settings source package in Impish: Confirmed Status in ubuntu-settings source package in Jammy: Confirmed Bug description: When attempting to 'apt upgrade' on the pi zero 2 with the 64 bit Impish image and nothing new installed to it, update-initramfs fails like so: Setting up linux-firmware (1.201.1) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 A simple workaround for now is to switch to the old lz4 default: $ sudo apt install lz4 $ sudo sed -i -e '/^COMPRESS=/ c COMPRESS=lz4' /etc/initramfs-tools/initramfs.conf Original Workaround === Adding a swap file to the setup allowed 'apt -f install' to run successfully. How the device was setup 1) xzcat | dd the sdcard with the impish 64 bit server image 2) setup for serial over USB (dtoverlay=dwc2, modules-load=dwc2,g_serial, link getty@ttyGS0.service ) as suggested in https://www.tal.org/tutorials/raspberry-pi-zero-usb-serial-console 3) resize partition 2 - fdisk delete partition 2 and recreate to use the rest of the 16GB flash, e2fsck, resize2fs 4) cp bcm2710-rpi-3-b.dtb bcm2710-rpi-zero-2.dtb per https://waldorf.waveform.org.uk/2021/the-pi-zero-2.html 5) boot, connect to wireless, ssh in 6) apt update && apt upgrade 7) observe above issue ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-firmware 1.201.1 ProcVersionSignature: Ubuntu 5.13.0-1009.10-raspi 5.13.14 Uname: Linux 5.13.0-1009-raspi aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 8 19:47 seq crw-rw 1 root audio 116, 33 Nov 8 19:47 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-1009-raspi. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu71 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Mon Nov 8 21:00:59 2021 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 ImageMediaBuild: 20211013 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lspci-vt: -[:00]- Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M PackageArchitecture: all PciMultimedia: ProcFB: 0 BCM2708 FB ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:5C:DA:C8 vc_mem.mem_base=0x1ec0 vc_mem.mem_size=0x2000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash modules-load=dwc2,g_serial Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-firmware StagingDrivers: bcm2835_mmal_vchiq snd_bcm2835 bcm2835_isp bcm2835_v4l2 bcm2835_codec vc_sm_cma Title: package linux-firmware 1.201.1 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1950214/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Focal: Fix Committed Status in pulseaudio source package in Hirsute: Won't Fix Status in pulseaudio source package in Impish: Fix Committed Status in pulseaudio source package in Jammy: Fix Committed Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+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 1946599] Re: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta
Fixed in Firefox 94 ** Changed in: firefox (Ubuntu) Status: Fix Committed => Fix Released -- 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/1946599 Title: Firefox break when returning from console with wayland (nvidia) on ubuntu 21.10 beta Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Fix Released Bug description: (again snap firefox) Returning from console break all firefox tabs which have to be refreshed mv@i56400:~$ firefox [GFX1-]: glxtest: libEGL missing [GFX1-]: glxtest: EGL test failed xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb xkbcommon: ERROR: failed to add default include path /usr/share/X11/xkb ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390144,name=PContent::Msg_AsyncMessage) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x390143,name=PContent::Msg_CommitBrowsingContextTransaction) Channel error: cannot send/recv ###!!! [Parent][MessageChannel] Error: (msgtype=0x39008C,name=PContent::Msg_FlushTabState) Channel error: cannot send/recv [Parent 6310, IPC I/O Parent] WARNING: FileDescriptorSet destroyed with unconsumed descriptors: file /build/firefox/parts/firefox/build/ipc/chromium/src/chrome/common/file_descriptor_set_posix.cc:19 After that, I logged under x11 (for test) but wasn't able to launch firefox: Error: cannot open display: :0 I had to reboot and the problem occurs only with wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1946599/+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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume
** Tags added: suspend-resume -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1951667 Title: [SRU] pulseaudio: restore hdmi audio be active output after resume Status in HWE Next: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Focal: In Progress Status in pulseaudio source package in Hirsute: In Progress Status in pulseaudio source package in Impish: In Progress Status in pulseaudio source package in Jammy: In Progress Bug description: [Impact] On the machines with legacy HDA audio driver, when users plug a hdmi/dp monitor, the active output device is still speaker, need users to manually select the hdmi, then the hdmi audio will be the users' preference, once it is plugged, it should become the active output automatically. But with the current PA, after reboot and suspend/resume, the hdmi can't change to be active output automatically anymore. [Fix] Backport an upstream fix, this will fix the issue of "preferred ports being cleaned by a mistake" [Test] On a machine with legacy HDA audio driver, install the patched pulseaudio, then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi audio to be active, with the hdmi monitor plugged and reboot, suspend and resume, check what is the active output, it is still the hdmi audio. [Where problems could occur] This patch is in the card-restore.c, if it could introduce regression, it will be on the default active input/output devices, for example, users select a input or output device to be active, after reboot, if those devices are available, they should be active, but they could be replaced by other devices if a regression is introduced. But this possibility is very low since we tested the patch on a couple of desktop and laptop machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951667/+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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Changed in: hplip (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: hplip (Ubuntu Focal) Importance: Undecided => Low ** Changed in: hplip (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: hplip (Ubuntu Impish) Importance: Undecided => Low ** Changed in: hplip (Ubuntu Jammy) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+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 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
** Also affects: ubiquity (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => High -- 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/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: New Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" [Test Plan] * Install Ubuntu on machine with "third-party packages" enabled * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Execute "prime-select query" should get "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Changed in: mutter (Ubuntu Hirsute) Importance: Undecided => High -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Hirsute: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plymouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start (
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Changed in: fedora Importance: Unknown => Undecided ** Changed in: fedora Status: Unknown => New ** Changed in: fedora Remote watch: Red Hat Bugzilla #1985251 => None ** Package changed: fedora => ubuntu-translations ** No longer affects: ubuntu-translations ** Bug watch removed: Red Hat Bugzilla #1985251 https://bugzilla.redhat.com/show_bug.cgi?id=1985251 ** Project changed: hplip => ubuntu-translations ** No longer affects: ubuntu-translations -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Package changed: mutter (Fedora) => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: Red Hat Bugzilla #1516859 => None ** No longer affects: ubuntu ** Bug watch removed: Red Hat Bugzilla #1516859 https://bugzilla.redhat.com/show_bug.cgi?id=1516859 ** Project changed: xorg-server => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 => None ** No longer affects: ubuntu ** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help
[Desktop-packages] [Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
** Changed in: pulseaudio (Ubuntu Impish) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Impish: Fix Committed Bug description: * Impact The pulseaudio service sometime segfaults on session closing which trigger a bug report dialog * Test plan Log out of a desktop session and back in, there should be no error prompt The issue isn't triggered only randomly it seems so it might be easier to check that reports stop on https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e * Where problems could occur The change is in the X session closing handling so shouldn't impact on normal use, if incorrect the fix could lead to increase the chance of hitting the segfault when an Xsession is closed --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1942685/+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 1916250] Re: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy)
** Changed in: libsignon-glib (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: libsignon-glib (Ubuntu Impish) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsignon-glib in Ubuntu. https://bugs.launchpad.net/bugs/1916250 Title: gir1.2-signon-2.0 needs to declare replace on older releases (Groovy2Hirsute and Focal2Jammy) Status in libsignon-glib package in Ubuntu: Fix Released Status in libsignon-glib source package in Hirsute: Fix Committed Status in libsignon-glib source package in Impish: Fix Committed Bug description: gir1.2-signon-1.0 from groovy gir1.2-signon-2.0 from hirsute above two packages ship the same file /usr/lib/python3/dist- packages/gi/overrides/Signon.py without specifying how to resolve the conflict. [Test Case] This can be simply tested with a focal schroot: 1) apt-get install vim libsignon-glib-dev 2) edit /etc/apt/sources.list replacing focal with hirsute 3) apt-get update 4) apt-get install libsignon-glib-dev With the version of libsignon-glib-dev from -proposed you'll no longer receive the 'dpkg: error' from below. Unpacking gir1.2-signon-2.0:amd64 (2.1-3) ... dpkg: error processing archive /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/gi/overrides/Signon.py', which is also in package gir1.2-signon-1.0 1.14+17.04.20161117-0ubuntu5 Errors were encountered while processing: /var/cache/apt/archives/gir1.2-signon-2.0_2.1-3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Probably needs a conflicts/replaces dependency added to the newer hirsute package. [Regression Potential] We are adding a replaces with gir1.2-signon-1.0 so anything that depends on that package would be broken but given that that package is no longer available after focal that seems fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsignon-glib/+bug/1916250/+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 1946499] Re: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all
** Project changed: ubuntu-mate => ubuntu-translations ** No longer affects: ubuntu-translations ** No longer affects: vte2.91 (Ubuntu) ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all Status in gdebi package in Ubuntu: Fix Released Status in gdebi source package in Impish: Fix Committed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1946499/+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 1948566] Re: Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main)
** Changed in: java-atk-wrapper (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/1948566 Title: Sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main) Status in java-atk-wrapper package in Ubuntu: New Bug description: Please sync java-atk-wrapper 0.38.0-5 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * No-change rebuild to build packages with zstd compression. * No-change rebuild to build packages with zstd compression. * Import an unreleased debian patch to better address the s390x FTBFS - debian/patches/werror * Import an unreleased debian patch to better address the s390x FTBFS - debian/patches/werror Werror patch has been included in Debian package. Changelog entries since current jammy version 0.38.0-2ubuntu3: java-atk-wrapper (0.38.0-5) unstable; urgency=medium [ Debian Janitor ] * Bump debhelper from old 12 to 13. * Update standards version to 4.5.1, no changes needed. * Remove constraints unnecessary since buster: + Build-Depends: Drop versioned constraint on java-common. [ Samuel Thibault ] * libatk-wrapper-java.lintian-overrides: Drop lintian warning for jar name. -- Samuel Thibault Sat, 18 Sep 2021 18:34:13 +0200 java-atk-wrapper (0.38.0-4) unstable; urgency=medium * patches/dbus: Also detect at-spi through dbus. -- Samuel Thibault Thu, 26 Aug 2021 02:50:17 +0200 java-atk-wrapper (0.38.0-3) unstable; urgency=medium * patches/werror: Only enable -Werror in upstream development (Closes: Bug#984069). * control: Set Rules-Requires-Root to no. * rules: Drop ddeb-migration rules, now useless -- Samuel Thibault Sun, 15 Aug 2021 22:56:34 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1948566/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => Low -- 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/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Confirmed Status in gnome-shell-extension-desktop-icons source package in Focal: Confirmed Status in nautilus source package in Focal: Fix Committed Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1948008] Re: Copying and pasting to/from Nautilus does not work
*** This bug is a duplicate of bug 1843588 *** https://bugs.launchpad.net/bugs/1843588 ** No longer affects: gnome-shell-extension-desktop-icons (Ubuntu Impish) ** This bug has been marked a duplicate of bug 1843588 Nautilus doesn't copy filenames for paste to other programs anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1948008 Title: Copying and pasting to/from Nautilus does not work Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Status in gnome-shell-extension-desktop-icons source package in Hirsute: Won't Fix Bug description: [Impact] * After upstream Nautilus has reverted the following commit [1] related to upstream bug [2] the desktop icons extension lost it's ability to copy to/from nautilus. * This is related to the fact that before there was some metadata passed along in the clipboard along with text data. This was causing issues with compatibility with some applications that were not expecting any metadata (MIME type in this case) was glued to the text clipboard contents. Hence, it was reverted upstream [3]. * Fixing the root cause of this issue required changes to Nautilus [3], gnome-shell [4] and desktop-icons [5] [6]. Nautilus and gnome- shell parts are already implemented and present in Hirsute and Impish. [Test Plan] 1) Make sure desktop-icons extension is enabled. 2) Open nautilus window and copy any file from there by right-clicking and selecting "Copy" from the popup menu. 3) Right-click on desktop and select "Paste" from the context menu. Expected result: selected file is copied to the desktop. Actual result: "Paste" item is disabled in the menu. [Where problems could occur] * Mixing a version of nautilus without commit [3] and fixed version of desktop-icons may still lead to a scenario when copying will not work. * Any extension/application copying to desktop using the smuggled-in- text clipboard behavior should be expected to stop working. [Other Info] [1] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/289 [2] https://gitlab.gnome.org/GNOME/nautilus/-/issues/634 [3] https://gitlab.gnome.org/GNOME/nautilus/-/merge_requests/573 [4] https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1321 [5] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [6] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1948008/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Changed in: oem-priority
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1929371
Title:
[SRU] there is always a "Rear Microphone - Built-in Audio" option on
the input device list even if the microphone is unplugged
Status in OEM Priority Project:
Fix Released
Status in alsa-ucm-conf package in Ubuntu:
Fix Released
Status in pulseaudio package in Ubuntu:
Fix Released
Status in alsa-ucm-conf source package in Focal:
Fix Released
Status in pulseaudio source package in Focal:
Fix Released
Status in alsa-ucm-conf source package in Hirsute:
Fix Released
Status in pulseaudio source package in Hirsute:
Fix Released
Bug description:
[Impact]
In Lenovo P520, which using a codec for front panel, the other codec for rear
panel and both are on a same card.
In this case, the rear Mic will present on input devices of "Sound
Settings" even if attaching nothing to rear mic jack.
[Fix]
For alsa-ucm-conf part, the Mic 2 should use "Rear Mic Jack" as JackControl
because of
```
control.18 {
iface CARD
name 'Rear Mic Jack'
value true
comment {
access read
type BOOLEAN
count 1
}
}
```
After applying "Rear Mic Jack", the rear Mic will not always there anymore
but it's not there as well if hot-plugging audio device on rear mic. Thus, it
needs to change pulseaudio to handle if all devices are off cases.
For pulseaudio, if there is no any audio devices attached, then
attaching an input device on rear mic jack. The port will not be
selected automatically because the profiles is off. It needs patch
pulseaudio to check off profiles (for dual codec case).
[Test]
After applying these patches, the rear mic jack works good in all cases (boot
without mic and then attach mic, boot with mic and then hotplug it) and other
functions (line-in / line-out) work pretty well.
[Where problems could occur]
This change only apply the bonus on below cases:
```
if ((has_input_port && found_available_input_port && !has_output_port) ||
(has_output_port && found_available_output_port && !has_input_port) ||
(has_input_port && found_available_input_port && has_output_port &&
found_available_output_port))
```
and these cases have been tested.
If there are some complex codec design then it might cause problem but so far
we didn't see that.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
** Changed in: nvidia-prime (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install 20.04.3 with "Third-party packages". After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946434/+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 1927100] Re: Slow file dialogs, open and save
** Changed in: gvfs (Ubuntu) Importance: Undecided => Low ** Also affects: gvfs (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gvfs (Ubuntu Focal) Importance: Undecided => Low ** Changed in: gvfs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1927100 Title: Slow file dialogs, open and save Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Focal: New Bug description: On Ubuntu Mate 20.04. Sometime the Open and Save dialogs in GTK applications will over 20 seconds to display. I found https://gitlab.gnome.org/GNOME/gvfs/-/issues/485 , which suggested this due to gvfsd-trash, and running `killall gvfsd-trash` which does temporary solve the problem. The issue is apparently fixed in gvfs 1.46.2 Please could 1.46.2 or the fix https://gitlab.gnome.org/GNOME/gvfs/-/merge_requests/96 be backported to Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1927100/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
** Tags removed: patch ** Bug watch removed: GNOME Bug Tracker #320128 https://gitlab.gnome.org/320128 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1756238/+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 1946499] Re: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file des
** Changed in: gdebi (Ubuntu Impish) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1946499 Title: installation of deb-packages with gdebi-gtk shows "dpkg: error: unable to read filedescriptor flags for : Bad file descriptor" in gdebi terminal, package is not installed Status in Ubuntu MATE: Invalid Status in gdebi package in Ubuntu: Fix Committed Status in vte2.91 package in Ubuntu: Confirmed Status in gdebi source package in Impish: Triaged Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.10 2. Open Firefox, navigate to discord.com 3. Download deb-file. At time of writing from the https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link 4. Open Caja in ~/Downloads folder and use GDebi to install the discord-0.0.16.deb file 5. In the GDebi window click Install button Expected results: * Gdebi quietly install discord package, there are no error messages in its terminal Actual results: * Gdebi terminal shows the error in the last line ``` Selecting previously unselected package gconf2-common. (Reading database ... 457178 files and directories currently installed.) Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ... Unpacking gconf2-common (3.2.6-7ubuntu2) ... Selecting previously unselected package libgconf-2-4:amd64. Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ... Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service-backend. Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service-backend (3.2.6-7ubuntu2) ... Selecting previously unselected package gconf-service. Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ... Unpacking gconf-service (3.2.6-7ubuntu2) ... Selecting previously unselected package libappindicator1. Preparing to unpack .../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ... Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Selecting previously unselected package libunwind-13:amd64. Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ... Unpacking libunwind-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++abi1-13:amd64. Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1-13:amd64. Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ... Unpacking libc++1-13:amd64 (1:13.0.0-2) ... Selecting previously unselected package libc++1:amd64. Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ... Unpacking libc++1:amd64 (1:13.0-53~exp1) ... Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ... Setting up gconf2-common (3.2.6-7ubuntu2) ... Creating config file /etc/gconf/2/path with new version Setting up libunwind-13:amd64 (1:13.0.0-2) ... Setting up libc++abi1-13:amd64 (1:13.0.0-2) ... Setting up libc++1-13:amd64 (1:13.0.0-2) ... Setting up libc++1:amd64 (1:13.0-53~exp1) ... Setting up gconf-service (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... Processing triggers for sgml-base (1.30) ... Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ... Setting up gconf-service-backend (3.2.6-7ubuntu2) ... Processing triggers for libc-bin (2.34-0ubuntu2) ... dpkg: error: unable to read filedescriptor flags for : Bad file descriptor ``` and as the result Discord package is not installed . ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdebi 0.9.5.7+nmu5ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Oct 8 18:17:36 2021 InstallationDate: Installed on 2021-10-08 (0 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1946499/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
I think it makes more sense to use bug 1946499 to track the issue happening in Ubuntu 21.10. The patches in this bug landed two years ago, so it would be confusing to reopen it. ** No longer affects: gdebi (Ubuntu) ** Tags removed: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte2.91/+bug/1756238/+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 1946440] Re: SRU: enable RTD3 only on laptops
** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High -- 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/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: New Bug description: [Impact] * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Installed Nvidia GPU driver * On laptop with Nvidia RTD3 supported GPU. Execute 'sudo gpu-manager', /run/nvidia_runtimepm_supported will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. But based on Nvidia READ, such case should not happen [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+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 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
** Changed in: vte2.91 (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1756238 Title: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags Status in gdebi package in Ubuntu: Fix Committed Status in vte2.91 package in Ubuntu: Fix Released Status in vte2.91 source package in Bionic: Fix Released Bug description: When using gdebi-gtk to install a .deb the install fails with the message:- dpkg: error: unable to read filedescriptor flags for : Bad file descriptor This only occurs via the gdebi-gtk GUI front end, packages install perfectly if done via the CLI with: sudo gdebi /path/to/packagename.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1756238/+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 1946143] Re: Apply upstream patches to display 5G NSA status
** Changed in: libqmi (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libqmi in Ubuntu. https://bugs.launchpad.net/bugs/1946143 Title: Apply upstream patches to display 5G NSA status Status in OEM Priority Project: New Status in libqmi package in Ubuntu: New Bug description: [Impact] The 5G NSA status can not be displayed in the libqmi version 1.28.6-1. (LP#1937012) The 5G NSA status is supported in the libqmi version 1.30.2. The requested upstream patches are listed as below: * 5G NSA status patches https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/29905223c5ae6e5e4ef9246dd9dd4d01b2819d9a * qmicli,nas: flag as 'n/a' the 5G NSA signal quality if not connected https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/commit/b05df7b658f9cfb4c5e74a3e07913de689914a8f [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Verify if the field “5G NSA Available: ” can be displayed via executing: $ sudo qmicli --device=/dev/wwan0p2MBIM --device-open-proxy --nas-get-system-info ... 5G NSA Available: 'no' ... [Where problems could occur] The requested upstream patches are for displaying the status information of 5G NSA network. This should not affect existing generic functions. [Other Info] The latest version of libqmi suit can display the 5G NSA status. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946143/+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 1946096] Re: Apply upstream patches to fix problems for Foxconn and Quectel modems.
** Changed in: modemmanager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1946096 Title: Apply upstream patches to fix problems for Foxconn and Quectel modems. Status in OEM Priority Project: New Status in modemmanager package in Ubuntu: New Bug description: [Impact] The following 2 modems need the ModemManager v1.16.6 suite to be patched from v1.18.2 to fix some problems(LP#1943774, LP#1943780): * Foxconn SDX55 T99W175 5G sub6 PCIE Modem * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem The requested upstream patches are listed as below: * for Quectel EM160 4G ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2 * for Foxconn T99W175 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9 **https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371 ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a ** https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154 [Test Plan] 1. Install the Ubuntu image. 2. Boot and login the system. 3. Prepare the modem’s firmware and install the firmware upgrading application provided by Foxconn and Quectel 4. Using the firmware upgrading application to upgrade the modem’s firmware 5. Verify if the modem’s firmware upgrading is successful 6. Reboot 7. Verify if the upgraded modem firmware is still working [Where problems could occur] The requested upstream patches are for these 2 specific modems and the status information. This should not affect existing generic functions and other modems. [Other Info] The firmware and the upgrading application can be downloaded from the following link: * LP#1943774 for Quectel modems * LP#1943780 for Foxconn modems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946096/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Tags removed: lubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is a Spac
[Desktop-packages] [Bug 1930188] Re: Acer Aspire 5 sound driver issues
** Also affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** No longer affects: linux (Ubuntu Hirsute) ** No longer affects: linux (Ubuntu Impish) ** No longer affects: pulseaudio (Ubuntu Focal) ** No longer affects: pulseaudio (Ubuntu Hirsute) ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Fix Released ** Changed in: linux (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: pulseaudio (Ubuntu Focal) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Hirsute) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: pulseaudio (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Hui Wang (hui.wang) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1930188 Title: Acer Aspire 5 sound driver issues Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: New Status in linux source package in Focal: Fix Released Status in pulseaudio source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: New Status in linux source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: In Progress Bug description: SRU Justification for alsa-ucm-conf: [Impact] On the machines with the sof audio driver, users could adjust the input volume from UI, but this only adjusts the "Capture Volume", the "Mic Boost" can't be changed, if "Mic Boost" is 0, even we adjust the "Capture Volume" to max, the recorded volume is still very low. [Fix] Backport a upstream patch, the patch adds the "Mic Boost" into the ucm [Test] plug a headset, make sure the headset-mic is the active input device, adjust the input volume to %20, open a terminal and run alsamixer, check the "Capture Volume" and "Mic Boost" value, then adjust the input volume to 80%, check those values and we could see both values are changed. [Where problems could occur] This patch could make the parse of input volume control fail, then the input volume can't be changed anymore when users adjust the volume from UI. But this possibility is very low, I tested this patch on many lenovo and dell machines with sof audio driver, all worked well. SRU Justification for pulseaudio: [Impact] On the machines with the sof audio driver, after booting up, the active output device is speaker by default, we adjust the output volume to 100%, then we plug a headphone, and adjust the output volume from 100% to 20%, now in theory, the speaker's volume is 100%, the headphone's volume is 20%. We plugout the headphone, the active output device becomes speaker and we expect the volume changes to 100%, but the output volume for speaker is 20%. [Fix] Backport a upstream patch, this patch is already in the pulseaudio-15.0, so impish already has this fix. Only hirsute and focal need to backport this patch. [Test] adjust speaker's volume to 80%, then plug headphone and adjust headphone's volume to 20%, unplug the headphone, the speaker's volume becomes to 80%, plug the headphone, the headphone's volume becomes to 20%. [Where problems could occur] The patch writes the output volume to hardware immediately when switching output device on the machines with sof audio driver, this could introduce pop noise when changing the output device, but this possibility is very low, I tested the patch on many lenovo and dell machines with sof audio driver, all worked as expected and have no pop noise when switching output device. The patch was merged to ubuntu 5.13.0 and 5.11.0 generic kernels with stable update already, but it is not merged to ubuntu 5.4.0 kernel yet, so I se
[Desktop-packages] [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
** Also affects: graphite2 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994757 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to graphite2 in Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package Status in graphite2 package in Ubuntu: New Status in graphite2 package in Debian: Unknown Bug description: There is no libgraphite2.a file, so it is not possible to compile statically against this library. See attached patch to solve this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+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 1943859] Re: The development package does not include static libraries
** Also affects: pango1.0 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994752 Importance: Unknown Status: Unknown ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1943859 Title: The development package does not include static libraries Status in pango1.0 package in Ubuntu: New Status in pango1.0 package in Debian: Unknown Bug description: The development package for pango (libpango1.0-dev) does not include static libraries so it is not possible to link these libraries statically. See attached patch with the fix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+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 1940504] Re: Support Alder Lake P graphics
** No longer affects: linux-oem-5.14 (Ubuntu)
** Changed in: linux-firmware (Ubuntu)
Status: Invalid => Fix Released
--
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/1940504
Title:
Support Alder Lake P graphics
Status in libdrm package in Ubuntu:
Fix Released
Status in linux-firmware package in Ubuntu:
Fix Released
Status in mesa package in Ubuntu:
Fix Released
Status in libdrm source package in Focal:
Fix Committed
Status in linux-firmware source package in Focal:
In Progress
Status in linux-oem-5.14 source package in Focal:
New
Status in mesa source package in Focal:
Fix Committed
Bug description:
[SRU Justification:linux-firmware]
[Impact]
It shows the firmware is missing, and runtime power management has been
disabled:
i915 :00:02.0: [drm] Failed to load DMC firmware
i915/adlp_dmc_ver2_10.bin. Disabling runtime power management.
[Fix]
Upstream commit 3d32f216 ("i915: Add ADL-P DMC Support").
[Test Case]
Verified on Intel ADL-M/ADL-P RVPs.
[Where problems could occur]
It's a new firmware for new GPU, not possible to introduce
regressions.
[Other Info]
Impish has this already. And while ADL-P/M support begins since v5.14,
only focal (for oem-5.14) is being nominated.
=
[SRU Justification:mesa,libdrm]
NOTE: this is for focal only, hirsute/impish do not and will not have
kernel support for this.
[Impact]
ADL-P machines need to use the native driver.
[Fix]
Backport support from upstream.
libdrm: a single patch from 2.4.107
mesa: three commits to add pci-id's and a workaround
kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports
[Test case]
Boot a machine and check that it's using the native driver and that the usual
workloads are fine.
[Where things could go wrong]
For older gpu's there's little to go wrong, since the commits are for ADL-P
only.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+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 1898005] Re: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:2
gnome-shell (3.36.9-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #1921963): - Improve login screen accessibility - Prefer image-data hint over app-icon in notifications - Plugged leak - Fixed crashes * debian/patches: - Correctly handle login cancellation and failures (LP: #1915066) - Show errors on fingerprint failures and limit retries (LP: #1865838) - gdm: Don't try to retry authenticating when the service is unavailable (LP: #1915570) - Enable to use Escape to cancel auth requests (with limits) (LP: #1921929) -- Marco Trevisan (Treviño) Wed, 31 Mar 2021 00:50:16 +0200 ** Changed in: gnome-shell (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898005 Title: gnome-shell crashed with SIGABRT in st_bin_destroy: assertion failed: (priv->child == NULL) called from DesktopManager::_destroyDesktopIcons() [desktopManager.js:234] Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell source package in Focal: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell source package in Hirsute: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Gnome Shell crashes at random times when the Desktop or home directory is modified, and the desktop-icons extension tries to refresh. https://errors.ubuntu.com/problem/fcc5c581fc0a8c2f8f68314fa383690423a3dc02 [Test Case] Open a nautilus (Files) window and tap Ctrl+H repeatedly. The shell should not crash or freeze. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading, like this bug. [Other Info] See also bug 1898910 --- Sorry, I missed what was happening when this crashed. I'll try to catch it next time. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4 Uname: Linux 5.8.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 30 08:38:45 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_CA.UTF-8 LANGUAGE=en_CA:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/gnome-shell/libst-1.0.so g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898005/+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 1942764] Re: Enable riscv64 build of mesa-opencl-icd
** Changed in: mesa (Ubuntu) Importance: Undecided => Medium -- 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/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: In Progress Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+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 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+s
[Desktop-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Changed in: wpa (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Fix Committed
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Tags removed: patch-forwarded-upstream
** Tags added: patch-accepted-upstream
** Changed in: hundredpapercuts
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Fix Released
Status in wpa package in Ubuntu:
Triaged
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1917362] Re: PAM: smartcard owner isn't associated to user by default
** Changed in: sssd (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1917362 Title: PAM: smartcard owner isn't associated to user by default Status in sssd: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in sssd package in Ubuntu: Fix Released Status in gdm3 source package in Hirsute: Fix Committed Status in sssd source package in Hirsute: Triaged Bug description: [ Impact ] Smartcard user is not selected automatically when inserting a smartcard [ Test case ] Insert a smartcard that has an user associated to it: -> gdm is expected to select the user associated to it and start the authentication requesting the card PIN, without having to explicitly write the username. [ Regression potential ] PAM configuration for smartcard changed the order [1] we check the services, so: - if a /var/run/nologin the user will be denied for accessing the system only after that the PIN has been inserted. - root may be an allowed user, if associated to a smartcard (even though we trust SSSD PAM module and configuration explicitly disallows it). [1] https://salsa.debian.org/gnome- team/gdm/-/compare/90e71bd4...d32be2e5 --- There's a SSSD side of this fix (for the carts with multiple certificates) that is part of 2.4.1 and should be handled by https://github.com/SSSD/sssd/pull/5401/ (+ commit https://github.com/SSSD/sssd/commit/4ea1739d09b) GDM should instead handle empty users properly both in the PAM config and sending the info back to gnome-shell. To manage notifications about this bug go to: https://bugs.launchpad.net/sssd/+bug/1917362/+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 1912168] Re: Merge ppp 2.4.9
** Summary changed: - please merge ppp 2.4.9 for 21.04 and then consider ipv6 default fix for SRU + Merge ppp 2.4.9 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1912168 Title: Merge ppp 2.4.9 Status in ppp package in Ubuntu: Triaged Bug description: Hi, due to this ML on devel-discuss [1] I realized that there is a new version that should be merged for Ubuntu 21.04 - and probably later [2] be considered/discussed for an SRU That new version is in Debian now [3] and I think it would be great to get that merged/synced. I guess ppp might be out-of-focus today, therefore per [4] I'm also pinging the Desktop team hoping this will help to get a look at it. [1]: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2021-January/018916.html [2]: https://github.com/paulusmack/ppp/pull/145/commits/0678d3bf69116af58b00fbc64bd4185acb4d5c37 [3]: https://tracker.debian.org/news/1217613/ppp-249-11-migrated-to-testing/ [4]: http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1912168/+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 1934787] Re: Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main)
** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1934787 Title: Sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main) Status in network-manager-openvpn package in Ubuntu: New Bug description: Please sync network-manager-openvpn 1.8.14-1 (main) from Debian experimental (main) *NOTE: this release properly support tls-crypt-v2 certifcates, which current Ubuntu version fail to import!* Explanation of the Ubuntu delta and why it can be dropped: * Cherry-pick two upstream commits (that were released with 1.8.14) to fix connecting to some OpenVPN providers when using openvpn >= 2.5.0 (LP: #1922423) - debian/patches/upstream-56bb08f.patch - debian/patches/upstream-353a521.patch These changes are cherry picked from 1.8.14, so they are already included in Debian 1.8.14-1. Changelog entries since current impish version 1.8.12-2ubuntu1: network-manager-openvpn (1.8.14-1) experimental; urgency=medium * New upstream version 1.8.14 * Fix capitalization error in package description -- Michael Biebl Tue, 30 Mar 2021 15:13:23 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1934787/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
** No longer affects: gnome-shell-extension-desktop-icons-ng (Ubuntu Focal) ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Impish) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1875015] Re: Ubuntu 20.04 and Displaylink is extremely slow
** Changed in: xorg-server (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu Impish) Importance: Undecided => Medium ** Tags removed: 20.04 displaylink docking station ubuntu -- 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/1875015 Title: Ubuntu 20.04 and Displaylink is extremely slow Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: In Progress Status in xorg-server source package in Hirsute: In Progress Status in xorg-server source package in Impish: Fix Committed Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1875015/+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 1926771] Re: [SRU] Hard dependency on desktop-file-utils not declared
** Changed in: wslu (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: wslu (Ubuntu Impish) Importance: Undecided => Medium ** Tags added: unmetdeps -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1926771 Title: [SRU] Hard dependency on desktop-file-utils not declared Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Focal: New Status in wslu source package in Impish: Fix Released Bug description: [Impact] This bug will cause installation issues once LP #1911432 SRU Process complete. [Test Case] * checkout the ubuntu/master branch on wslu GitHub or launchpad repository; * Run the autopktest with command "autopkgtest path/to/folder -- null" in Ubuntu 20.04 on WSL1 and WSL2. * View the result of the test, it should be passed with 7 Windows Explorer open and 3 webpage open on the default browser. [Regression Potential] The potential regressions would be a result of badly generated ~/.config/wslu/, or a badly merged package. [Original Bug Report] Context: Manual upgrade (via updating sources.list, not do-release-upgrade) of Windows Store version of Ubuntu 20.04 to 20.10 failed. Expected: wslu declares all required dependencies as mandatory dependencies (Depends:). Actual: wslu's post-installation script requires desktop-file-utils, but wslu declares desktop-file-utils as a recommended dependency (Recommends:). Attempting to install wslu 3.2.1-0ubuntu1.1 without desktop-file-utils installed results in the following error: E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up wslu (3.2.1-0ubuntu1.1) ... /var/lib/dpkg/info/wslu.postinst: 13: desktop-file-install: not found dpkg: error processing package wslu (--configure): installed wslu package post-installation script subprocess returned error exit status 127 dpkg: dependency problems prevent configuration of ubuntu-wsl: ubuntu-wsl depends on wslu; however: Package wslu is not configured yet. $ lsb_release -rd Description:Ubuntu 20.10 Release:20.10 $ apt-cache policy wslu wslu: Installed: 3.2.1-0ubuntu1.1 Candidate: 3.2.1-0ubuntu1.1 Version table: *** 3.2.1-0ubuntu1.1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.2.1-0ubuntu1 500 500 https://atl.mirrors.clouvider.net/ubuntu groovy/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1926771/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT
** Tags removed: verification-needed -- 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/1934783 Title: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] The new upstream version 21.0.3 has a regression on radeonsi (amdgpu), which shows as graphical corruption on the desktop apps with certain hardware. The fix is to add a commit from upstream staging/21.0 -branch, which never got released as 21.0.4. [Test case] Install the update, use desktop apps, see that it works correctly now. [Where things could go wrong] The fix adds a single line for an earlier commit that was incomplete. In theory it might regress some other amd hw, but this is highly unlikely. -- Since the update to Mesa 21.0.3 I have graphical glitches in desktop: Unity, Gnome Shell both sessions (X.org and Wayland). Also most of the programs have glitches. However Firefox seems unaffected. CPU: Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz min/max: 2200/3600 MHz Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] driver: amdgpu v: kernel Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0 5.4.0-79-generic LLVM 12.0.0) v: 4.6 Mesa 21.0.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Merge proposal unlinked:
https://code.launchpad.net/~os369510/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/403448
** Project changed: plainbox-provider-checkbox => ubuntu-translations
** No longer affects: ubuntu-translations
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
In Progress
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/issues #1358 https://gitlab.freedesktop.org/mesa/mesa/issues/1358 ** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #4275 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 -- 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/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #2859
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
** Changed in: mesa (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: mesa (Ubuntu Hirsute)
Importance: Undecided => Medium
--
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/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
Patch sent upstream:
https://patchwork.ozlabs.org/project/hostap/patch/20210525031333.7665-1-mathew.hod...@gmail.com/
** Tags added: patch-forwarded-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Triaged
Status in wpa package in Ubuntu:
Triaged
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+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 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
** Tags removed: verification-needed -- 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/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in enigmail package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in enigmail source package in Bionic: Fix Committed Status in jsunit source package in Bionic: Fix Committed Status in thunderbird source package in Bionic: Fix Committed Status in enigmail source package in Focal: Fix Released Status in jsunit source package in Focal: Fix Released Status in thunderbird source package in Focal: Fix Released Status in tinyjsd source package in Focal: Fix Released Status in thunderbird source package in Groovy: Fix Released Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1895643/+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 1929371] Re: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged
** Changed in: alsa-ucm-conf (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Also affects: pulseaudio (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: alsa-ucm-conf (Ubuntu Focal) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Focal) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Groovy) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1929371 Title: [SRU] there is always a "Rear Microphone - Built-in Audio" option on the input device list even if the microphone is unplugged Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Status in alsa-ucm-conf source package in Focal: New Status in pulseaudio source package in Focal: New Status in alsa-ucm-conf source package in Groovy: New Status in pulseaudio source package in Groovy: New Status in alsa-ucm-conf source package in Hirsute: Fix Released Status in pulseaudio source package in Hirsute: New Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1929371/+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 1911379] Re: [SRU] Avoid error message when the file doesn't exist
** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] Avoid error message when the file doesn't exist Status in wslu package in Ubuntu: Fix Released Status in wslu source package in Groovy: Fix Released Status in wslu source package in Hirsute: Fix Released Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+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 885086] Re: XDG "Desktop" item not translated on Live CD
** Bug watch removed: gitlab.xfce.org/xfce/thunar/-/issues #537 https://gitlab.xfce.org/xfce/thunar/-/issues/537 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-user-dirs in Ubuntu. https://bugs.launchpad.net/bugs/885086 Title: XDG "Desktop" item not translated on Live CD Status in Ubuntu Translations: Triaged Status in casper package in Ubuntu: In Progress Status in xdg-user-dirs package in Ubuntu: Opinion Bug description: When I switch the language on my Oneiric Live CD, other XDG directories are translated except the "Desktop" item. When I have a look inside ~/.config/user-dirs.dirs, the string is untranslated (other strings in the file are translated all right). If I run xdg- user-dirs-update, ~/.config/user-dirs.dirs is updated to the correct translation. So I suppose that the default Live CD user is created by some not-localized hackish solution. If this seems not so important, since installed systems have the "Desktop" directory translated all right (at least I hope so, because my system has), it certainly affects all Ubuntu localized Live-CDs and makes them fail the basic "translated or not surface check". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/885086/+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 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min Status in gdm3 package in Ubuntu: Won't Fix Bug description: UBUNTU 19.10 installed on ThunderX2 saber ARM64 machine. If the system left idle for ~22min it becomes unresponsive. The system will not take any inputs like from UART, ping ..etc. The system will completely freeze and we need to hard reset the system. It could be possible the system goes to hibernate state and could not able to come out of the state. Dmesg log when system halts/no response on Saber boards (TX2) Ubuntu 19.10 ubuntu ttyAMA0 ubuntu login: ubuntu Password: Last login: Wed Jan 29 20:08:22 PST 2020 on ttyAMA0 Welcome to Ubuntu 19.10 (GNU/Linux 5.3.0-26-generic aarch64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage ubuntu@ubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan [ +0.732512] audit: type=1400 audit(1580358920.412:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=3087 comm="apparmor_parser" [ +0.64] audit: type=1400 audit(1580358920.412:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=3091 comm="apparmor_parser" [ +0.000168] audit: type=1400 audit(1580358920.412:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=3086 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=3086 comm="apparmor_parser" [ +0.000546] audit: type=1400 audit(1580358920.412:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=3085 comm="apparmor_parser" [ +0.06] audit: type=1400 audit(1580358920.412:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=3085 comm="apparmor_parser" [ +0.05] audit: type=1400 audit(1580358920.412:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=3085 comm="apparmor_parser" [ +0.000854] audit: type=1400 audit(1580358920.412:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=3089 comm="apparmor_parser" [ +0.002667] audit: type=1400 audit(1580358920.416:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=3093 comm="apparmor_parser" [ +0.04] audit: type=1400 audit(1580358920.416:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=3093 comm="apparmor_parser" [ +1.382579] igb :92:00.1 enp146s0f1: igb: enp146s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX [ +0.000299] IPv6: ADDRCONF(NETDEV_CHANGE): enp146s0f1: link becomes ready [ +3.131173] mpt3sas_cm0: port enable: SUCCESS [Jan29 20:36] random: crng init done [ +0.04] random: 7 urandom warning(s) missed due to ratelimiting *[Jan29 20:37] rfkill: input handler disabled* *[Jan29 20:57] PM: suspend entry (deep)* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #2859 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 ** Changed in: mesa Remote watch: gitlab.freedesktop.org/mesa/mesa/-/issues #3468 => gitlab.freedesktop.org/mesa/mesa/-/issues #2859 ** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #4275 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 -- 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/1918855 Title: Xorg xserver got signal 6 to abort Status in Mesa: Unknown Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1918855/+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 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-terminal/-/issues #253 https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 ** Also affects: gnome-terminal via https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/303 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in GNOME Terminal: Unknown Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-terminal/+bug/1922839/+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 1717257] Re: [bug / patch ]patch for glibc 2.26 to avoid errors in compiling with CUDA(NVCC)
** No longer affects: llvm-toolchain-3.8 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to llvm-toolchain-3.8 in Ubuntu. https://bugs.launchpad.net/bugs/1717257 Title: [bug / patch ]patch for glibc 2.26 to avoid errors in compiling with CUDA(NVCC) Status in gcc-7 package in Ubuntu: Fix Released Status in glibc package in Ubuntu: Fix Released Bug description: DistroRelease: Ubuntu 17.10 (Proposed) Package: glibc 2.26-0ubuntu1 Architecture: amd64 extrapackage (not incl. in UBUNTU) NVIDIA-DRIVER, CUDA --- Here is another proposal regarding bug report I posted (but in reject). https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1716816 I reported that glibc 2.26-0ubuntu1 ( adopted in Artful-proposed on Sep 5.) causes compilation error by using NVIDIA's CUDA8.0 and 9.0RC. Under glibc 2.24, they work. It maybe comes from glibc226's new feature, i.e. "128-bit floating point as defined by ISO/IEC/IEEE 60559:2011 (IEEE 754-2008) and ISO/IEC TS 18661-3:2015" . (Evidence Scripted at bottom) I proposed the patch to /usr/include/x86_64-linux-gnu/bits/floatn.h which lets NVCC (CUDA's compiler) avoid __float128 (NVCC does support neither 8.0 nor 9.0). So can the patch be merged to glibc2.25 be adopted in Arful or later? - *** floatn.h-dist 2017-09-04 16:34:21.0 +0900 --- floatn.h 2017-09-14 21:46:15.334033614 +0900 *** *** 28,34 support, for x86_64 and x86. */ #if (defined __x86_64__ \ ? __GNUC_PREREQ (4, 3) \ ! : (defined __GNU__ ? __GNUC_PREREQ (4, 5) : __GNUC_PREREQ (4, 4))) # define __HAVE_FLOAT128 1 #else # define __HAVE_FLOAT128 0 --- 28,35 support, for x86_64 and x86. */ #if (defined __x86_64__ \ ? __GNUC_PREREQ (4, 3) \ ! : (defined __GNU__ ? __GNUC_PREREQ (4, 5) : __GNUC_PREREQ (4, 4))) \ ! && !defined(__CUDACC__) # define __HAVE_FLOAT128 1 #else # define __HAVE_FLOAT128 0 - (evidence) -- 1. Here is part of message during compiing Tensorflow with CUDA on UBUNTU17.10 beta with proposed-components. . -- typedef _Complex float __cfloat128 __attribute__ ((__mode__ (__TC__))); ^ INFO: From Compiling external/nccl_archive/src/broadcast.cu.cc: /usr/include/x86_64-linux-gnu/bits/floatn.h(61): error: invalid argument to attribute "__mode__" /usr/include/x86_64-linux-gnu/bits/floatn.h(73): error: identifier "__float128" is undefined -- 2. Forums in INVIDIA where issues the problems around glibc.2.26 NVIDIA https://devtalk.nvidia.com/default/topic/1023776/cuda-programming-and-performance/-request-add-nvcc-compatibility-with-glibc-2-26/ 3. THis bug has already discussed in Arch linux and the patch (tas same ) proposed https://www.reddit.com/r/archlinux/comments/6zrmn1/torch_on_arch/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1717257/+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 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions
** Bug watch added: bugzilla.gnome.org/ #745032 https://bugzilla.gnome.org/show_bug.cgi?id=745032 ** Changed in: mutter Importance: Medium => Unknown ** Changed in: mutter Status: Confirmed => Unknown ** Changed in: mutter Remote watch: GNOME Bug Tracker #745032 => bugzilla.gnome.org/ #745032 ** Bug watch removed: GNOME Bug Tracker #745032 https://gitlab.gnome.org/745032 -- 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/1690719 Title: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland). It's not reliably smooth like you would see in Xorg or Mir demo servers. Feels like there is a blocking call being made in a GUI thread that shouldn't have any blocking calls. Although it's not clear if this is just a problem with pointer input or the shell compositing in general. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 Date: Mon May 15 13:23:22 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1690719/+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 1916469] Re: Apps don't use Wayland by default
** No longer affects: vlc (Ubuntu) -- 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/1916469 Title: Apps don't use Wayland by default Status in firefox package in Ubuntu: Fix Released Status in qdirstat package in Ubuntu: Confirmed Status in telegram-desktop package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Fix Committed Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1916469/+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 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
** Changed in: gnome-terminal (Ubuntu Hirsute) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+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 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
** Also affects: xfwm4 via https://bugzilla.xfce.org/show_bug.cgi?id=16716 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in xf86-video-amd: Unknown Status in Xfwm4: Unknown Status in xfwm4 package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Triaged Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Triaged Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Triaged Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET32W (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NECTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefin
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
** No longer affects: libxcb (Ubuntu) ** No longer affects: libxcb (Ubuntu Focal) ** No longer affects: libxcb (Ubuntu Groovy) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => Triaged ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal) Status: Incomplete => Triaged ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy) Status: Incomplete => Triaged ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Focal) Importance: Undecided => High ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Groovy) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in xf86-video-amd: Unknown Status in xfwm4 package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Triaged Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Triaged Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Triaged Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users _MarkForUpload: True dmi.bios.date: 12/23/2019 dmi.bios.vendor: LENOVO dmi.b
[Desktop-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths
xfwm4 (4.14.2-1) unstable; urgency=medium * Team upload. [ Debian Janitor ] * Trim trailing whitespace. * Bump debhelper from old 11 to 12. * Set upstream metadata fields: Name (from ./configure), Repository. * Fix day-of-week for changelog entry 4.0.0.final-1. [ Mateusz Łukasik ] * d/watch: Update to working version. * New upstream version 4.14.1 - Fix raise delay (Closes: #940796) * d/control: update standards version to 4.5.0 [ Unit 193 ] * New upstream version 4.14.2. - Fix window title alignment (Closes: #953112) * d/control: R³: no. -- Unit 193 Sun, 03 May 2020 08:29:52 -0400 ** Changed in: xfwm4 (Ubuntu) Status: Confirmed => Fix Released ** Tags added: regression-release ** Changed in: xfwm4 (Ubuntu Focal) Importance: Undecided => High ** Changed in: xfwm4 (Ubuntu Groovy) Importance: Undecided => High ** Project changed: linux => xf86-video-amd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1873895 Title: Regression: block staircase display with side-by-side monitors of different pixel widths Status in xf86-video-amd: Unknown Status in libxcb package in Ubuntu: Incomplete Status in xfwm4 package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Status in libxcb source package in Focal: Incomplete Status in xfwm4 source package in Focal: In Progress Status in xserver-xorg-video-amdgpu source package in Focal: Incomplete Status in libxcb source package in Groovy: Incomplete Status in xfwm4 source package in Groovy: Fix Released Status in xserver-xorg-video-amdgpu source package in Groovy: Incomplete Bug description: [Impact] * This issue affects AMD graphics on Xfwm4 4.14.1. * Windows are displayed staggered with a multi-window layout [Test Plan] * Use AMD graphics drivers * Connect a second display at a different resolution * Open multiple windows * While the issue is present, the windows and desktop will appeared staggered * Once fixed, they display normally. [Where problems could occur] * Regression potential should be relatively low, as the release between 4.14.1 and 4.14.5 are bug releases. * With window managers, some changes could lead to different behavior and other broken displays. Non-AMD graphics users should also test for regressions. [Other Info] * Please see the Xfwm4 release notes for changes between 4.14.1 and 4.14.5: https://gitlab.xfce.org/xfce/xfwm4/-/blob/xfce-4.14/NEWS#L7-44 [Original Report] Update based on further research. This only happens when the secondary external display is operating at a different pixel width to the internal. In this case eDP is 1920x1080 whereas the external HDMI-A-0 is natively 1680x1050. It is caused by xfwm4's recent switch from using glx to xpresent for AMD GPUs. The underlying bug is in the AMD driver. I was able to reproduce on an external 1920x1200 display only when it was set to a non-native 1680x1050 resolution. --- Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred initially on the laptop that is having package upgrades applied regularly. With dual monitors and the external monitor placed left or right the display has a blocked staircase effect shown in the attached photograph, and seems related to https://gitlab.freedesktop.org/xorg/driver/xf86-video- amdgpu/-/issues/10 More detailed investigation suggests it only happens when the X coordinate of the two monitors is different. The symptom looks like an off-by-one error because it appears as if the display is divided into, say, 10 rows and 15 columns but the first row has 16 'columns' worth of blocks on it and so wraps to the beginning of the 2nd row, and so on. On the laptop without package upgrades being applied this didn't happen. So I upgraded it (314 packages) and restarted and it too sees the same problem. I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but that didn't solve it. I now suspect libxcb but so far haven't been able to prove it. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2020-04-08 (11 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408) MachineType: LENOVO 20NECTO1WW Package: xserver-xorg-video-amdgpu 19.1.0-1 PackageArchitecture: amd64 ProcK
[Desktop-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
** Also affects: bluez (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986836 Importance: Unknown Status: Unknown -- 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/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: In Progress Status in bluez package in Debian: Unknown Bug description: In the case of upgrading or installing bluez for the first time on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+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 1869059] Re: Button 2 of my ThinkPad X1 Yoga's stylus is not detected
** Changed in: libwacom (Ubuntu) Importance: Low => Medium ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1869059 Title: Button 2 of my ThinkPad X1 Yoga's stylus is not detected Status in OEM Priority Project: New Status in libwacom package in Ubuntu: New Bug description: This also happened on Eoan, but I never had the chance to report the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwacom2 1.1-2build3 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Mar 25 13:12:20 2020 DistUpgraded: 2020-03-21 19:59:50,804 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8324, 5.3.0-42-generic, x86_64: installed backport-iwlwifi, 8324, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics [17aa:2292] InstallationDate: Installed on 2020-01-19 (66 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20SA0002US ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=8644acd5-759a-4daa-a34c-75ad3f4c5c12 ro quiet splash vt.handoff=7 SourcePackage: libwacom UpgradeStatus: Upgraded to focal on 2020-03-21 (3 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1869059/+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
