[Desktop-packages] [Bug 2015671] Re: no spinning Ubuntu / Kubuntu logo on startup
[Expired for plymouth (Ubuntu) because there has been no activity for 60 days.] ** Changed in: plymouth (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to plymouth in Ubuntu. https://bugs.launchpad.net/bugs/2015671 Title: no spinning Ubuntu / Kubuntu logo on startup Status in plymouth package in Ubuntu: Expired Bug description: no spinning Ubuntu logo on startup on the latest kernel (6.2.0-19-generic) update ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: plymouth-theme-spinner 22.02.122-3ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 9 16:27:11 2023 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-06-25 (1017 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-19-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/kubuntu-text/kubuntu-text.plymouth UpgradeStatus: Upgraded to lunar on 2022-09-30 (190 days ago) dmi.bios.date: 02/10/2023 dmi.bios.release: 1.22 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.0:bd02/10/2023:br1.22:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2015671/+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 2023927] Re: Screen flickering whe update images
Comment #7 shows the wrong driver in use - it's using software rendering on the CPU instead of using the GPU. I cannot figure out why yet, but generally recommend you use long term support release 22.04 instead: https://ubuntu.com/download/desktop ** Changed in: linux-hwe-5.13 (Ubuntu) Status: Incomplete => New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Screen flickering whe update images + [focal] Screen flickering in Xorg on i7-1165G7 -- 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/2023927 Title: [focal] Screen flickering in Xorg on i7-1165G7 Status in linux-hwe-5.13 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Often, when there are small changes in image displayed, an horizontal flickering is observed. This happen for example on a mouse right button menu, or when a hyperlink description appears on the screen bottom when mouse pointer cross some field on a webpage, also when favorites menu appear. The flickering usually disappear in a few moments, sometimes (usually when a few pixels are updating) it can last for seconds. This flickering is caused by a late updating of some horizontal lines, so for awhile a few lines of previous image coexist with a majority of new ones ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-41.46~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 14 22:44:12 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.32, 5.13.0-40-generic, x86_64: installed virtualbox, 6.1.32, 5.13.0-41-generic, x86_64: installed virtualbox, 6.1.32, 5.4.0-126-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e39:a025] InstallationDate: Installed on 2022-01-01 (529 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Error: command ['lsusb'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 127: lsusb: symbol lookup error: lsusb: undefined symbol: libusb_error_name MachineType: MEDION S15449 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-41-generic root=UUID=cbfc0023-baf3-4a11-b0aa-6dadbd0f60f7 ro quiet splash pci=noaer vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 212 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr212:bd04/09/2021:br5.19:svnMEDION:pnS15449:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:skuML-23000830031014: dmi.product.family: Akoya dmi.product.name: S15449 dmi.product.sku: ML-230008 30031014 dmi.product.version: Default string dmi.sys.vendor: MEDION version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/2023927/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Based on the suggestion in #14, update the changelog to make the update
more clearly for the use
[ Jeremy Szu ]
* README, README.md,
UbuntuDrivers/detect.py,
tests/test_ubuntu_drivers.py:
- Let OEM image can locally extending the NVIDIA driver
supported PCI IDs for cutting edge silicons by specifying
related information in /etc/custom_supported_gpus.json file.
(lp: #1990341)
- Support autopkgtest for force install Nvidia and update
related section in README.
** Patch added: "force_install_NVIDIA_driver-jammy_3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5680578/+files/force_install_NVIDIA_driver-jammy_3.debdiff
** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
Status: Incomplete => In Progress
--
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/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
In Progress
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2024333] [NEW] Received empty error dialog after applying Nvidia driver
*** This bug is a duplicate of bug 2008489 *** https://bugs.launchpad.net/bugs/2008489 Public bug reported: I tried to apply a newer Nvidia driver via the Additional Drivers tab, but an empty error dialog appeared as the progress bar reached the end. It didn't give me any details about the failure. From /var/log/syslog: 2023-06-18T21:39:38.059182-04:00 logan-Ubuntu-XPS software-proper[4062]: Failed to set text 'Error while applying changes#012#012pk-client-error-quark: The following packages have unmet dependencies:#012 nvidia-driver-530: Depends: nvidia-kernel- common-530 (<= 530.41.03-1) but it is not installable#012 Depends: nvidia-kernel-common-530 (>= 530.41.03) but it is not installable#012 linux-modules-nvidia-530-6.2.0-23-generic: Depends: nvidia-kernel-common-530 (>= 530.41.03) but it is not installable#012 linux-modules-nvidia-530-generic: Depends: nvidia-kernel-common-530 (>= 530.41.03) but it is not installable#012 (268)' from markup due to error parsing markup: Error on line 4 char 59: “=” is not a valid character following a “<” character; it may not begin an element name ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: software-properties-gtk 0.99.35 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 18 21:39:48 2023 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-02-14 (1220 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to lunar on 2023-06-19 (0 days ago) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screenshot from 2023-06-18 21-43-06.png" https://bugs.launchpad.net/bugs/2024333/+attachment/5680573/+files/Screenshot%20from%202023-06-18%2021-43-06.png ** Description changed: I tried to apply a newer Nvidia driver via the Additional Drivers tab, but an empty error dialog appeared as the progress bar reached the end. It didn't give me any details about the failure. + + From /var/log/syslog: + + 2023-06-18T21:39:38.059182-04:00 logan-Ubuntu-XPS software-proper[4062]: + Failed to set text 'Error while applying + changes#012#012pk-client-error-quark: The following packages + have unmet dependencies:#012 nvidia-driver-530: Depends: nvidia-kernel- + common-530 (<= 530.41.03-1) but it is not installable#012 + Depends: nvidia-kernel-common-530 (>= 530.41.03) but it is not + installable#012 linux-modules-nvidia-530-6.2.0-23-generic: Depends: + nvidia-kernel-common-530 (>= 530.41.03) but it is not installable#012 + linux-modules-nvidia-530-generic: Depends: nvidia-kernel-common-530 (>= + 530.41.03) but it is not installable#012 (268)' from markup due to error + parsing markup: Error on line 4 char 59: “=” is not a valid character + following a “<” character; it may not begin an element name ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: software-properties-gtk 0.99.35 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jun 18 21:39:48 2023 ExecutablePath: /usr/bin/software-properties-gtk InstallationDate: Installed on 2020-02-14 (1220 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InterpreterPath: /usr/bin/python3.11 PackageArchitecture: all ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, user) - SHELL=/usr/bin/fish - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, user) + SHELL=/usr/bin/fish + XDG_RUNTIME_DIR= Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A SourcePackage: software-properties UpgradeStatus: Upgraded to lunar on 2023-06-19 (0 days ago) ** This bug has been marked a duplicate of bug 2008489 Unable to switch NVIDIA driver -- cryptic "OK" window pops up -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2024333 Title: Received empty error dialog after applying Nvidia driver Status in software-properties package in Ubuntu: New Bug description: I tried to apply a newer Nvidia driver via the Additional Drivers tab, but an empty error dialog appeared as the progress bar reached the end. It didn't give me any details about the failure. From /var/log/syslog:
[Desktop-packages] [Bug 2024303] Re: No LibreOffice Still PPA release for Ubuntu 23.04 Lunar
Ubuntu 23.04 ship with LibreOffice 7.5.x by default which is at this point the stable Fresh version. While LibreOffice Still currently refers to 7.4.x series it would mean to provide a downgrade to an older version. This is not the intention of the available PPAs. ** Tags added: ppa ** Changed in: libreoffice (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2024303 Title: No LibreOffice Still PPA release for Ubuntu 23.04 Lunar Status in libreoffice package in Ubuntu: Won't Fix Bug description: There's a Fresh PPA proposed release for 23.04 but no Still. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2024303/+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 1971242] Autopkgtest regression report (cups/2.4.1op1-1ubuntu4.3)
All autopkgtests for the newly accepted cups (2.4.1op1-1ubuntu4.3) for jammy
have finished running.
The following regressions have been reported in tests triggered by the package:
pappl/1.0.3-2 (arm64)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/jammy/update_excuses.html#cups
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
Status in CUPS:
Fix Released
Status in atril package in Ubuntu:
Confirmed
Status in cups package in Ubuntu:
Fix Committed
Status in okular package in Ubuntu:
Confirmed
Status in cups source package in Jammy:
Fix Committed
Bug description:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers
are affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
PDF_Printer-PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Chcke whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints
about color printing. So the regression potential is very low.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid
I am affected by this bug for a Xerox B230, I'd the printer is shut off and restart. Deleting the certificate fixes it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1973441 Title: Printing does not work on Ubuntu 22.04 - cups-pki-invalid Status in cups package in Ubuntu: Confirmed Bug description: After upgrading to 22.04 printing did not work. There is cups-pki- invalid error and printer goes to paused state. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cups 2.4.1op1-1ubuntu4 Uname: Linux 5.17.7-051707-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log' CurrentDesktop: ubuntu:GNOME Date: Sun May 15 15:34:47 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2021-10-12 (214 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) Lpstat: device for HP_Color_LaserJet_M552_5F80BF: implicitclass://HP_Color_LaserJet_M552_5F80BF/ MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago) dmi.bios.date: 03/29/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.318 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.81 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1929851] Re: GSmartControl & NVME drive
https://github.com/storaged-project/udisks/issues/1121 ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** No longer affects: udisks2 (Ubuntu) ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/storaged-project/udisks/issues #1121 https://github.com/storaged-project/udisks/issues/1121 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1929851 Title: GSmartControl & NVME drive Status in gsmartcontrol package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: New Bug description: Ubuntu 18.04.5 (Linux Mint 19.3) gsmartcontrol 1.1.3-1, amd64 I see that GSmartControl cannot work with NVME (SSD disk) correctly. I test with WD SN550 - 1TB, blue NVME drive. Problem: gsmartcontrol list my drive as /dev/nvme0n1. That is OK, but there is parent drive (/dev/nvme0) and that is not listed. /dev/nvme0 has some important information related to SMART, including value of TBW. Other issue is that gsmartcontrol cannot identify NVME disk, it list it as "Unknown model". I dump here output from GSmartControl and after that dump from tool smartctl. === ## gsmartcontrol (detail of /dev/nvme0n1 - 'Unknown model') smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-32-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC WDS100T2B0C-00PXH0 Serial Number: 2052FQSECRET Firmware Version: 211070WD PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 1 000 204 886 016 [1,00 TB] Unallocated NVM Capacity: 0 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1 000 204 886 016 [1,00 TB] Namespace 1 Formatted LBA Size: 512 Local Time is: Thu May 27 18:31:08 2021 CEST Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL *Other* Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat *Other* Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.90W -0 0 0 00 0 1 + 2.70W1.80W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0200W --3 3 3 3 3900 11000 4 - 0.0050W --4 4 4 4 5000 39000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 2 1 -4096 0 1 === START OF SMART DATA SECTION === Read NVMe SMART/Health Information failed: NVMe Status 0x4002 === $ sudo smartctl -a /dev/nvme0 smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-32-generic] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: WDC WDS100T2B0C-00PXH0 Serial Number: 2052FQSECRET Firmware Version: 211070WD PCI Vendor/Subsystem ID:0x15b7 IEEE OUI Identifier:0x001b44 Total NVM Capacity: 1 000 204 886 016 [1,00 TB] Unallocated NVM Capacity: 0 Controller ID: 1 Number of Namespaces: 1 Namespace 1 Size/Capacity: 1 000 204 886 016 [1,00 TB] Namespace 1 Formatted LBA Size: 512 Local Time is: Thu May 27 18:33:33 2021 CEST Firmware Updates (0x14):2 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL *Other* Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat *Other* Maximum Data Transfer Size: 128 Pages Warning Comp. Temp. Threshold: 80 Celsius Critical Comp. Temp. Threshold: 85 Celsius Namespace 1 Features (0x02):NA_Fields Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 3.50W2.90W -0 0 0 00 0 1 + 2.70W1.80W -0 0 0 00 0 2 + 1.90W1.50W -0 0 0 00 0 3 - 0.0200W --3 3 3 3 3900 11000 4
[Desktop-packages] [Bug 2024310] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/2024310/+attachment/5680505/+files/xserver.devices.txt ** Package changed: ubuntu => xserver-xorg-video-ati (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/2024310 Title: After upgrading to Lunar Lobster X server is no longer using radeon driver (bad performance) Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: After upgrading from Kinetic Kudu to Lunar Lobster, I've noticed a very sluggish performance in games. glxgears show almost 15x FPS reduction. Really at a loss what my be the issue, but there are few odd things in Xorg.log below. Some additional information 1. lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 2. apt-cache policy xserver-xorg-video-radeon xserver-xorg-video-radeon: Installed: 1:19.1.0-3 Candidate: 1:19.1.0-3 Version table: *** 1:19.1.0-3 500 500 http://gb.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status 3. lspci -nn | grep VGA 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c3) 4. inxi -GSC -xx System: Host: MINIPC-PN50 Kernel: 6.2.0-23-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.1 tk: GTK v: 3.24.37 wm: gnome-shell dm: GDM3 Distro: Ubuntu 23.04 (Lunar Lobster) CPU: Info: 6-core model: AMD Ryzen 5 4500U with Radeon Graphics bits: 64 type: MCP arch: Zen 2 rev: 1 cache: L1: 384 KiB L2: 3 MiB L3: 8 MiB Speed (MHz): avg: 1398 high: 1400 min/max: 1400/2375 boost: disabled cores: 1: 1397 2: 1397 3: 1397 4: 1400 5: 1400 6: 1400 bogomips: 28448 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm Graphics: Device-1: AMD Renoir vendor: ASUSTeK driver: N/A arch: GCN-5 pcie: speed: 16 GT/s lanes: 16 bus-ID: 04:00.0 chip-ID: 1002:1636 Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.8 compositor: gnome-shell driver: X: loaded: vesa unloaded: fbdev,modesetting,radeon dri: swrast gpu: N/A display-ID: :1 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 Monitor-1: default res: 1920x1080 size: N/A API: OpenGL v: 4.5 Mesa 23.0.2 renderer: llvmpipe (LLVM 15.0.7 256 bits) direct-render: Yes 5. sudo egrep -i 'amd|radeon|\(EE\)|\(WW\)' /var/log/Xorg.0.log (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [20.470] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [20.470] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist. [20.470] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist. [20.471] (WW) The directory "/usr/share/fonts/X11/100dpi" does not exist. [20.471] (WW) The directory "/usr/share/fonts/X11/75dpi" does not exist. [20.571] (II) LoadModule: "radeon" [20.571] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so [20.576] (II) Module radeon: vendor="X.Org Foundation" [20.578] (II) RADEON: Driver for ATI/AMD Radeon chipsets: ATI Radeon Mobility X600 (M24), ATI FireMV 2400, ATI Radeon Mobility X300 (M24), ATI FireGL M24 GL, ATI Radeon X600 (RV380), ATI FireGL V3200 (RV380), ATI Radeon IGP320 (A3), ATI Radeon IGP330/340/350 (A4), ATI Radeon 9500, ATI Radeon 9600TX, ATI FireGL Z1, ATI Radeon 9800SE, ATI Radeon 9800, ATI FireGL X2, ATI Radeon 9600, ATI Radeon 9600SE, ATI Radeon 9600XT, ATI FireGL T2, ATI Radeon 9650, ATI FireGL RV360, ATI Radeon 7000 IGP (A4+), ATI Radeon 8500 AIW, ATI Radeon IGP320M (U1), ATI Radeon IGP330M/340M/350M (U2), ATI Radeon Mobility 7000 IGP, ATI Radeon 9000/PRO, ATI Radeon 9000, ATI Radeon X800 (R420), ATI Radeon X800PRO (R420), ATI Radeon X800SE (R420), ATI FireGL X3 (R420), ATI Radeon Mobility 9800 (M18), ATI Radeon X800 SE (R420), ATI Radeon X800XT (R420), ATI Radeon X800 VE (R420), ATI Radeon X850 (R480), ATI Radeon X850 XT (R480), ATI Radeon X850 SE (R480), ATI Radeon X850 PRO (R480), ATI Radeon X850 XT PE (R480), ATI Radeon Mobility M7, ATI Mobility FireGL 7800 M7, ATI Radeon Mobility M6, ATI FireGL Mobility 9000 (M9), ATI Radeon Mobility 9000 (M9), ATI Radeon 9700 Pro, ATI Radeon 9700/9500Pro, ATI FireGL X1, ATI Radeon 9800PRO, ATI Radeon 9800XT, ATI Radeon Mobility 9600/9700 (M10/M11), ATI Radeon Mobility 9600 (M10), ATI Radeon Mobility 9600 (M11), ATI Radeon, ATI FireGL 8700/8800, ATI Radeon 8500, ATI Radeon 9100, ATI Radeon 7500, ATI Radeon VE/7000, ATI ES1000, ATI Radeon Mobility X300 (M22), ATI Radeon Mobility X600 SE (M24C),
[Desktop-packages] [Bug 2022851] Re: Nautilus displays invalid directory content after deleting
I think control for selecting files in list mode is not fixed with latest updates. Maybe still not in main repository? I have Nautillus 1:44.0-1ubuntu2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2022851 Title: Nautilus displays invalid directory content after deleting Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Released Status in gtk4 source package in Lunar: Fix Released Bug description: Impact -- When files are deleted in Nautilus, they can still show up but in the wrong order. This can also happen if the files are rearranged. This bug is marked Critical because it happen with gtk4 4.10.3+ds-0ubuntu1 in lunar-updates but not with 4.10.1+ds-2ubuntu1 which was originally released with Lunar. Test Case - Install the gtk4 update 1. Close the file browser windows if they are open 2. From a terminal, run these commands: mkdir delete-test cd delete-test touch a b c d e f 3. Open the Nautilus file browser window 4. Navigate to the delete-test folder 5. Select the f file and press the Delete key to delete the file. The file should be deleted and you should see only the files a b c d e in the current folder view What Could Go Wrong --- This fix is included in gtk4 4.10.4 update so see the master bug LP: #2023031 Original Bug Report --- When I delete or reorganize files, they can be displayed wrong. After going to another directory and then back, everything displays properly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.0-1ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 4 18:25:47 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'initial-size' b'(725, 456)' InstallationDate: Installed on 2022-07-22 (317 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2022851/+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 1537113] Re: Please, add apt logs
** Changed in: gnome-system-log (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-log in Ubuntu. https://bugs.launchpad.net/bugs/1537113 Title: Please, add apt logs Status in gnome-system-log package in Ubuntu: Triaged Status in gnome-system-log package in Debian: Fix Released Bug description: Please, add some of the logs at "/var/log/apt/*" to the GNOME System Logs application, as these are of great usefulness for reverting installations. Otherwise the user cannot tell which dependencies are not longer useful. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: gnome-system-log 3.9.90-4 ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6 Uname: Linux 4.2.0-25-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Jan 22 16:48:49 2016 InstallationDate: Installed on 2015-11-14 (69 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: gnome-system-log UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-log/+bug/1537113/+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 1829364] Re: Will not play sound via HDMI using 48000 Hz sample rate
I tried this by 20.04, but could not get sound via HDMI cable work, except once, even if I had sample rate 44100 set in daemon.conf. I wonder what is wrong. TV tells: "unknown audio signal, check the source." -- 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/1829364 Title: Will not play sound via HDMI using 48000 Hz sample rate Status in pulseaudio package in Ubuntu: Confirmed Bug description: Does not play sound when playing file that has 48000 Hz sample rate via sink output:iec958-stereo. This is when using proprietary nvidia-340 driver; when using nouveau driver, HDMI is not even recognized (Bug #1844129). Note that the device (HP 8510w, having NVIDIA Quadro FX 570M graphics adapter) does not have real HDMI audio, but audio is somehow wired from motherboard's S/PDIF to HDMI explaining the sink name. Anyway, in the attached AlsaInfo.txt there is a device "Node 0x02 [Audio Output] wcaps 0x30311: Stereo Digital" that has "rates [0x60]: 44100 48000". Workaround: Set alternate-sample-rate = 44100 in /etc/pulse/daemon.conf and restart pulseaudio ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jarnos 1283 F pulseaudio CurrentDesktop: XFCE Date: Thu May 16 12:39:15 2019 InstallationDate: Installed on 2019-05-08 (7 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68MVD Ver. F.20 dmi.board.name: 30C5 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.36 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68MVDVer.F.20:bd12/01/2011:svnHewlett-Packard:pn:pvrF.20:rvnHewlett-Packard:rn30C5:rvrKBCVersion71.36:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829364/+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 1951685] Re: Chromium flatpak reliably crashes xdg-desktop-portal
Hi, the problem occurs again with Flatpak 1.14.4: UngoogledChromium refuses to load any content after a short period of time. Installed browser version: com.github.Eloston.UngoogledChromium 114.0.5735.106 OS: Ubuntu 20.04.6 LTS (Focal Fossa) Desktop: Gnome 3.36.9 Best regards Michael -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1951685 Title: Chromium flatpak reliably crashes xdg-desktop-portal Status in xdg-desktop-portal package in Ubuntu: New Bug description: For a while now I am facing the issue that Chromium installed via Flatpak after a minute or so stops working with a puzzling error ERR_NO_SUPPORTED_PROXIES. I guess this is due to the Proxy feature of the desktop portal because now I noticed that the portal is actually crashing shortly after I started Chromium and/or started browsing. According to the stack trace this happens in get_one_app_state so I think this bug was fixed in version 1.7.0 with this patch: https://github.com/flatpak/xdg-desktop- portal/commit/a0b641f1230016e8ed9a291c70d4dd226429dda4 Could that fix please be backported to 1.6.0/focal? PID: 15467 (xdg-desktop-por) UID: 1000 (xxx) GID: 1000 (xxx) Signal: 11 (SEGV) Timestamp: Sat 2021-11-20 16:55:00 CET (4min 23s ago) Command Line: /usr/libexec/xdg-desktop-portal Executable: /usr/libexec/xdg-desktop-portal Control Group: /user.slice/user-1000.slice/user@1000.service/xdg-desktop-portal.service Unit: user@1000.service User Unit: xdg-desktop-portal.service Slice: user-1000.slice Owner UID: 1000 (xxx) Boot ID: 1841d625a5354885a778e18a20b48103 Machine ID: 30e0f491ec7847428bc900251dc271af Hostname: xxx Storage: /var/lib/systemd/coredump/core.xdg-desktop-por.1000.1841d625a5354885a778e18a20b48103.15467.1637423700.lz4 Message: Process 15467 (xdg-desktop-por) of user 1000 dumped core. Stack trace of thread 15505: #0 0x7f5990c485f4 g_str_hash (libglib-2.0.so.0 + 0x405f4) #1 0x7f5990c4773c g_hash_table_lookup (libglib-2.0.so.0 + 0x3f73c) #2 0x5646137cf282 get_one_app_state (xdg-desktop-portal + 0x30282) #3 0x5646137cf778 background_monitor (xdg-desktop-portal + 0x30778) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15470: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f5990c5a4f1 n/a (libglib-2.0.so.0 + 0x524f1) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15475: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a4a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7f598e5f099d n/a (libdconfsettings.so + 0xa99d) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5 0x7f5990bee609 start_thread (libpthread.so.0 + 0x9609) #6 0x7f5990b15293 __clone (libc.so.6 + 0x122293) Stack trace of thread 15467: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x5646137bb7e8 main (xdg-desktop-portal + 0x1c7e8) #4 0x7f5990a1a0b3 __libc_start_main (libc.so.6 + 0x270b3) #5 0x5646137bb94e _start (xdg-desktop-portal + 0x1c94e) Stack trace of thread 15471: #0 0x7f5990b08aff __GI___poll (libc.so.6 + 0x115aff) #1 0x7f5990c5a36e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7f5990c5a6f3 g_main_loop_run (libglib-2.0.so.0 + 0x526f3) #3 0x7f5990eaff8a n/a (libgio-2.0.so.0 + 0x11ef8a) #4 0x7f5990c83ad1 n/a (libglib-2.0.so.0 + 0x7bad1) #5
