[Desktop-packages] [Bug 2055804] [NEW] Choosing font
Public bug reported: Hello, I want to choosing best fonts from my collection in easy way. ~/.fonts$ find . -type f |wc -l 11196 I have +1 fonts, Arabic & English. I can not comparing between fonts . More than 50% of Arabic fonts are not working (some of them were worked in 7.10). There is not grouping or sorting by language , (I can see some sorting in Open Office Writer - character ...) Some system & applications hanging if I add all of them (8g ram + swap 16g) I can not grouping them or selecting some of them to viewing & others to hide in easy way !. I can not know wich of them are working & wich are not working to removing or fixing !. Some Applications access to .fonts & change some of files (FireFox or other?) , I know that by rsync files. I can not view 0 as number , Not as O or o. Some fonts can not displayed as before. I can not found package deb to install all necessary package for Arabic fonts & English & Viewing 0. Almost I use TrueType fonts were working in WindowsXP. I need help. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sun Mar 3 09:49:16 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7850] InstallationDate: Installed on 2023-08-21 (194 days ago) InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) MachineType: MSI MS-7850 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=31f7c266-8d08-49d3-9846-5083e162dc40 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:br4.6:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy kubuntu third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2055804 Title: Choosing font Status in xorg package in Ubuntu: New Bug description: Hello, I want to choosing best fonts from my collection in easy way. ~/.fonts$ find . -type f |wc -l 11196 I have +1 fonts, Arabic & English. I can not comparing between fonts . More than 50% of Arabic fonts are not working (some of them were worked in 7.10). There is not grouping or sorting by language , (I can see some sorting in Open Office Writer - character ...) Some system & applications hanging if I add all of them (8g ram + swap 16g) I can not grouping them or selecting some of them to viewing & others to hide in easy way !. I can not know wich of them are working & wich are not working to removing or fixing !. Some Applications access to .fonts & change some of files (FireFox or other?) , I know that by rsync files. I can not view 0 as number , Not as O or o. Some fonts can not displayed as before. I can not found package deb to install all necessary package for Arabic fonts & English & Viewing 0. Almost I use TrueType fonts were working in WindowsXP. I need help. Thank you ProblemType: Bug DistroRelease: Ubuntu 22.04 Package:
[Desktop-packages] [Bug 2045977] Re: GNOME Shell crash with Wayland
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/2045977 Title: GNOME Shell crash with Wayland Status in gnome-shell package in Ubuntu: Expired Bug description: My GNOME session got idle and crashed. In the journalctl logs there is more details ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 8 10:43:43 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-26 (742 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-08-18 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2045977/+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 2046553] Re: i am unable to pair and connect bluetooth
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/2046553 Title: i am unable to pair and connect bluetooth Status in bluez package in Ubuntu: Expired Bug description: sudo apt-get install fwupd sudo fwupdmgr update Reading package lists... Done Building dependency tree... Done Reading state information... Done fwupd is already the newest version (1.7.9-1~22.04.3). fwupd set to manually installed. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Devices with no available firmware updates i have configered also but no problem found Type: Primary Bus: USB BD Address: 34:41:5D:32:F1:53 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:19216 acl:0 sco:0 events:2629 errors:0 TX bytes:603774 acl:0 sco:0 commands:2570 errors:0 please fix this ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 15 18:29:38 2023 InstallationDate: Installed on 2023-08-31 (106 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:58ca Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 002: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4GHz Wireless rechargeable vertical mouse [More] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic root=UUID=3e546dec-b6ab-4cff-9ae6-19d09ccec9e4 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2023 dmi.bios.release: 1.33 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.33.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.33.0:bd07/06/2023:br1.33:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:sku081C: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2046553/+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 2046189] Re: Xorg freezes on external displays when in Gnome Shell on Nvidia graphics
[Expired for xorg-server (Ubuntu) because there has been no activity for
60 days.]
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/2046189
Title:
Xorg freezes on external displays when in Gnome Shell on Nvidia
graphics
Status in xorg-server package in Ubuntu:
Expired
Bug description:
When using external displays, they randomly freeze, but the internal
display works just fine. Windows remain interactive, but frozen, on
external displays, and the cursor disappears.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Dec 11 15:14:50 2023
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a60] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD
Graphics] [1462:1305]
NVIDIA Corporation GA106M [GeForce RTX 3060 Mobile / Max-Q] [10de:2520] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] GA106M [GeForce RTX
3060 Mobile / Max-Q] [1462:1305]
InstallationDate: Installed on 2022-06-28 (531 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64
(20220419)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic
root=UUID=70390c05-b447-4e39-b596-a9f9eb4ac62b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/15/2021
dmi.bios.release: 1.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: E17K3IMS.11B
dmi.board.asset.tag: Default string
dmi.board.name: MS-17K3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17K3IMS.11B:bd09/15/2021:br1.27:svnMicro-StarInternationalCo.,Ltd.:pnGE76Raider11UE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17K3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17K3.1:
dmi.product.family: GE
dmi.product.name: GE76 Raider 11UE
dmi.product.sku: 17K3.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu4
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2046189/+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 2055779] Re: software and updates not opening
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2055779 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Project changed: ubuntu-desktop-installer => software-properties (Ubuntu) ** Changed in: software-properties (Ubuntu) Status: New => Incomplete -- 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/2055779 Title: software and updates not opening Status in software-properties package in Ubuntu: Incomplete Bug description: Since recent updates trying to access software sources or additional drivers gets no response. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055779/+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 2055779] [NEW] software and updates not opening
You have been subscribed to a public bug: Since recent updates trying to access software sources or additional drivers gets no response. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- software and updates not opening https://bugs.launchpad.net/bugs/2055779 You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. -- 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 2055793] [NEW] Wine program crashes with unhandled page fault on startup
Public bug reported: Today, APT Performed the following update: Start-Date: 2024-03-02 16:23:10 Commandline: aptdaemon role='role-commit-packages' sender=':1.304' Upgrade: tcpdump:amd64 (4.99.1-3ubuntu0.1, 4.99.1-3ubuntu0.2), libglx-mesa0:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libglx-mesa0:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgbm1:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgbm1:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), firmware-sof-signed:amd64 (2.0-1ubuntu4.4, 2.0-1ubuntu4.5), gigolo:amd64 (0.5.2-1, 0.5.2-1ubuntu0.22.04.1), mesa-va-drivers:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgl1-mesa-dri:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libgl1-mesa-dri:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libosmesa6:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libosmesa6:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), mesa-vulkan-drivers:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), mesa-vulkan-drivers:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libglapi-mesa:am d64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libglapi-mesa:i386 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), libegl-mesa0:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2), mesa-vdpau-drivers:amd64 (23.0.4-0ubuntu1~22.04.1, 23.2.1-1ubuntu3.1~22.04.2) This update causes a problem when running a program via wine (6.0.3~repack-1) which I have run (under wine) for over 10 years. Dialog box error message: A program on your system has crashed, but WineDbg was unable to attach to the process to obtain a backtrace. [ OK ] Terminal error message: wine: Unhandled page fault on read access to at address (thread 0024), starting debugger... Can't attach process 0020: error 5 I reverted by installing the following packages: 8c1d0584ae15da9fa9006798e396280825cbc19b043c9fea34c605d05d10544a libegl-mesa0_23.0.4-0ubuntu1~22.04.1_amd64.deb 33da608ad1dd71ae0e181cc7d29425a3e76d3bc3d595644a4e424ce0065600a1 libgbm1_23.0.4-0ubuntu1~22.04.1_amd64.deb 409bfe746eadf276e85fd82023b87dc4361d6d537d43936b8f8922a2a8f9fdb4 libgbm1_23.0.4-0ubuntu1~22.04.1_i386.deb 8933615dda5ec6c8ddcdf61bf965a6c89fe27bb58257ddbeccf891fabf565bbc libgl1-mesa-dri_23.0.4-0ubuntu1~22.04.1_amd64.deb 7d83885adb22054ff0ba10a10dd014e2a9de22c6d27300aa835b01489c84c51a libgl1-mesa-dri_23.0.4-0ubuntu1~22.04.1_i386.deb c62aafcd439764e398be1684f47b265a9b6e8e84bc455b912ffd844d27f01a01 libglapi-mesa_23.0.4-0ubuntu1~22.04.1_amd64.deb 0485f51e4362795c823936ff955bc46b47677df8d3554ef3cabf850eea25126e libglapi-mesa_23.0.4-0ubuntu1~22.04.1_i386.deb a66c3572cbee38c2ddf7a001528ff2ee8221eade056f45d7607b878b4d976430 libglx-mesa0_23.0.4-0ubuntu1~22.04.1_amd64.deb 88d881ace0ce9b5d219984c9f6c76aabf381cfec3172225be0b3ef94030b35ad libglx-mesa0_23.0.4-0ubuntu1~22.04.1_i386.deb 2d2bb86103d52eb921003506e1ffc474aa29d24f5732ab5e8161aae9370abc7e libosmesa6_23.0.4-0ubuntu1~22.04.1_amd64.deb 48d1ca94af2e82f8074f66f21f29f19d7ea0cec21c9feb664415e92f3418adba libosmesa6_23.0.4-0ubuntu1~22.04.1_i386.deb Which gives the messages: dpkg: warning: downgrading libegl-mesa0:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgbm1:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgbm1:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgl1-mesa-dri:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libgl1-mesa-dri:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglapi-mesa:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglapi-mesa:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglx-mesa0:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libglx-mesa0:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libosmesa6:amd64 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 dpkg: warning: downgrading libosmesa6:i386 from 23.2.1-1ubuntu3.1~22.04.2 to 23.0.4-0ubuntu1~22.04.1 After reverting, the software starts as normal (and, as expected, there is no error in the terminal). Release: Description: Ubuntu 22.04.4 LTS Release: 22.04 I am not sure exactly which package contains the bug, because these 11 packages upgrade together. The specific version diffs are shown above. One thing I noticed is that this seems to be a fairly large version increase (mesa 23.0.4 --> 23.2.1). If I could get all of the package versions between these two, then
[Desktop-packages] [Bug 2055783] Re: "Unnamed" actions on Rhythmbox's icon right-click menu
The attachment "rhythmbox-contextmenu-askubuntu-1506260.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2055783 Title: "Unnamed" actions on Rhythmbox's icon right-click menu Status in rhythmbox package in Ubuntu: Triaged Bug description: This is from https://askubuntu.com/q/1506260/1004020 . I'm using Rhythmbox 3.4.7 and as you can see on the picture bellow, there are some Unnamed options on Rhythmbox's icon right-click menu: I've tried to copy org.gnome.Rhythmbox.desktop and org.gnome.Rhythmbox.device.desktop files data from Rhythmbox's GitLab to /usr/share/applications (same .desktop files), but nothing has changed. I guess that something is wrong with [Desktop Action ...] entries I've found a solution. [Desktop Action ...] entries were missing the Name properties $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.7-1ubuntu1 Candidate: 3.4.7-1ubuntu1 Version table: *** 3.4.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status # What you expected to happen There should not be any unnamed entries in the GNOME dock or left bar when you right click for the context menu. https://askubuntu.com/q/1506260/1004020 # What happened instead The 4 unnamed entries appear in Ubuntu GNOME. Oddly they don't appear in KDE, but this is a GNOME bug either way because Rhythmbox is made by GNOME. # Analysis The self-answerer added names for the 4 desktop actions. This appeared to fix the problem. However, the new names lack localization. One thing is that the 4 actions will show all the time even if Rhythmbox is not open. Based on the behaviour on KDE, I think that the GNOME developers' original intent was to populate the 4 entries using the running application and hide them otherwise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2055783/+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 2055783] Re: "Unnamed" actions on Rhythmbox's icon right-click menu
** No longer affects: gnome-shell (Ubuntu) ** Changed in: rhythmbox (Ubuntu) Status: New => Triaged ** Changed in: rhythmbox (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2055783 Title: "Unnamed" actions on Rhythmbox's icon right-click menu Status in rhythmbox package in Ubuntu: Triaged Bug description: This is from https://askubuntu.com/q/1506260/1004020 . I'm using Rhythmbox 3.4.7 and as you can see on the picture bellow, there are some Unnamed options on Rhythmbox's icon right-click menu: I've tried to copy org.gnome.Rhythmbox.desktop and org.gnome.Rhythmbox.device.desktop files data from Rhythmbox's GitLab to /usr/share/applications (same .desktop files), but nothing has changed. I guess that something is wrong with [Desktop Action ...] entries I've found a solution. [Desktop Action ...] entries were missing the Name properties $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.7-1ubuntu1 Candidate: 3.4.7-1ubuntu1 Version table: *** 3.4.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status # What you expected to happen There should not be any unnamed entries in the GNOME dock or left bar when you right click for the context menu. https://askubuntu.com/q/1506260/1004020 # What happened instead The 4 unnamed entries appear in Ubuntu GNOME. Oddly they don't appear in KDE, but this is a GNOME bug either way because Rhythmbox is made by GNOME. # Analysis The self-answerer added names for the 4 desktop actions. This appeared to fix the problem. However, the new names lack localization. One thing is that the 4 actions will show all the time even if Rhythmbox is not open. Based on the behaviour on KDE, I think that the GNOME developers' original intent was to populate the 4 entries using the running application and hide them otherwise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/2055783/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
** Changed in: thunderbird Status: New => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Fix Released Status in Mozilla Thunderbird: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1932328]
Resolved per whiteboard -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in GNOME Shell: Fix Released Status in Mozilla Thunderbird: Expired Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Invalid Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 2055783] [NEW] "Unnamed" actions on Rhythmbox's icon right-click menu
Public bug reported: This is from https://askubuntu.com/q/1506260/1004020 . I'm using Rhythmbox 3.4.7 and as you can see on the picture bellow, there are some Unnamed options on Rhythmbox's icon right-click menu: I've tried to copy org.gnome.Rhythmbox.desktop and org.gnome.Rhythmbox.device.desktop files data from Rhythmbox's GitLab to /usr/share/applications (same .desktop files), but nothing has changed. I guess that something is wrong with [Desktop Action ...] entries I've found a solution. [Desktop Action ...] entries were missing the Name properties $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.7-1ubuntu1 Candidate: 3.4.7-1ubuntu1 Version table: *** 3.4.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status # What you expected to happen There should not be any unnamed entries in the GNOME dock or left bar when you right click for the context menu. https://askubuntu.com/q/1506260/1004020 # What happened instead The 4 unnamed entries appear in Ubuntu GNOME. Oddly they don't appear in KDE, but this is a GNOME bug either way because Rhythmbox is made by GNOME. # Analysis The self-answerer added names for the 4 desktop actions. This appeared to fix the problem. However, the new names lack localization. One thing is that the 4 actions will show all the time even if Rhythmbox is not open. Based on the behaviour on KDE, I think that the GNOME developers' original intent was to populate the 4 entries using the running application and hide them otherwise. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Patch added: "rhythmbox-contextmenu-askubuntu-1506260.patch" https://bugs.launchpad.net/bugs/2055783/+attachment/5751666/+files/rhythmbox-contextmenu-askubuntu-1506260.patch ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/2055783 Title: "Unnamed" actions on Rhythmbox's icon right-click menu Status in gnome-shell package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: This is from https://askubuntu.com/q/1506260/1004020 . I'm using Rhythmbox 3.4.7 and as you can see on the picture bellow, there are some Unnamed options on Rhythmbox's icon right-click menu: I've tried to copy org.gnome.Rhythmbox.desktop and org.gnome.Rhythmbox.device.desktop files data from Rhythmbox's GitLab to /usr/share/applications (same .desktop files), but nothing has changed. I guess that something is wrong with [Desktop Action ...] entries I've found a solution. [Desktop Action ...] entries were missing the Name properties $ lsb_release -rd No LSB modules are available. Description:Ubuntu 23.10 Release:23.10 $ apt-cache policy rhythmbox rhythmbox: Installed: 3.4.7-1ubuntu1 Candidate: 3.4.7-1ubuntu1 Version table: *** 3.4.7-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status # What you expected to happen There should not be any unnamed entries in the GNOME dock or left bar when you right click for the context menu. https://askubuntu.com/q/1506260/1004020 # What happened instead The 4 unnamed entries appear in Ubuntu GNOME. Oddly they don't appear in KDE, but this is a GNOME bug either way because Rhythmbox is made by GNOME. # Analysis The self-answerer added names for the 4 desktop actions. This appeared to fix the problem. However, the new names lack localization. One thing is that the 4 actions will show all the time even if Rhythmbox is not open. Based on the behaviour on KDE, I think that the GNOME developers' original intent was to populate the 4 entries using the running application and hide them otherwise. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2055783/+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 2052913] Re: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
this might be the same as the reported upstream issue in mutter https://gitlab.gnome.org/GNOME/mutter/-/issues/3134 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3134 https://gitlab.gnome.org/GNOME/mutter/-/issues/3134 -- 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/2052913 Title: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble (gnome-shell 45.3-1ubuntu1) Default Ubuntu GNOME desktop environment used with no user added extensions. GPU driverstack identical between the two distros (eliminated as a variable). Linux kernel identical between distros (eliminated as a variable) CPU, GPU, and RAM clocks pinned to max. Test case: Minecraft Java Edition (shared drive with identical setup between Ubuntu versions). Fullscreen 1080p. Xorg display server. FPS (uncapped): Ubuntu Jammy: 177fps Ubuntu Noble: 140fps Observations: Ubuntu Jammy: gnome-shell process cpu% when camera is still: 0-1% gnome-shell process cpu% when camera is moving: 10-20% Memory Bandwidth (CPU and GPU shared): 40% Ubuntu Noble: gnome-shell process cpu% when camera is still: 20-55% gnome-shell process cpu% when camera is moving: 30-55% Memory Bandwidth (CPU and GPU shared): 50% In both cases GPU utilization is observed to be near 100%. So in summary, large performance regression regression which appears to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on ubuntu jammy when there the camera is still (even with a fps graph drawn onscreen) in stark contrast to ubuntu noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052913/+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 2052913] Re: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
I tested all of these: * gnome-extensions disable tiling-assist...@ubuntu.com * gnome-extensions disable ubuntu-appindicat...@ubuntu.com * gnome-extensions disable d...@rastersoft.com * gnome-extensions disable ubuntu-d...@ubuntu.com and then had no effect on the performance on noble (yes they did disable and I could see the visible changed in UI). I tried rebooting afterwards with no improvement. I did this: You can test that theory by comparing the windowed performance between jammy and noble. noble performance is about equal with a maximized window and fullscreen (140fps) jammy performance is a bit lower maximized window than fullscreen (162fps vs 177fps) but I see gnome-shell cpu usage at ~50% when when maximized window (vs 0-1% in fullscreen) so yeah definitely appears to be an issue with fullscreen direct scanout not working and additionally just gnome performance regresssions with windowed mode . -- 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/2052913 Title: Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble (gnome-shell 45.3-1ubuntu1) Default Ubuntu GNOME desktop environment used with no user added extensions. GPU driverstack identical between the two distros (eliminated as a variable). Linux kernel identical between distros (eliminated as a variable) CPU, GPU, and RAM clocks pinned to max. Test case: Minecraft Java Edition (shared drive with identical setup between Ubuntu versions). Fullscreen 1080p. Xorg display server. FPS (uncapped): Ubuntu Jammy: 177fps Ubuntu Noble: 140fps Observations: Ubuntu Jammy: gnome-shell process cpu% when camera is still: 0-1% gnome-shell process cpu% when camera is moving: 10-20% Memory Bandwidth (CPU and GPU shared): 40% Ubuntu Noble: gnome-shell process cpu% when camera is still: 20-55% gnome-shell process cpu% when camera is moving: 30-55% Memory Bandwidth (CPU and GPU shared): 50% In both cases GPU utilization is observed to be near 100%. So in summary, large performance regression regression which appears to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on ubuntu jammy when there the camera is still (even with a fps graph drawn onscreen) in stark contrast to ubuntu noble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2052913/+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 2055528] Re: ftbfs with golang-1.22: missing crosscall_amd64 symbol
This bug was fixed in the package ubuntu-report - 1.7.3 --- ubuntu-report (1.7.3) noble; urgency=medium * Use regex to capature all crosscall symbols in libsysmetrics1. (LP: #2055528) These are internal symbols from cgo. Fix FTBFS with golang-1.22. -- Shengjing Zhu Fri, 01 Mar 2024 15:47:58 +0800 ** Changed in: ubuntu-report (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2055528 Title: ftbfs with golang-1.22: missing crosscall_amd64 symbol Status in ubuntu-report package in Ubuntu: Fix Released Bug description: https://launchpadlibrarian.net/708934179/buildlog_ubuntu-noble- amd64.ubuntu-report_1.7.2_BUILDING.txt.gz dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsysmetrics1/DEBIAN/symbols doesn't match completely debian/libsysmetrics1.symbols --- debian/libsysmetrics1.symbols (libsysmetrics1_1.7.2_amd64) +++ dpkg-gensymbolsKEGIqW 2024-01-12 08:59:34.126055379 + @@ -1,9 +1,9 @@ libsysmetrics.so.1 libsysmetrics1 #MINVER# (regex|optional)"_cgo.*" 1.0.0 - (arch=arm64 riscv64)crosscall1@Base 1.0.0 + crosscall1@Base 1.0.0 crosscall2@Base 1.0.0 (arch=i386)crosscall_386@Base 1.0.0 - (arch=amd64)crosscall_amd64@Base 1.0.0 +#MISSING: 1.7.2# (arch=amd64)crosscall_amd64@Base 1.0.0 (arch=armhf)crosscall_arm1@Base 1.0.0 (arch=ppc64el)crosscall_ppc64@Base 1.0.0 (arch=s390x)crosscall_s390x@Base 1.0.0 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2055528/+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 2055720] Re: Edubuntu upgrade removed universe repo mantic -> noble
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu) Importance: Undecided => High -- 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/2055720 Title: Edubuntu upgrade removed universe repo mantic -> noble Status in software-properties package in Ubuntu: New Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: Upon upgrade from mantic to noble, my bare metal Edubuntu install removed the Universe repo from the installation and, therefore, did not upgrade any Edubuntu-specific packages. I suspect this was caused by the apt DEB-822 upgrade to the repo and not detecting the universe repo as required by the Edubuntu installation. As Edubuntu looks identical to Ubuntu Desktop in terms of installation on the surface due to it also being a GNOME desktop, I suspect an assumption may have been derived from this. Additionally, simply trying `add-apt-repository universe` was ineffective, so that might need some work as well. Will attach logs if I can find them, but please do advise what logs you need. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055720/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
Image of running the beta. works fine with --disable-gpu ** Attachment added: "betaIssue.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+attachment/5751657/+files/betaIssue.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
Here is the output of the commands you asked for. Note this was after I installed the beta version snap connections chromium Interface PlugSlot Notes audio-playbackchromium:audio-playback :audio-playback - audio-record chromium:audio-record :audio-record - bluez chromium:bluez :bluez - browser-support chromium:browser-sandbox :browser-support- camerachromium:camera :camera - content chromium:foo-install-cups - - content[gnome-42-2204]chromium:gnome-42-2204 gnome-42-2204:gnome-42-2204 - content[gtk-3-themes] chromium:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] chromium:icon-themes gtk-common-themes:icon-themes - content[sound-themes] chromium:sound-themes gtk-common-themes:sound-themes - cups chromium:cups cups:cups - desktop chromium:desktop:desktop - desktop-legacychromium:desktop-legacy :desktop-legacy - gsettings chromium:gsettings :gsettings - hardware-observe chromium:hardware-observe :hardware-observe - home chromium:home :home - joystick chromium:joystick :joystick - mount-observe chromium:mount-observe - - mpris - chromium:mpris - network chromium:network:network - network-bind chromium:network-bind :network-bind - network-manager chromium:network-manager- - openglchromium:opengl :opengl - password-manager-service chromium:password-manager-service - - personal-fileschromium:chromium-config :personal-files - personal-fileschromium:dot-local-share-applications :personal-files - personal-fileschromium:dot-local-share-icons :personal-files - raw-usb chromium:raw-usb- - removable-media chromium:removable-media :removable-media- screen-inhibit-controlchromium:screen-inhibit-control :screen-inhibit-control - system-files chromium:etc-chromium-browser-policies :system-files - system-packages-doc chromium:system-packages-doc :system-packages-doc- u2f-devices chromium:u2f-devices:u2f-devices - unity7chromium:unity7 :unity7 - upower-observechromium:upower-observe :upower-observe - wayland chromium:wayland:wayland - x11 chromium:x11:x11 - snap list|grep ^gnome gnome-3-38-20040+git.efb213a 143latest/stable/… canonical** - gnome-42-2204 0+git.ff35a85 141latest/stable canonical** - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or
[Desktop-packages] [Bug 2054887] Re: Grahpical bugs caused by unable to access libdrm
I still have the issue after switching to the beta version 123.0.6312.22 ** Attachment added: "Beta.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+attachment/5751656/+files/Beta.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
I can confirm the --disable-gpu argument made chromium work as intended. I'll give the beta a try. Thank you so much for your help and looking in to this issue! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 1641215] Re: nvidia driver 304 fails to load libGLU, GLX errors
obsolete bug, nvidia 304 is gone ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1641215 Title: nvidia driver 304 fails to load libGLU, GLX errors Status in xorg package in Ubuntu: Invalid Bug description: resulting setup is useless for openGL and SDL rendering is very slow kernels 4.4.0-47 -45 xubuntu 16.04 64bit ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 304.132 Fri Sep 16 11:02:09 PDT 2016 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Nov 11 16:05:16 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.132, 4.4.0-45-generic, x86_64: installed nvidia-304, 304.132, 4.4.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0292] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation G71 [GeForce 7900 GS] [10de:0370] InstallationDate: Installed on 2016-11-05 (6 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=9b509dd9-28f8-42d9-bd9f-c2fa7eb33811 ro vebose SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0605 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A8R-MVP dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0605:bd12/09/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA8R-MVP:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Thu Nov 10 16:07:53 2016 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputImExPS/2 Logitech Wheel Mouse MOUSE, id 9 xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1641215/+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 2032910] Re: 60x11-common_xdg_path sets wrong XDG_DATA_DIRS on Plasma
that's not the file you're looking for ** Package changed: xorg (Ubuntu) => kubuntu-settings (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2032910 Title: 60x11-common_xdg_path sets wrong XDG_DATA_DIRS on Plasma Status in kubuntu-settings package in Ubuntu: New Bug description: XDG_DATA_DIRS shouldn't include /usr/share/plasma by default. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 1:7.7+23ubuntu2 3) What you expected to happen XDG_DATA_DIRS shouldn't include /usr/share/plasma 4) What happened instead XDG_DATA_DIRS includes /usr/share/plasma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-settings/+bug/2032910/+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 2042956] Re: Error activating XKB configs (After sleep mode)
sounds more like an issue in MATE
** Package changed: xorg (Ubuntu) => mate-common (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042956
Title:
Error activating XKB configs (After sleep mode)
Status in mate-common package in Ubuntu:
New
Bug description:
I have been getting this random error always when coming back from
sleep mode.
Random because it doesn't always pop-up at resume.
Also half of the suggestions displayed in the error message does not
seem to work so perhaps this problem is twofolds.
Problem 1: error activating XKB
Problem 2: update the "Please include" portion as it does not reflect the
reality of 23.10
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckMismatches: ./casper/filesystem.squashfs
CasperMD5CheckResult: fail
CompositorRunning: None
CurrentDesktop: MATE
Date: Sun Nov 5 10:57:04 2023
DistUpgraded: 2023-10-12 22:24:13,551 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [1002:15d8] (rev df) (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Picasso/Raven 2 [Radeon Vega Series /
Radeon Vega Mobile Series] [103c:87b7]
InstallationDate: Installed on 2023-02-23 (256 days ago)
InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=3e40054f-c010-4c20-834b-badb6d17cf88 ro splash splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-13 (24 days ago)
dmi.bios.date: 12/29/2022
dmi.bios.release: 15.67
dmi.bios.vendor: AMI
dmi.bios.version: F.67
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.21
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.21
dmi.modalias:
dmi:bvnAMI:bvrF.67:bd12/29/2022:br15.67:efr28.21:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.21:cvnHP:ct10:cvrChassisVersion:sku10M11UA#ABL:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 10M11UA#ABL
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-common/+bug/2042956/+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 2055762] [NEW] Closing window button doesn't appear correctly on the second display
Public bug reported: If toggle it to the Activity task, its closing window button on second display (other monitor) is showed as well, however if toggle it to the Program Menu then the X button doesn't show completely. I attached a recorded explains it. Please observe the left screen's X button. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "스크린캐스트 2024년 03월 02일 15시 28분 34초.webm" https://bugs.launchpad.net/bugs/2055762/+attachment/5751477/+files/%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%BA%90%EC%8A%A4%ED%8A%B8%202024%EB%85%84%2003%EC%9B%94%2002%EC%9D%BC%2015%EC%8B%9C%2028%EB%B6%84%2034%EC%B4%88.webm -- 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/2055762 Title: Closing window button doesn't appear correctly on the second display Status in gnome-shell package in Ubuntu: New Bug description: If toggle it to the Activity task, its closing window button on second display (other monitor) is showed as well, however if toggle it to the Program Menu then the X button doesn't show completely. I attached a recorded explains it. Please observe the left screen's X button. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2055762/+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
