[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Hello jeremyszu, or anyone else affected,
Accepted ubuntu-drivers-common into lunar-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.7.1.2
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
lunar to verification-done-lunar. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-lunar. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: ubuntu-drivers-common (Ubuntu Lunar)
Status: Confirmed => Fix Committed
** Tags removed: verification-failed
** Tags added: verification-needed verification-needed-lunar
--
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:
Triaged
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
Confirmed
Status in ubuntu-drivers-common source package in Lunar:
Fix Committed
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 2037569] Re: udev issues with mantic beta
Marking invalid in systemd, other than long-standing udev rules being involved I'm not sure this will be fixed in systemd. Exploring if libblockdev with the s390 plugin enabled helps. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Also affects: libblockdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037756] [NEW] Gnome session crashes after resume from suspend
Public bug reported: I upgraded to the Ubuntu 23.10 beta from 23.04. After the upgrade, every time I suspend the laptop and resume from suspend the gnome session crashes and I am returned to the login screen. I am using a Thinkpad T14 gen 2 AMD laptop. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 16:25:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (604 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- 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/2037756 Title: Gnome session crashes after resume from suspend Status in gnome-shell package in Ubuntu: New Bug description: I upgraded to the Ubuntu 23.10 beta from 23.04. After the upgrade, every time I suspend the laptop and resume from suspend the gnome session crashes and I am returned to the login screen. I am using a Thinkpad T14 gen 2 AMD laptop. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 16:25:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-02 (604 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037756/+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 2028082] Re: Update glib to 2.76.4
** Description changed: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. - Ensure that there aren't autopgktest regressions triggered by this + Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: In Progress Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
> Also issues like having to be able to update nodejs in a stable Ubuntu serie to build a newer thunderbird should make us consider phasing out the deb in favor of using a snap as we did for firefox... Funny, I was just about to say this :) People on Reddit will be mad but from both a security standpoint it seems it's the right thing to do. Hopefully this switch can get done in time for 24.04 LTS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+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 2037569] Re: udev issues with mantic beta
In function udisks_linux_partition_table_update if num_parts > 0, no ID_PART_TABLE_TYPE is present, and bd_part_get_disk_spec fails to get the disk information including part_type, this function will fail. Also, because libblockdev uses libfdisk in a manner that opens the disk RW, that causes another udev event and that will cause udisks_linux_partition_table_update to be called again. -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037461] Re: Broken scaling on app labels in app grid on multi monitor setups with varying scale factors
Seeing the same thing with text in notifications when the higher scaled monitor is above the top panel. Don't know if it's related the cause of this multimonitor weirdness but the screenshot attached was taken on the 1920x1080 monitor but somehow has an image size of 2884 × 1622, even the secondary monitor is only 2560x1600. I can create a separate bug for this? ** Attachment added: "Screenshot from 2023-09-29 19-22-24.png" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037461/+attachment/5705421/+files/Screenshot%20from%202023-09-29%2019-22-24.png -- 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/2037461 Title: Broken scaling on app labels in app grid on multi monitor setups with varying scale factors Status in gnome-shell package in Ubuntu: New Bug description: Multi monitor with different scale factors causes app grid labels scaling to break when page scrolls from direction of adjacent monitor with higher scaling. Steps to reproduce: 1) Configure a second monitor (higher scale factor) to be either on the left or right of the primary monitor (lower scale factor) 2) Open app grid 3) Scroll page so it moves toward the secondary monitor 4) Scroll page back to make it come back from the direction of the secondary monitor 5) Observe enlarged text (might require a few back and forth scrolls) Disabled all extensions to rule out an extension being the cause. Possibly same underlying cause as this bug?: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/2037143 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Sep 26 19:11:29 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-31 (544 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037461/+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 2034986] Re: some text became unreadable during a distribution upgrade
I have uploaded the fix. I am adding block-proposed so that I can do another test, i.e. do-release-upgrade -d -p, just because the manual way of testing differs slightly. ** Changed in: ubuntu-release-upgrader (Ubuntu Mantic) Status: In Progress => Fix Committed ** Tags added: block-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: Fix Committed Status in ubuntu-meta source package in Mantic: In Progress Status in ubuntu-release-upgrader source package in Mantic: Fix Committed Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2037011] Re: Can't create ovpn
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037011 Title: Can't create ovpn Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: In Progress Status in network-manager-openvpn package in Fedora: New Bug description: Settings -> Network -> Add VPN -> Import from file to import an .ovpn file does nothing after clicking Add, it just returns to the Add VPN page and no VPN connection is added. The same .ovpn file works fine in 22.04. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager-openvpn 1.10.2-3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 22:12:58 2023 InstallationDate: Installed on 2023-09-18 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037011/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
** Merge proposal linked:
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1923363
Title:
Grant access to hardware (UARTs, I2C, etc.) via custom udev rules
Status in cloud-init package in Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Invalid
Status in ubuntu-settings package in Ubuntu:
Confirmed
Status in user-setup package in Ubuntu:
Invalid
Status in cloud-init source package in Impish:
Won't Fix
Status in ubiquity source package in Impish:
Invalid
Status in ubuntu-settings source package in Impish:
Won't Fix
Status in user-setup source package in Impish:
Invalid
Status in cloud-init source package in Jammy:
Confirmed
Status in ubiquity source package in Jammy:
Invalid
Status in ubuntu-settings source package in Jammy:
Confirmed
Status in user-setup source package in Jammy:
Invalid
Status in cloud-init source package in Kinetic:
Won't Fix
Status in ubiquity source package in Kinetic:
Invalid
Status in ubuntu-settings source package in Kinetic:
Won't Fix
Status in user-setup source package in Kinetic:
Invalid
Status in cloud-init source package in Lunar:
Won't Fix
Status in ubiquity source package in Lunar:
Invalid
Status in ubuntu-settings source package in Lunar:
Won't Fix
Status in user-setup source package in Lunar:
Invalid
Status in cloud-init source package in Mantic:
Fix Released
Status in ubiquity source package in Mantic:
Invalid
Status in ubuntu-settings source package in Mantic:
Confirmed
Status in user-setup source package in Mantic:
Invalid
Bug description:
We're attempting to make the GPIO system on the Raspberry Pi images
work "out of the box" on the new image. By default, GPIO kernel
devices are made available to members of the "dialout" group which the
initial user is added to by default on our server images. However,
we've noticed that this isn't the case on the desktop images.
The regression potential is minimal; the group already exists and
we're simply adding the freshly created user to a new group and not
removing any existing memberships. The group in question ("dialout")
is also rarely used these days except for providing access to serial
consoles, and as mentioned above is already a default membership on
the server images. The change has been tested on the desktop image
successfully.
A test build of the updated image will be made under
https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
attach a debdiff shortly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 2037642] Re: [FFe] Raspberry Pi 5 support
** Merge proposal linked: https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
The real issue is that our previous thunderbird maintainer left and we didn't get a new member to replace him and the other team members have more than enough to do already. I'm doing my best to get the updates out but I'm not that familiar with the project and I'm also busy, if anyone wants to step up to help instead of complaining about our priority being wrong that would help... Also issues like having to be able to update nodejs in a stable Ubuntu serie to build a newer thunderbird should make us consider phasing out the deb in favor of using a snap as we did for firefox... Meanwhile it seems that the depends requirement doesn't need to be as strict so for this round we should be able to just lower the depends in a patch, new builds have been uploaded to the security ppa for 115.3.1 on the different series -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
"Let's get ubuntu-drivers-common uploaded ASAP so that we can test the fix from a daily build well before release" he said with his release team hat on. -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Triaged Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 1895665] Re: PulseAudio automatically switches away from HDMI after display sleep
*** This bug is a duplicate of bug 1888598 *** https://bugs.launchpad.net/bugs/1888598 Likeit is hardcoded...really? Why? https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/blame/master/src/modules/module-switch-on-connect.c#L36 -- 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/1895665 Title: PulseAudio automatically switches away from HDMI after display sleep Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have an Nvidia based video card that has an HDMI output + a DisplayPort output. DisplayPort output audio is listed as "Digital Stereo (HDMI)" and HDMI output is listed as "Digital Stereo (HDMI 2)". I prefer to use "Digital Stereo (HDMI 2)". But after each display sleep (screen lock for example) audio is switched to built in audio ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.6 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Sep 15 14:56:58 2020 InstallationDate: Installed on 2020-06-20 (86 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.1 dmi.board.name: 0CNDTP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.1:bd11/11/2019:svnDellInc.:pnG55590:pvr:rvnDellInc.:rn0CNDTP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5590 dmi.product.sku: 08EA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1895665/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
Thunderbird 115.0 came out 11 weeks ago, first confirmed working Test build 6 weeks ago but after that the focus seems to have shifted back from bringing TB 115 towards TB 102 maintenance and fighting evil button colors. Now, when Mozillas transition phase is completely over, the first real show stopper pops up?!? This is exactly, what S. Auer described in many words as "wrong priorities". Major Thunderbird package updates have been going like this for many years now. I am really disappointed. :( -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+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 2037569] Re: udev issues with mantic beta
I think it's caused by udisksctl here: https://github.com/storaged-project/udisks/blob/c7027d888c00381851d918f33a13102e7b86e188/tools/udisksctl.c#L2810C1-L2811C75 due to its repeating monitor messages: udisksctl monitor ** (udisksctl monitor:424911): WARNING **: 11:14:33.100: (udisksctl.c:2811):monitor_on_interface_proxy_properties_changed: runtime check failed: (g_strv_length ((gchar **) invalidated_properties) == 0) -- 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/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Confirmed Status in systemd package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037642] Re: [FFe] Raspberry Pi 5 support
This bug was fixed in the package rpi-eeprom - 18.4-1ubuntu1 --- rpi-eeprom (18.4-1ubuntu1) mantic; urgency=medium * New upstream release (LP: #2037642) * Adds Raspberry Pi 5 support -- Dave Jones Thu, 28 Sep 2023 14:51:50 +0100 ** Changed in: rpi-eeprom (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
Could the gnome-shell crash be a consequence of how we are booting the Legacy image and starting the desktop environment? I noticed the following in the crash report "gnome-shell --sm-disable --mode=ubiquity". -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
Hi that was a client Laptop and I don't have access to it anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers Status in mesa package in Ubuntu: Incomplete Bug description: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39.
[Desktop-packages] [Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
No, only one that even has gnome in the name is network-manager-gnome. I haven't had any freezing issue the last couple days, but will run and post the journal commands next time it happens. Still getting JS Error workspace is undefined and stack traces every time I exit "activities" if my mouse cursor is hovering over an application window on a monitor other than my primary display, and can't' update stage views actor any time I resize any application on any monitor, with the exception of using the application controls to maximize (not full screen). -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4
[Desktop-packages] [Bug 2016435] Re: amdgpu driver randomly resets
Random resets are "typically" triggered by mesa or application bugs. Can you still trigger them in the latest mantic (which has a more up to date mesa and kernel)? ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/2016435 Title: amdgpu driver randomly resets Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Invalid Bug description: amdgpu tends to randomly reset. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xserver-xorg-video-amdgpu 23.0.0-1 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE Date: Sun Apr 16 18:04:34 2023 DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1002:73bf] (rev c0) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] [1849:5212] NVIDIA Corporation GA104 [GeForce RTX 3060 Ti] [10de:2486] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GA104 [GeForce RTX 3060 Ti] [3842:3663] InstallationDate: Installed on 2022-01-14 (457 days ago) InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: Gigabyte Technology Co., Ltd. X570S AORUS MASTER ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1 vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.2.0-20-generic SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: Upgraded to lunar on 2023-04-01 (14 days ago) dmi.bios.date: 10/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F3c dmi.board.asset.tag: Default string dmi.board.name: X570S AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF3c:bd10/01/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570S AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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 --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: KDE DistUpgraded: 2023-04-01 18:21:47,742 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroRelease: Ubuntu 23.04 DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 6.2.0-19-generic, x86_64: installed openrazer-driver/3.4.0, 6.2.0-20-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-19-generic, x86_64: installed xone/v0.3-1-g2467407, 6.2.0-20-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard:
[Desktop-packages] [Bug 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers Status in mesa package in Ubuntu: Incomplete Bug description: Sony laptop with AMD RV710 Try to play a DVD with Vaapi mesa drivers installed ALl players crash , example with VLC ( Works great without VAAPI ) libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva info: va_openDriver() returns 0 [7fd5d8085d50] main generic debug: using glconv module "glconv_vaapi_drm" [7fd5d8001610] main vout display debug: using vout display module "gl" [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4028010] main video output debug: original format sz 720x576, of (0,0), vsz 720x576, 4cc VAOP, sar 16:15, msk r0x0 g0x0 b0x0 [7fd5d4029610] main spu text debug: removing module "freetype" [7fd5d4072b40] main spu text debug: looking for text renderer module matching "any": 2 candidates [7fd5d4072b40] freetype spu text debug: Building font databases. [5601ed37aed0] qt interface debug: Logical video size: 768x576 [7fd5d4039c20] main window debug: resized to 768x576 [7fd5d8001610] main vout display debug: VoutDisplayEvent 'resize' 768x576 [7fd5d4072b40] freetype spu text debug: Took -23713 microseconds [7fd5d4072b40] main spu text debug: using text renderer module "freetype" [7fd5d409d080] main generic debug: looking for hw decoder module matching "vaapi": 3 candidates [7fd5d409d080] main generic debug: using hw decoder module "vaapi" [7fd5d004efb0] avcodec decoder: Using Mesa Gallium driver 22.0.5 for AMD RV710 (DRM 2.50.0 / 5.15.0-46-generic, LLVM 13.0.1) for hardware decoding [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld chosen by get_format(). [mpeg2video @ 0x7fd5d4087d80] Format vaapi_vld requires hwaccel initialisation. [mpeg2video @ 0x7fd5d4087d80] Using deprecated struct vaapi_context in decode. [mpeg2video @ 0x7fd5d4087d80] Using user-supplied decoder context: 0x15/0x16. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 0, 40 bytes) is 0x17. [mpeg2video @ 0x7fd5d4087d80] Param buffer (type 1, 288 bytes) is 0x18. [mpeg2video @ 0x7fd5d4087d80] Slice 0 param buffer (48 bytes) is 0x19. [mpeg2video @ 0x7fd5d4087d80] Slice 0 data buffer (176 bytes) is 0x1a. [mpeg2video @ 0x7fd5d4087d80] Slice 1 param buffer (48 bytes) is 0x1b. [mpeg2video @ 0x7fd5d4087d80] Slice 1 data buffer (175 bytes) is 0x1c. [mpeg2video @ 0x7fd5d4087d80] Slice 2 param buffer (48 bytes) is 0x1d. [mpeg2video @ 0x7fd5d4087d80] Slice 2 data buffer (175 bytes) is 0x1e. [mpeg2video @ 0x7fd5d4087d80] Slice 3 param buffer (48 bytes) is 0x1f. [mpeg2video @ 0x7fd5d4087d80] Slice 3 data buffer (175 bytes) is 0x20. [mpeg2video @ 0x7fd5d4087d80] Slice 4 param buffer (48 bytes) is 0x21. [mpeg2video @ 0x7fd5d4087d80] Slice 4 data buffer (175 bytes) is 0x22. [mpeg2video @ 0x7fd5d4087d80] Slice 5 param buffer (48 bytes) is 0x23. [mpeg2video @ 0x7fd5d4087d80] Slice 5 data buffer (175 bytes) is 0x24. [mpeg2video @ 0x7fd5d4087d80] Slice 6 param buffer (48 bytes) is 0x25. [mpeg2video @ 0x7fd5d4087d80] Slice 6 data buffer (175 bytes) is 0x26. [mpeg2video @ 0x7fd5d4087d80] Slice 7 param buffer (48 bytes) is 0x27. [mpeg2video @ 0x7fd5d4087d80] Slice 7 data buffer (175 bytes) is 0x28. [mpeg2video @ 0x7fd5d4087d80] Slice 8 param buffer (48 bytes) is 0x29. [mpeg2video @ 0x7fd5d4087d80] Slice 8 data buffer (175 bytes) is 0x2a. [mpeg2video @ 0x7fd5d4087d80] Slice 9 param buffer (48 bytes) is 0x2b. [mpeg2video @ 0x7fd5d4087d80] Slice 9 data buffer (175 bytes) is 0x2c. [mpeg2video @ 0x7fd5d4087d80] Slice 10 param buffer (48 bytes) is 0x2d. [mpeg2video @ 0x7fd5d4087d80] Slice 10 data buffer (175 bytes) is 0x2e. [mpeg2video @ 0x7fd5d4087d80] Slice 11 param buffer (48 bytes) is 0x2f. [mpeg2video @ 0x7fd5d4087d80] Slice 11 data buffer (175 bytes) is 0x30. [mpeg2video @ 0x7fd5d4087d80] Slice 12 param buffer (48 bytes) is 0x31. [mpeg2video @ 0x7fd5d4087d80] Slice 12 data buffer (175 bytes) is 0x32. [mpeg2video @ 0x7fd5d4087d80] Slice 13 param buffer (48 bytes) is 0x33. [mpeg2video @ 0x7fd5d4087d80] Slice 13 data buffer (175 bytes) is 0x34. [mpeg2video @ 0x7fd5d4087d80] Slice 14 param buffer (48 bytes) is 0x35. [mpeg2video @ 0x7fd5d4087d80] Slice 14 data buffer (175 bytes) is 0x36. [mpeg2video @ 0x7fd5d4087d80] Slice 15 param buffer (48 bytes) is 0x37. [mpeg2video @ 0x7fd5d4087d80] Slice 15 data buffer (571 bytes) is 0x38. [mpeg2video @ 0x7fd5d4087d80] Slice 16 param buffer (48 bytes) is 0x39.
[Desktop-packages] [Bug 1094959] Re: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade
> NonfreeKernelModules: fglrx Nothing that will be done in mesa for an issue with fglrx anyway these days. ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1094959 Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade Status in mesa package in Ubuntu: Won't Fix Bug description: I was trying to (re)install Steam, and I got this error. One weird thing that happened before is that Steam (and all it's files) wiped themselves out of my system for no reason... ProblemType: PackageDistroRelease: Ubuntu 12.04 Package: libgl1-mesa-dri 8.0.4-0ubuntu0.2 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] ProcVersionSignature: Ubuntu 3.2.0-35.55-generic 3.2.34 Uname: Linux 3.2.0-35-generic x86_64 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.0.1-0ubuntu17 AptOrdering: libgl1-mesa-dri: Install libgl1-mesa-dri: Configure Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz Date: Mon Dec 31 16:48:23 2012 DistUpgraded: Fresh install DistroCodename: precise DistroVariant: ubuntu DkmsStatus: fglrx-updates, 9.000, 3.2.0-34-generic, x86_64: installed fglrx-updates, 9.000, 3.2.0-35-generic, x86_64: installed DpkgTerminalLog: Unpacking libgl1-mesa-dri:i386 (from .../libgl1-mesa-dri_8.0.4-0ubuntu0.2_i386.deb) ... dpkg: error processing /var/cache/apt/archives/libgl1-mesa-dri_8.0.4-0ubuntu0.2_i386.deb (--unpack): './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system ErrorMessage: './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices [AMD] nee ATI Device [1002:683d] (prog-if 00 [VGA controller]) Subsystem: Giga-byte Technology Device [1458:2556] InstallationMedia: This MachineType: HP-Pavilion FQ601AA-A2L m9505f MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-35-generic root=UUID=4fd95ed0-53b7-4da0-9a18-989348244233 ro quiet splashSourcePackage: mesa Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz] failed to install/upgrade: './usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz' is different from the same file on the system UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/10/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.43 dmi.board.name: Benicia dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.01 dmi.chassis.asset.tag: Asset-1234 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.43:bd09/10/2009:svnHP-Pavilion:pnFQ601AA-A2Lm9505f:pvr:rvnPEGATRONCORPORATION:rnBenicia:rvr1.01:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: FQ601AA-A2L m9505f dmi.sys.vendor: HP-Pavilion version.compiz: compiz 1:0.9.7.12-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.32-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.4-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.4-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu10.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.0-0ubuntu1.2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu4.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1094959/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
In this case the kernel is the "messenger" for the page fault. This is more likely to be a mesa or application issue than a kernel issue. Can you please raise a ticket to the upstream mesa bug tracker? https://gitlab.freedesktop.org/mesa/mesa/ ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037569] Re: udev issues with mantic beta
Today I did some more tests and investigations. First of all I moved to the new mantic ISO image (20230928) that improved things quite a lot! The installation (on z/VM so far) is again very snappy and quick, incl. the enablement of a DASD device in the zDev activation screen. At the end of the installation, before hitting 'Reboot now' I went to the console and had a look at top to see if udev related processes are active, but I couldn't identify any: top - 10:47:51 up 9 min, 2 users, load average: 0.44, 0.41, 0.20 Tasks: 137 total, 1 running, 136 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3988.9 total,214.3 free, 1957.6 used, 3233.2 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 2031.3 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 15026 root 20 08788 4864 2816 R 0.7 0.1 0:00.28 top 1439 root 20 0 129824 74216 21376 S 0.3 1.8 0:03.76 /snap/subiquity/5183/usr/bin/python3.10 /snap/subiquity/518+ 1441 root 20 0 129788 74312 21376 S 0.3 1.8 0:03.57 /snap/subiquity/5183/usr/bin/python3.10 /snap/subiquity/518+ 2381 root 20 0 12216 5760 4864 S 0.3 0.1 0:00.10 sudo snap run subiquity 2383 root 20 0 206204 77680 21632 S 0.3 1.9 0:04.96 /snap/subiquity/5183/usr/bin/python3.10 -m subiquity 1 root 20 0 103300 13676 8940 S 0.0 0.3 0:03.49 /sbin/init --- 2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kthreadd] 3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [rcu_gp] 4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [rcu_par_gp] 5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [slub_flushwq] 6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [netns] 8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [kworker/0:0H-events_highpri] 9 root 20 0 0 0 0 I 0.0 0.0 0:00.00 [kworker/0:1-cgroup_destroy] 10 root 20 0 0 0 0 I 0.0 0.0 0:01.11 [kworker/u128:0-events_unbound] 11 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 [mm_percpu_wq] 12 root 20 0 0 0 0 I 0.0 0.0 0:00.00 [rcu_tasks_rude_kthread] 13 root 20 0 0 0 0 I 0.0 0.0 0:00.00 [rcu_tasks_trace_kthread] Then, having the post-install reboot completed, and looking at top, I can observe the udev activities: top - 10:55:26 up 6 min, 1 user, load average: 2.16, 1.75, 0.84 Tasks: 108 total, 5 running, 103 sleeping, 0 stopped, 0 zombie %Cpu(s): 18.1 us, 22.7 sy, 0.0 ni, 48.8 id, 8.1 wa, 0.6 hi, 0.8 si, 0.9 st MiB Mem : 3988.9 total, 3274.2 free,271.4 used,539.0 buff/cache MiB Swap: 0.0 total, 0.0 free, 0.0 used. 3717.5 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1177 root 20 0 24884 5724 2560 R 33.2 0.1 1:50.24 (udev-worker) 1 root 20 0 168592 12912 8432 R 20.6 0.3 1:07.93 /sbin/init 690 root 20 0 467964 13112 10752 D 15.6 0.3 0:52.91 /usr/libexec/udisks2/udisksd 660 message+ 20 09328 4480 3840 S 14.6 0.1 0:52.68 @dbus-daemon --system --address=systemd: --nofork --nopidfile -+ 16285 ubuntu20 0 18004 9984 8448 S 10.6 0.2 0:33.06 /lib/systemd/systemd --user 385 root 20 0 24764 7492 4676 S 9.3 0.2 0:30.40 /lib/systemd/systemd-udevd 373 root rt 0 288412 26368 8064 S 6.6 0.6 0:21.50 /sbin/multipathd -d -s 686 root 20 0 16096 7424 6528 S 4.0 0.2 0:13.20 /lib/systemd/systemd-logind 681 root 20 0 2066332 34480 21248 S 1.7 0.8
[Desktop-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: rpi-eeprom (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: ubuntu-settings (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1883457 Title: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else. Status in gimp package in Ubuntu: Confirmed Status in gnome-xcf-thumbnailer package in Ubuntu: Confirmed Status in gthumb package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in nemo package in Ubuntu: Invalid Status in snapd package in Ubuntu: Confirmed Bug description: Hi, On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see thumbnails for .xcf files only « inside » Gimp and nowhere else ( Nemo, Nautilus, gThumb… ) I did a messy workaround for .xcf thumbnails to appear anywhere expected : I put all of my user’s thumbnails into ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is a symlink targeting the first. You’d agree it’s absolutely a bad idea to store all of an user’s thumbnails into a particular subfolder of a particular snap. How tell my session to look for thumbnails not only in ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/ ? For references : ⋅ https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files ⋅ https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799 ⋅ https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1883457/+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 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-xcf-thumbnailer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1883457 Title: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else. Status in gimp package in Ubuntu: Confirmed Status in gnome-xcf-thumbnailer package in Ubuntu: Confirmed Status in gthumb package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in nemo package in Ubuntu: Invalid Status in snapd package in Ubuntu: Confirmed Bug description: Hi, On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see thumbnails for .xcf files only « inside » Gimp and nowhere else ( Nemo, Nautilus, gThumb… ) I did a messy workaround for .xcf thumbnails to appear anywhere expected : I put all of my user’s thumbnails into ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is a symlink targeting the first. You’d agree it’s absolutely a bad idea to store all of an user’s thumbnails into a particular subfolder of a particular snap. How tell my session to look for thumbnails not only in ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/ ? For references : ⋅ https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files ⋅ https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799 ⋅ https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1883457/+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 1883457] Re: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gimp (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1883457 Title: Thumbnails for .xcf files only show in Gimp ( snap ) and nowhere else. Status in gimp package in Ubuntu: Confirmed Status in gnome-xcf-thumbnailer package in Ubuntu: Confirmed Status in gthumb package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in nemo package in Ubuntu: Invalid Status in snapd package in Ubuntu: Confirmed Bug description: Hi, On Ubuntu ( Budgie ) 20.04 when using Gimp as a snap, you’ll see thumbnails for .xcf files only « inside » Gimp and nowhere else ( Nemo, Nautilus, gThumb… ) I did a messy workaround for .xcf thumbnails to appear anywhere expected : I put all of my user’s thumbnails into ~/snap/gimp/common/.cache/thumbnails/ and now ~/.cache/thumbnails/ is a symlink targeting the first. You’d agree it’s absolutely a bad idea to store all of an user’s thumbnails into a particular subfolder of a particular snap. How tell my session to look for thumbnails not only in ~/.cache/thumbnails/ but also in any thumbnails folder inside ~/snap/ ? For references : ⋅ https://askubuntu.com/questions/1250031/gimp-snap-and-thumbnails-for-xcf-files ⋅ https://discourse.ubuntubudgie.org/t/gimp-as-a-snap-no-thumbnails-for-xcf-files-in-nemo-gthumb/3799 ⋅ https://forum.snapcraft.io/t/gimp-and-thumbnails-for-xcf-files/18131/3?u=coeur-noir ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2053949 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1883457/+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 1970291] Re: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions
First prototype solution proposed here: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970291 Title: [nvidia] Secondary monitor performance is slow on an Nvidia hybrid system in Wayland sessions Status in GNOME Shell: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: In session with Wayland the Nvidia driver settings do not load. And there is a sluggishness when opening apps, show applications menu, maximize, changing workspace, resize, changing monitor windows etc. When in an Xorg session the Nvidia settings load correctly and the performance is satisfactory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.60.02 Wed Mar 16 11:24:05 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 21:18:08 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:2086] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation TU116M [GeForce GTX 1660 Ti Mobile] [8086:2086] InstallationDate: Installed on 2022-04-24 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) MachineType: Avell High Performance A60 MUV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=894cb598-7172-481c-a449-3133b8f226e5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2020 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QCCFL357.0122.2020.0911.1520 dmi.board.name: Avell High Performance dmi.board.vendor: Avell High Performance dmi.chassis.type: 10 dmi.chassis.vendor: Avell High Performance dmi.chassis.version: 1.0 dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnIntelCorp.:bvrQCCFL357.0122.2020.0911.1520:bd09/11/2020:br5.13:efr1.25:svnAvellHighPerformance:pnA60MUV:pvr:rvnAvellHighPerformance:rnAvellHighPerformance:rvr:cvnAvellHighPerformance:ct10:cvr1.0:skuA60MUV: dmi.product.family: A60 MUV dmi.product.name: A60 MUV dmi.product.sku: A60 MUV dmi.sys.vendor: Avell High Performance version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 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/gnome-shell/+bug/1970291/+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 2037011] Re: Can't create ovpn
** Changed in: network-manager-openvpn (Ubuntu) Status: Confirmed => Invalid ** No longer affects: network-manager-openvpn (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037011 Title: Can't create ovpn Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: In Progress Status in network-manager-openvpn package in Fedora: New Bug description: Settings -> Network -> Add VPN -> Import from file to import an .ovpn file does nothing after clicking Add, it just returns to the Add VPN page and no VPN connection is added. The same .ovpn file works fine in 22.04. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager-openvpn 1.10.2-3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 22:12:58 2023 InstallationDate: Installed on 2023-09-18 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037011/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Out of office][Bug 2015674] Re: Unread mail notifications do not update
Szanowny nadawco,
do 2.10.2023 przebywam na urlopie wypoczynkowym.
W bieżących sprawach proszę o kontakt z właściwymi zespołami, na
pozostałe wiadomości odpowiem po powrocie.
Pozdrawiam
Przemysław Lepiarz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2015674
Title:
Unread mail notifications do not update
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
The Thunderbird icon on the dock shows the count of new mails
correctly, but the icon does not update itself once the emails have
been read. Even restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once
the mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Finnish Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-af991e4b-f99c-455f-8b24-2a1ee2160904
bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
dmi.bios.date: 06/27/2022
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET72W(1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001AMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001AMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2015674/+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 1967593] Re: kernel modules going missing after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Desktop-packages] [Bug 1967593] Re: kernel modules going missing after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-lowlatency (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root
[Desktop-packages] [Bug 1967593] Re: kernel modules going missing after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-kvm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1967593 Title: kernel modules going missing after reboot Status in cloud-initramfs-tools package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-lowlatency package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: EDIT: There are no accurate results in the package search, but it is for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it is not kernel specific. It must be a problem with configuration, but reinstalling doesnt fix it. EDIT2: it turns out this is caused by the cloud-initramfs-copymods package mounting over modules locations. Removed it and reinstalled kernel modules package (extras didnt seem necessary, but probably prudent too). This affects several different kernels I've tried in 22.04. This post basically sums it up: https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot detailed answer: https://unix.stackexchange.com/a/499580/346155 And this one from upgrading from 20.04 to 22.04: https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade Basically, for some reason the kernel modules are being mounted over after reboot. My image was built on top of a cloud-init image, but removing the recommeded package "cloud-initramfs-copymods" that mounts over modules didnt work for me. Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules did fix my issue for this module. But how many others will not be available? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux (not installed) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: Tags: jammy uec-images Uname: Linux 5.15.0-23-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago) UserGroups: libvirt sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.release: 0.0 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2189 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 IwConfig: lono wireless extensions. enp1s0no wireless extensions. virbr0no wireless extensions. Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[Desktop-packages] [Bug 2037497]
aha, thanks! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037497]
(In reply to Adam Williamson from comment #14) > Can reporters please test downgrading packages to figure out what actually > fixes this? I'd suggest this order: > > 1. Downgrade mesa to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2274339 > 2. If that doesn't fix it, downgrade mutter and gnome-shell to > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284675 and > https://koji.fedoraproject.org/koji/buildinfo?buildID=2284676 > > if that doesn't fix it, report back and we'll try something else, I guess. :D > > Instructions for downgrading: `dnf -y install koji`, then make a scratch dir > somewhere (in your home dir or /var/tmp or something), and do `koji > download-build --arch=x86_64 --arch=noarch (buildid)` , where (buildid) is > the build ID from the URL, so 2274339 for mesa. Then do `dnf downgrade > *.rpm`. None of this worked, nor mesa-23.2.0~rc2-1.fc39. I was able to get it working again by downgrading to mesa-23.1.5-1.fc39 (build 2268808). Will try to bisect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037642] Re: [FFe] Raspberry Pi 5 support
Debdiff with squash of https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25450 Briefly tested on Pi 5, 4 and 400. Desktop comes up and glx and vulkan are accelerated. ** Patch added: "mesa_23.2.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037642/+attachment/5705304/+files/mesa_23.2.1-1ubuntu2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2013544] Re: font names displayed in an unreadable way
The lunar version shows the same so perhaps it's an issue with the font itself? ** Changed in: gnome-font-viewer (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/2013544 Title: font names displayed in an unreadable way Status in gnome-font-viewer package in Ubuntu: New Bug description: Hi, in the attached screenshot, font names in the 4th row are displayed in a vertical way that is unreadable. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-font-viewer 44.0-1 ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6 Uname: Linux 6.2.0-18-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 31 14:30:35 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/2013544/+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 2037345] Re: error saving a new vpn
*** This bug is a duplicate of bug 2037011 *** https://bugs.launchpad.net/bugs/2037011 ** This bug has been marked a duplicate of bug 2037011 Can't create ovpn -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037345 Title: error saving a new vpn Status in gnome-control-center package in Ubuntu: Confirmed Bug description: I tried adding a new openvpn. I filled in all the information, but after I click the save button, it returns me to the network settings list, but that vpn is not present. Release: 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+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 2037011] Re: Can't create ovpn
** Changed in: network-manager-openvpn (Ubuntu) Importance: Undecided => High ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2668 Importance: Unknown Status: Unknown ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2037011 Title: Can't create ovpn Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Status in network-manager-openvpn package in Ubuntu: Confirmed Status in network-manager-openvpn package in Fedora: New Bug description: Settings -> Network -> Add VPN -> Import from file to import an .ovpn file does nothing after clicking Add, it just returns to the Add VPN page and no VPN connection is added. The same .ovpn file works fine in 22.04. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: network-manager-openvpn 1.10.2-3 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 21 22:12:58 2023 InstallationDate: Installed on 2023-09-18 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230918) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/2037011/+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 2037228] Re: Firefox doesn't work after 23.10 upgrade
hum, what's the output of $ snap info firefox and why would snapd be stopped? ** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete ** Changed in: snapd (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2037633] Re: Help browser produces empty windows under nvidia drivers on X11
*** This bug is a duplicate of bug 2023322 *** https://bugs.launchpad.net/bugs/2023322 ** This bug has been marked a duplicate of bug 2023322 Unable to setup Google Online Accounts with Nvidia drivers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2037633 Title: Help browser produces empty windows under nvidia drivers on X11 Status in yelp package in Ubuntu: New Bug description: The Help browser in the dock on Mantic produces an empty window without content when launch under X11 using the nvidia-driver-535 535.104.05-0ubuntu4 video drivers. If I logout and login back in under Wayland, the Help browser behaves normally and produces the expected content in its window. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: yelp 42.2-1 ProcVersionSignature: Ubuntu 6.5.0-6.6-generic 6.5.3 Uname: Linux 6.5.0-6-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 28 05:33:27 2023 InstallationDate: Installed on 2023-09-22 (6 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230919.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: yelp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yelp/+bug/2037633/+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 2015674] Re: Unread mail notifications do not update
** Changed in: thunderbird (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2015674
Title:
Unread mail notifications do not update
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
The Thunderbird icon on the dock shows the count of new mails
correctly, but the icon does not update itself once the emails have
been read. Even restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once
the mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Finnish Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-af991e4b-f99c-455f-8b24-2a1ee2160904
bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
dmi.bios.date: 06/27/2022
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET72W(1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001AMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001AMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2015674/+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 2015674] Re: Unread mail notifications do not update
Thanks for help! I was struggling with this fantom badge numbers for
months. Now I see that it's more like Gnome problem. I agree, unread
system notifications should not influnce on badge number. In MacOS and
in Windows the application itself decides what number should be on
badge, not the OS notification system
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/2015674
Title:
Unread mail notifications do not update
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
The Thunderbird icon on the dock shows the count of new mails
correctly, but the icon does not update itself once the emails have
been read. Even restarting the app will not update the icon.
I would expect the notification icon to show zero (new emails) once
the mails have been read.
ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: thunderbird 1:102.10.0+build1-0ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
Uname: Linux 6.2.0-19-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
BuildID: 20230405152512
CasperMD5CheckResult: pass
Channel: Unavailable
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 9 12:11:34 2023
ForcedLayersAccel: False
IncompatibleExtensions:
English (GB) Language Pack - langpack-en...@thunderbird.mozilla.org
Finnish Language Pack - langpack...@thunderbird.mozilla.org
Thunderbird (default) - {972ce4c6-7e08-4474-a285-3208198ce6fd}
InstallationDate: Installed on 2022-03-22 (382 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321)
IpRoute:
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.104 metric 600
169.254.0.0/16 dev wlp3s0 scope link metric 1000
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.104 metric
600
MostRecentCrashID: bp-af991e4b-f99c-455f-8b24-2a1ee2160904
PrefErrors: Unexpected character ',' before close parenthesis @
/usr/lib/thunderbird/omni.ja:greprefs.js:306
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=102.10.0/20230405152512 (In use)
RunningIncompatibleAddons: True
SourcePackage: thunderbird
SubmittedCrashIDs:
bp-af991e4b-f99c-455f-8b24-2a1ee2160904
bp-e1f0ba3b-5182-4280-9ed6-c76da2160127
UpgradeStatus: Upgraded to lunar on 2023-04-02 (6 days ago)
dmi.bios.date: 06/27/2022
dmi.bios.release: 1.41
dmi.bios.vendor: LENOVO
dmi.bios.version: R1CET72W(1.41 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20UH001AMX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.41
dmi.modalias:
dmi:bvnLENOVO:bvrR1CET72W(1.41):bd06/27/2022:br1.41:efr1.41:svnLENOVO:pn20UH001AMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001AMX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UH_BU_Think_FM_ThinkPadT14sGen1:
dmi.product.family: ThinkPad T14s Gen 1
dmi.product.name: 20UH001AMX
dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
dmi.product.version: ThinkPad T14s Gen 1
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2015674/+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 2037698] Re: Icon theme changed after recent update
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2037698 Title: Icon theme changed after recent update Status in yaru-theme package in Ubuntu: New Bug description: Recently the software got updated and all the icons of the pre- installed apps were changed. I tried to change the icon theme using gnome-tweaks. But it is of no use. I need the icons to be like the time of my first installation of ubuntu. I have also tried to copy the theme from my friend's laptop to edit the change, But this was also of no use. Please look into it and help me to find the solution 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: ubuntu:GNOME Date: Fri Sep 29 11:58:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:8778] InstallationDate: Installed on 2022-11-01 (331 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-er0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8778 dmi.board.vendor: HP dmi.board.version: 14.14 dmi.chassis.asset.tag: 5CG0172W2M dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.14 dmi.modalias: dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-er0xxx dmi.product.sku: 3C465PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2037698/+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 2037698] Re: Icon theme changed after recent update
** Package changed: xorg (Ubuntu) => yaru-theme (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/2037698 Title: Icon theme changed after recent update Status in yaru-theme package in Ubuntu: New Bug description: Recently the software got updated and all the icons of the pre- installed apps were changed. I tried to change the icon theme using gnome-tweaks. But it is of no use. I need the icons to be like the time of my first installation of ubuntu. I have also tried to copy the theme from my friend's laptop to edit the change, But this was also of no use. Please look into it and help me to find the solution 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: ubuntu:GNOME Date: Fri Sep 29 11:58:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:8778] InstallationDate: Installed on 2022-11-01 (331 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-er0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8778 dmi.board.vendor: HP dmi.board.version: 14.14 dmi.chassis.asset.tag: 5CG0172W2M dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.14 dmi.modalias: dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-er0xxx dmi.product.sku: 3C465PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2037698/+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 2037176] Re: not able to cold boot with ARC770M
Some additional testing done: * If at cold boot I boot Windows 11 Pro first and then Linux (Debian or Ubuntu), Linux boots properly. * If at cold boot I add "nomodeset" to kernel parameters in Grub, boot process will hang as well. It's even worse with this param, because ctrl+alt+del does not reboot machine. I believe it must be related to either firmware loading, i915 module or both. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/2037176 Title: not able to cold boot with ARC770M Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I am able to boot with kernel 6.5.x after install however after POWER OFF, Restart It hangs during boot and it does not start the graphical server. George Nistor ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xserver-xorg-video-intel 2:2.99.917+git20210115-1 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: ubuntu:GNOME Date: Sat Sep 23 19:07:47 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3026] Intel Corporation Device [8086:5690] (rev 08) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:3026] InstallationDate: Installed on 2023-09-21 (2 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Intel(R) Client Systems NUC12SNKi72 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-6.2.0-33-generic root=UUID=5663b3c3-49bb-4a93-b8fc-399746cb1397 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-intel UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2023 dmi.bios.release: 0.58 dmi.bios.vendor: Intel Corp. dmi.bios.version: SNADL357.0058.2023.0711.1531 dmi.board.name: NUC12SNKi72 dmi.board.vendor: Intel Corporation dmi.board.version: M45201-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnIntelCorp.:bvrSNADL357.0058.2023.0711.1531:bd07/11/2023:br0.58:efr1.17:svnIntel(R)ClientSystems:pnNUC12SNKi72:pvrM82271-502:rvnIntelCorporation:rnNUC12SNKi72:rvrM45201-502:cvnIntelCorporation:ct35:cvr2.0:skuRNUC12SNKi7200: dmi.product.family: SN dmi.product.name: NUC12SNKi72 dmi.product.sku: RNUC12SNKi7200 dmi.product.version: M82271-502 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/2037176/+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 2037696] Re: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common
** Tags removed: need-duplicate-check -- 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/2037696 Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice- common Status in libreoffice package in Ubuntu: New Bug description: I wanted to upgrade the ubuntu. But these bugs are coming on update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 25 00:08:48 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2023-08-21 (35 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: Upgraded to focal on 2023-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037696/+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 2037696] [NEW] package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common
Public bug reported: I wanted to upgrade the ubuntu. But these bugs are coming on update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 25 00:08:48 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2023-08-21 (35 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: Upgraded to focal on 2023-09-24 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- 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/2037696 Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice- common Status in libreoffice package in Ubuntu: New Bug description: I wanted to upgrade the ubuntu. But these bugs are coming on update. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 5.4.0-163.180-generic 5.4.246 Uname: Linux 5.4.0-163-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Sep 25 00:08:48 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2023-08-21 (35 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: Upgraded to focal on 2023-09-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2037696/+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 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: libcamera (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-meta-raspi (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: pipewire (Ubuntu) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037697] [NEW] Xorg freeze when browsing the web
Public bug reported: While using my computer, the screen suddenly goes black with a blinking cursor. It is the 2nd or 3rd time, this time when browsing with Firefox 108.0 (it was at the end of a youtube video), no other apps loaded. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.113.01 Tue Sep 12 19:41:24 UTC 2023 GCC version: ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 07:00:09 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Aspire E5-575G [1025:1094] Subsystem: Acer Incorporated [ALI] GM107M [GeForce GTX 950M] [1025:1094] InstallationDate: Installed on 2023-09-19 (9 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b573 Chicony Electronics Co., Ltd HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Qualcomm Atheros QCA9377 Bluetooth Bus 001 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-575G ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7a808742-50c6-42f2-9ff3-d1faeb2d8470 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2017 dmi.bios.release: 0.0 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.32 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: Acer dmi.board.version: V1.32 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 2.30 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.32:bd10/24/2017:br0.0:efr2.30:svnAcer:pnAspireE5-575G:pvrV1.32:rvnAcer:rnIronman_SK:rvrV1.32:cvnChassisManufacturer:ct10:cvrChassisVersion:skuAspireE5-575G_115F_1.32: dmi.product.family: KBL dmi.product.name: Aspire E5-575G dmi.product.sku: Aspire E5-575G_115F_1.32 dmi.product.version: V1.32 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug freeze lunar 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/2037697 Title: Xorg freeze when browsing the web Status in xorg package in Ubuntu: New Bug description: While using my computer, the screen suddenly goes black with a blinking cursor. It is the 2nd or 3rd time, this time when browsing with Firefox 108.0 (it was at the end of a youtube video), no other apps loaded. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: ""
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
** Patch added: "filechooser_42.1_patch.diff" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+attachment/5705189/+files/filechooser_42.1_patch.diff -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1879137] Re: The snap-store is using hundreds of MiBs of RAM.
On my Ubuntu 23.04 the snap-store uses ~26GB!!! of RAM in 7 days of uptime. o_0 > ps -p 6720 -o %cpu,%mem,cmd %CPU %MEM CMD 0.0 39.6 /snap/snap-store/959/usr/bin/snap-store --gapplication-service > top -n 1 -p 6720 top - 00:54:56 up 7 days, 20:34, 2 users, load average: 1.83, 2.31, 2.60 Tasks: 1 total, 0 running, 1 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 0.0 sy, 0.0 ni,100.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 64004.4 total, 19553.1 free, 42037.0 used, 6194.6 buff/cache MiB Swap: 1952.0 total, 0.0 free, 1952.0 used. 21967.4 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 6720 taurus20 0 27.1g 24.8g 5604 S 0.0 39.6 4:39.30 snap-store Happy to help tracing it! How? P.S. It could be the separate issue... ** Attachment added: "Screenshot from 2023-09-29 00-57-05.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1879137/+attachment/5705240/+files/Screenshot%20from%202023-09-29%2000-57-05.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1879137 Title: The snap-store is using hundreds of MiBs of RAM. Status in GNOME Software: New Status in snap-store-desktop: Confirmed Status in gnome-software package in Ubuntu: Confirmed Bug description: The snap-store process is intermittently using hundreds of megabytes of RAM. Is this normal? Is there a solution? Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1879137/+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 1971168] Re: [snap] Files on local network shares are not opened / written
The attachment "filechooser_42.1_patch.diff" 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 xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1971168] Re: [snap] Files on local network shares are not opened / written
For those who are interested. I modified the patch from Sergio Costas Rodriguez to version 42.1 which is shipped with Ubuntu 22.04 It works on my laptop :-) ** Patch added: "filechooser_42.1_patch.diff" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+attachment/5705190/+files/filechooser_42.1_patch.diff ** Patch removed: "filechooser_42.1_patch.diff" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1971168/+attachment/5705189/+files/filechooser_42.1_patch.diff -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Status in xdg-desktop-portal-gnome package in Ubuntu: Fix Released Status in xdg-desktop-portal-gnome source package in Jammy: Triaged Status in xdg-desktop-portal-gnome source package in Lunar: Triaged Bug description: [ Impact ] When the user is running a containerized application (like the snapped Firefox or Chromium), and tries to save a document, the xdg-desktop- portal-gnome backend does show remote drives (like SMB or SFTP ones), and allows to choose them, but then the save operation fails. The previous backend, xdg-desktop-portal-gtk, did work fine in these cases, because it returned the local path that corresponded to the local file exported by Gvfs using FUSE, so this behaviour is not only a serious bug, but also a regression. [ Test plan] Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown [ Where problems could occur ] - If the remote drives aren't exported as local files by Gvfs using FUSE, the patch won't work and the behaviour will be the same than now. - Any hidden bug in g_file_get_path() when managing remote drives could be triggered by this patch. [ Additional information ] * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 2013236] Re: b43 driver conflicts with bcmwl driver for some Broadcom devices
I think the fix is https://github.com/tseliot/ubuntu-drivers- common/pull/90/files -- 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/2013236 Title: b43 driver conflicts with bcmwl driver for some Broadcom devices Status in broadcom-sta package in Ubuntu: New Status in linux-firmware package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Triaged Status in broadcom-sta source package in Lunar: New Status in linux-firmware source package in Lunar: Invalid Status in ubuntu-drivers-common source package in Lunar: Incomplete Status in broadcom-sta source package in Mantic: New Status in linux-firmware source package in Mantic: Invalid Status in ubuntu-drivers-common source package in Mantic: Triaged Bug description: Specifically for Lunar - using a Macbook Air 2012, its wireless driver was not enabled even though I ticked the wireless tickbox on the installer. A quick look at the installer logs reveals various issues syslog:2023-03-29T18:01:25.141599+00:00 ubuntu-budgie kernel: [ 43.063747] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141625+00:00 ubuntu-budgie kernel: [ 43.063802] b43 bcma0:1: Direct firmware load for b43/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063862] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 syslog:2023-03-29T18:01:25.141626+00:00 ubuntu-budgie kernel: [ 43.063908] b43 bcma0:1: Direct firmware load for b43-open/ucode29_mimo.fw failed with error -2 I will attach the installer logs manually since this was captured after the installation Note - on 20.04.6, 22.04.2 and 22.10 with the same laptop bcmwl was installed correctly during the install so this is a regression with the 6.2 kernel Workaround -- You'll first need to blacklist the b43 driver by adding a blacklist file to /etc/modprobe.d/b43.conf with the contents "blacklist b43". Then run "update-initramfs -u". Then install the bcmwl-kernel-source package. After a reboot your wireless device should be available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/2013236/+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 2000422] Re: Cannot save Libre docs directly to external usb nor additional SSD
** Tags added: snap -- 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/2000422 Title: Cannot save Libre docs directly to external usb nor additional SSD Status in libreoffice package in Ubuntu: New Bug description: I can save a libre doc to my desktop for example. I do see in my Ubuntu "files and or Dics" app both the USB external drive and the additional SSD added post purchase, but libre does not see those memory places when I attempt a "save as". Libre only sees that which would be called something akin to the C drive. I am able to copy files from the "C" drive on to my external USB or new SSD. My Ubuntu is 20.04.5 LTS I am running this on a new Dell Workstation 7760 that came with Ubuntu loaded. I get all of my software from the Ubuntu software store. I am using the Office Suite of Libre (libreoffice canonical version 7.4.3.2), not the individually loaded components. I did check the permissions to allow data to be stored on an external drive. I hope to get the "save as" function to work correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2000422/+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 2037698] [NEW] Icon theme changed after recent update
You have been subscribed to a public bug: Recently the software got updated and all the icons of the pre-installed apps were changed. I tried to change the icon theme using gnome-tweaks. But it is of no use. I need the icons to be like the time of my first installation of ubuntu. I have also tried to copy the theme from my friend's laptop to edit the change, But this was also of no use. Please look into it and help me to find the solution 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: ubuntu:GNOME Date: Fri Sep 29 11:58:30 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Iris Plus Graphics G1 (Ice Lake) [8086:8a56] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Iris Plus Graphics G1 (Ice Lake) [103c:8778] InstallationDate: Installed on 2022-11-01 (331 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 05c8:03d2 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP TrueVision HD Camera Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 14s-er0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=7facb30b-d308-4a9f-876f-f235cfa36a6a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2021 dmi.bios.release: 15.14 dmi.bios.vendor: AMI dmi.bios.version: F.14 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8778 dmi.board.vendor: HP dmi.board.version: 14.14 dmi.chassis.asset.tag: 5CG0172W2M dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 14.14 dmi.modalias: dmi:bvnAMI:bvrF.14:bd02/02/2021:br15.14:efr14.14:svnHP:pnHPLaptop14s-er0xxx:pvr:rvnHP:rn8778:rvr14.14:cvnHP:ct10:cvrChassisVersion:sku3C465PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 14s-er0xxx dmi.product.sku: 3C465PA#ACJ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.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-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 ubuntu wayland-session -- Icon theme changed after recent update https://bugs.launchpad.net/bugs/2037698 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg 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 2034276] Re: [FFE] Update gjs to 1.78.0 and switch mozjs102 to mozjs115
This bug was fixed in the package gjs - 1.78.0-0ubuntu1 --- gjs (1.78.0-0ubuntu1) mantic; urgency=medium * New upstream release * Switch from mozjs102 to 115 (LP: #2034276) * Drop all patches: applied in new release * debian/libgjs0g.symbols: Add new symbol -- Jeremy Bícha Tue, 26 Sep 2023 13:21:46 -0400 ** Changed in: gjs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2034276 Title: [FFE] Update gjs to 1.78.0 and switch mozjs102 to mozjs115 Status in gjs package in Ubuntu: Fix Released Bug description: Explanation of FeatureFreeze exception === gjs 1.78.0 is part of GNOME 45. gjs 1.78 switches from mozjs102 to mozjs115. mozjs is the SpiderMonkey JavaScript engine from Firefox (ESR). The Firefox 102 ESR branch is no longer supported by Mozilla later this month; 115 is the new Firefox ESR series. We did not finish packaging mozjs115 before Mantic Feature Freeze. This feature freeze request includes promoting mozjs115 from universe to main and demoting mozjs102 to universe. The only other user of mozjs* in Mantic is cjs, Cinnamon's fork of gjs. Cinnamon will not be ready to switch to mozjs115 in time for Ubuntu 23.10. As a minor note, we will also need to add mozjs115 to the list of packages to build on i386. Upstream changes https://gitlab.gnome.org/GNOME/gjs/-/blob/1.78.0/NEWS Changelog entries since current mantic version 1.76.2-4: gjs (1.78.0-0ubuntu1) mantic; urgency=medium * New upstream release * Switch from mozjs102 to 115 (LP: #2034276) * Drop all patches: applied in new release * debian/libgjs0g.symbols: Add new symbol -- Jeremy Bícha Tue, 26 Sep 2023 13:48:35 -0400 Testing Done Successful builds for 1.77.90: https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/ppa/+packages autopkgtest: https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-ubuntu-desktop-ppa/mantic/amd64/g/gjs/20230905_185208_5e448@/log.gz I have successfully completed the manual test case at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2034276/+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 2034986] Re: some text became unreadable during a distribution upgrade
On 2023-09-26 22:32, Gunnar Hjalmarsson wrote: > But one of the changes in mantic is that no font is safely present > (i.e. the default ones are "Recommends:" only). So later, when people > will upgrade from 23.10 to 24.04, just using "Sans" temporarily may > not be the best option. And changing it to a specific font family is > tricky, since we don't know if the user has uninstalled some of the > default font packages. > > So my thought is: Can this be a reason to let desktop-common depend > on, and not only recommend, some font package after all? And if so, > which package would be suitable for the purpose? To make it easier to keep 'the temporary font' approach in 24.04 — if that is what we want by then — I added a hard dependency on fonts- dejavu-core to desktop-common. No upstream changes to the DejaVu fonts have been made the last 6 years, so it's more or less unmaintained, which in this context is an advantage. ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Confirmed => In Progress ** Changed in: ubuntu-meta (Ubuntu Mantic) Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2034986 Title: some text became unreadable during a distribution upgrade Status in ubuntu-meta package in Ubuntu: In Progress Status in ubuntu-release-upgrader package in Ubuntu: In Progress Status in ubuntu-meta source package in Mantic: In Progress Status in ubuntu-release-upgrader source package in Mantic: In Progress Bug description: I was upgrading from Lunar to Mantic the other day and left a couple of applications open during the upgrade process. During the upgrade the text in audacious became unreadable (I'll attach a screenshot) and I seem to recall the title bar of Firefox being unreadable but the contents of web pages still being readable. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.5 ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0 Uname: Linux 6.5.0-4-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Sep 8 15:39:27 2023 InstallationDate: Installed on 2018-08-10 (1855 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago) VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', '/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 126: Error executing command as another user: Request dismissed VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.meta-release: 2021-05-27T16:30:16.970490 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2034986/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
We could create an /etc/apport/report-ignore/ file with the contents '/usr/bin/gnome-shell' so then at least the crash report dialog would not appear. However, after choosing try Ubuntu you presented with a black screen and some console output so its still not a great experience. ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Milestone: None => ubuntu-23.10 -- 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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in apport package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Incomplete Status in ubiquity package in Ubuntu: New Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2036440/+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 2036651] Re: gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from guess_category_value() from __dcigettext()
** Information type changed from Private to Public
--
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/2036651
Title:
gnome-shell crashed with SIGSEGV in __GI_getenv("LANGUAGE") from
guess_category_value() from __dcigettext()
Status in gnome-shell package in Ubuntu:
Confirmed
Bug description:
Crash on startup
ProblemType: Crash
DistroRelease: Ubuntu 23.10
Package: gnome-shell 45.0-1ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME-Greeter:GNOME
Date: Tue Sep 19 22:38:53 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
InstallationDate: Installed on 2023-09-12 (7 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/false
XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 45.0-1ubuntu1
SegvAnalysis:
Segfault happened at: 0x7f706ee45e6d <__GI_getenv+77>: cmp
(%rbx),%r12b
PC (0x7f706ee45e6d) ok
source "(%rbx)" (0x55fd90525) not located in a known VMA region (needed
readable region)!
destination "%r12b" ok
Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
__GI_getenv (name=name@entry=0x7f706efc0257 "LANGUAGE") at
./stdlib/getenv.c:31
guess_category_value (categoryname=0x7f706efa5493 <_nl_category_names+51>
"LC_MESSAGES", category=5) at ./intl/dcigettext.c:1569
__dcigettext (domainname=0x7f706f79e126 "glib20", msgid1=0x7f706f985c68 "The
sockets address family to use for socket construction", msgid2=0x0, plural=0,
n=0, category=5) at ./intl/dcigettext.c:647
?? () from /lib/x86_64-linux-gnu/libgio-2.0.so.0
g_type_class_ref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: gnome-shell crashed with SIGSEGV in __GI_getenv()
UpgradeStatus: Upgraded to mantic on 2023-09-18 (1 days ago)
UserGroups: N/A
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036651/+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 2037228] Re: Firefox doesn't work after 23.10 upgrade
apt-get install firefox --reinstall should run debian/firefox.preinst which is responsible for installing the snap. The preinstall script depends on /run/snapd.socket existing. So when the snapd service is stopped the snap will not be installed. Would it be preferable to let debian/firefox.preinst return an error if the socket does not exist? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2036817] Re: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->()
** Changed in: libreoffice (Ubuntu) Status: Confirmed => Fix Released -- 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/2036817 Title: soffice.bin crashed with SIGSEGV in com::sun::star::uno::Reference::operator->() Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Released Bug description: Occurred when exiting Calc/ ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: libreoffice-core 4:7.6.1~rc2-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 20 13:44:57 2023 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2023-09-17 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230908.2) ProcAttrCurrent: libreoffice-soffice (complain) ProcCmdline: /usr/lib/libreoffice/program/soffice.bin --calc file:///home/username/Documents/Comic%20Book%20Collection.ods --splash-pipe=5 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f4aee4abf8e:mov(%rax,%rbp,1),%rdi PC (0x7f4aee4abf8e) ok source "(%rax,%rbp,1)" (0x558d207ac2b2) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: libreoffice StacktraceTop: ?? () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing(unsigned int, com::sun::star::uno::Reference const&) () from /usr/lib/libreoffice/program/libmergedlo.so comphelper::OAccessibleContextWrapper::disposing() () from /usr/lib/libreoffice/program/libmergedlo.so cppu::WeakComponentImplHelperBase::dispose() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 cppu::WeakComponentImplHelperBase::release() () from /usr/lib/libreoffice/program/libuno_cppuhelpergcc3.so.3 Title: soffice.bin crashed with SIGSEGV in comphelper::AccessibleEventNotifier::revokeClientNotifyDisposing() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/2036817/+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 2037228] Re: Firefox doesn't work after 23.10 upgrade
Submitter says snapped firefox is installed but snapped firefox binary isn't found, probably needs more triaging ** Package changed: ubuntu-release-upgrader (Ubuntu) => snapd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2037228] Re: Firefox doesn't work after 23.10 upgrade
What does ls -l /snap/bin/firefox tell you? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037228 Title: Firefox doesn't work after 23.10 upgrade Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Firefox doesn’t work after upgrading from 23.04 to 23.10 beta. The Firefox icon disappeared from my sidebar during the upgrade process. 'snap list' shows firefox stable is installed, trying to run the command firefox says: Command '/usr/bin/firefox' requires the firefox snap to be installed. Please install it with: snap install firefox $ lsb_release -rd No LSB modules are available. Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 $ apt-cache policy firefox firefox: Installed: 1:1snap1-0ubuntu3 Candidate: 1:1snap1-0ubuntu3 Version table: *** 1:1snap1-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037228/+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 2037527] Re: [Ffe] libwebp
Hello, it is needed for new libavif, as explained in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001 Having the new version will make easier to build it with finally the sharpyuv functionality. That said, will be anyway autosync next time we open, so there should be plenty of time to fix it properly before 24.04. My idea was to ship in 23.10 to let users broadly test before next LTS. Not a big deal, I'll close this bug and let it sync for NANIMAL ** Bug watch added: Debian Bug tracker #1022001 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001 ** Changed in: libwebp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: Invalid Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) Changes since mantic version 1.2.4-0.3 == libwebp (1.3.2-0.3) unstable; urgency=medium * Non-maintainer upload. * Fix invalid incremental decoding check. (Closes: #1052447) * Fix next is invalid pointer when WebPSafeMalloc fails * Fix static analyzer warnings. -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 libwebp (1.3.2-0.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 libwebp (1.3.2-0.1) unstable; urgency=medium * Non-maintainer upload. * Upload to unstable. -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 libwebp (1.3.2-0.1~exp2) experimental; urgency=medium * Non-maintainer upload. [ Gianfranco Costamagna ] * Also install .a files again. * Make sure we have built and installed anim_dump and anim_diff. (Closes: #1023482) -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 libwebp (1.3.2-0.1~exp1) experimental; urgency=medium * Non-maintainer upload. * New upstream release 1.3.2. + The 1.3.x branch introduces libsharpyuv, which will be introduced as separate Debian binary packages. (Closes: #1040970) + CVE-2023-4863 is handled in this release. (LP: #2035220) * debian/gbp.conf: Use ignore-branch=True to avoid limitation on experimental branch. * debian/control: + Drop unnecessary build-dependency on autotools-related packages. + Add build-dependency on pkg-config. + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + Apply RPATH-related hotfix before debhelper compat level 14. + Add new binary packages: libsharpyuv-dev, libsharpyuv0, libwebpdecoder3. * debian/libwebp-dev.install: Do not install static library anymore since CMake is not building them by default. * debian/rules: + Enforce --buildsystem=cmake. + Drop explicit option --enable-aligned, this option has been removed by libwebp upstream (see upstream ChangeLog). * debian/docs: Rename to libwebp-dev.docs to avoid confusion. * debian/patches: Drop all old patches, merged upstream. * debian/patches/: + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: Add patch to install CMake Config files to architecture-dependent location instead to retain Multi-Arch property of dev packages. * debian/copyright: Completely rewritten in machine-readable copyright format. -- Boyuan Yang Thu, 14 Sep 2023 22:22:30
[Desktop-packages] [Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Are any of the reports at https://errors.ubuntu.com/user/ID from gnome- shell? That's the important one if the screen has frozen but the cursor keeps moving. -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 2037425] Re: ubuntu-server pulls in ZFS userspace
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
seed MP merged, dput of ubuntu-meta done. ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037425] Re: ubuntu-server pulls in ZFS userspace
This bug was fixed in the package ubuntu-meta - 1.522 --- ubuntu-meta (1.522) mantic; urgency=medium * Refreshed dependencies * Removed zfs-initramfs from server [amd64 arm64 ppc64el riscv64 s390x], server-raspi [amd64 arm64 ppc64el riscv64 s390x] (LP: #2037425) * Removed zfsutils-linux from server, server-raspi -- Dan Bungert Thu, 28 Sep 2023 10:32:46 -0600 ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2037425 Title: ubuntu-server pulls in ZFS userspace Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Released Bug description: ubuntu-server in Mantic pulls in zfs userspace packages and systemd services are automatically enabled, which means zfs kernel modules are automatically loaded at boot, for everybody. On Raspberry Pi, this results in +5MB of additional memory consumption which is not acceptable, especially not on 512MB devices. Culprit: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=36c17dbdbfd13f1b386aa86d065a8a9d34c48a35 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2037425/+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 2037577] Re: [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2037577 Title: [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect Status in gnome-shell package in Ubuntu: Confirmed Bug description: When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is modified, the GNOME Shell theme remains in the default state, i.e. it switches between light and dark together with the ‘Dark Style’ toggle. It is impossible to set the Shell theme to be unconditionally dark or light. To reproduce: 1. Run command gsettings set org.gnome.shell.ubuntu color-scheme 'prefer-dark' or modify the parameter color-scheme in /org/gnome/shell/ubuntu/ to be equal 'prefer-dark' via the Dconf Editor GUI. 2. Make sure that the ‘Dark Style’ toggle is deactivated in the quick settings. What should happen: The Shell dialogs like the quick settings menu and the calendar-and-notifications menu should be rendered in dark style. What happens instead: The Shell dialogs are still light. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 20:04:08 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-21 (371 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037577/+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 2037642] Re: [FFe] Raspberry Pi 5 support
FFe for linux-firmware-raspi in LP: #2037634 FFe for gpiozero in LP: #2037637 ** No longer affects: linux-firmware-raspi (Ubuntu) ** Changed in: libcamera (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux-meta-raspi (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Triaged ** Changed in: mesa (Ubuntu) Status: Confirmed => Triaged ** Changed in: pipewire (Ubuntu) Status: Confirmed => Triaged ** Changed in: rpi-eeprom (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-settings (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037642] Re: [FFe] Raspberry Pi 5 support
** Tags added: mantic raspi raspigfx ** Tags removed: raspigfx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037642] Re: [FFe] Raspberry Pi 5 support
FFe granted for the remaining packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Triaged Status in linux-raspi package in Ubuntu: Triaged Status in mesa package in Ubuntu: Triaged Status in pipewire package in Ubuntu: Triaged Status in rpi-eeprom package in Ubuntu: Triaged Status in ubuntu-settings package in Ubuntu: Triaged Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037655] Re: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs
Actual Mantic logs: journalctl -b | grep DENIED kernel: audit: type=1400 audit(1695910314.967:110): apparmor="DENIED" operation="connect" class="file" profile="/usr/sbin/cups-browsed" name="/run/systemd/resolve/io.systemd.Resolve" pid=1338 comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=132 ouid=101 kernel: audit: type=1400 audit(1695910314.987:111): apparmor="DENIED" operation="connect" class="file" profile="/usr/sbin/cups-browsed" name="/run/systemd/resolve/io.systemd.Resolve" pid=1338 comm="cups-browsed" requested_mask="wr" denied_mask="wr" fsuid=132 ouid=101 kernel: audit: type=1400 audit(1695910472.859:112): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=4268 comm="snap-confine" capability=12 capname="net_admin" kernel: audit: type=1400 audit(1695910472.859:113): apparmor="DENIED" operation="capable" class="cap" profile="/usr/lib/snapd/snap-confine" pid=4268 comm="snap-confine" capability=38 capname="perfmon" kernel: audit: type=1400 audit(1695910473.231:114): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=4284 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 kernel: audit: type=1400 audit(1695910473.235:115): apparmor="DENIED" operation="open" class="file" profile="snap-update-ns.firefox" name="/var/lib/" pid=4284 comm="5" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 kernel: audit: type=1400 audit(1695910475.843:116): apparmor="DENIED" operation="mknod" class="file" profile="snap.firefox.firefox" name="/etc/igfx_user_feature.txt" pid=4405 comm="vaapitest" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 kernel: audit: type=1400 audit(1695910475.843:117): apparmor="DENIED" operation="mknod" class="file" profile="snap.firefox.firefox" name="/etc/igfx_user_feature_next.txt" pid=4405 comm="vaapitest" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000 ** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037655 Title: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037655/+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 2037655] Re: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037655 Title: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037655/+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 2037655] Re: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2037655 Title: dbuss apparmor="DENIED" interface="org.gnome.Mutter.IdleMonitor" spamming logs Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: On the latest 23.10 Mantic beta using firefox 118.0 spams the log with message: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/gnome/Mutter/IdleMonitor/Core" interface="org.gnome.Mutter.IdleMonitor" member="GetIdletime" mask="send" name=":1.34" pid=6444 label="snap.firefox.firefox" peer_pid=3234 peer_label="unconfined" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2037655/+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 2037691] [NEW] Audio output stopped working
Public bug reported: Audio output was working fine when i installed ubuntu 1.5 years ago. Approximately a year ago it stopped working, might be because i updated to linux 22.04 then, now i have updated to 23.04 and the issue remains. I tried reinstalling drivers, but nothing helps ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: telemak1863 F wireplumber /dev/snd/controlC0: telemak1863 F wireplumber /dev/snd/seq:telemak1856 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 03:38:05 2023 InstallationDate: Installed on 2022-04-28 (518 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-09-27 (1 days ago) dmi.bios.date: 04/08/2022 dmi.bios.release: 2.10 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NBM-WXX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnHUAWEI:bvr2.10:bd04/08/2022:br2.10:efr2.10:svnHUAWEI:pnNBM-WXX9:pvrM1020:rvnHUAWEI:rnNBM-WXX9-PCB-B2:rvrM1020:cvnHUAWEI:ct10:cvrM1020:skuC171: dmi.product.family: MateBook D dmi.product.name: NBM-WXX9 dmi.product.sku: C171 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar third-party-packages wayland-session -- 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/2037691 Title: Audio output stopped working Status in pulseaudio package in Ubuntu: New Bug description: Audio output was working fine when i installed ubuntu 1.5 years ago. Approximately a year ago it stopped working, might be because i updated to linux 22.04 then, now i have updated to 23.04 and the issue remains. I tried reinstalling drivers, but nothing helps ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pulseaudio 1:16.1+dfsg1-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: telemak1863 F wireplumber /dev/snd/controlC0: telemak1863 F wireplumber /dev/snd/seq:telemak1856 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 29 03:38:05 2023 InstallationDate: Installed on 2022-04-28 (518 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to lunar on 2023-09-27 (1 days ago) dmi.bios.date: 04/08/2022 dmi.bios.release: 2.10 dmi.bios.vendor: HUAWEI dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: NBM-WXX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 2.10 dmi.modalias: dmi:bvnHUAWEI:bvr2.10:bd04/08/2022:br2.10:efr2.10:svnHUAWEI:pnNBM-WXX9:pvrM1020:rvnHUAWEI:rnNBM-WXX9-PCB-B2:rvrM1020:cvnHUAWEI:ct10:cvrM1020:skuC171: dmi.product.family: MateBook D dmi.product.name: NBM-WXX9 dmi.product.sku: C171 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2037691/+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 2037695] [NEW] Backport packages to server-backports PPA from lunar
Public bug reported: Backport the following packages to the server-backports PPA from lunar: * dpdk * edk2 * libslirp * libvirt * libvirt-python * openvswitch * qemu * rdma-core * seabios * spice * spice-protocol * spice-vdagent * virglrenderer * virt-manager The following build dependencies for the above will also require backporting: * meson ** Affects: dpdk (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: In Progress ** Affects: edk2 (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: libslirp (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: libvirt (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: libvirt-python (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: meson (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: openvswitch (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: In Progress ** Affects: qemu (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: rdma-core (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: seabios (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: spice (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: spice-protocol (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: spice-vdagent (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: virglrenderer (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Affects: virt-manager (Ubuntu) Importance: Wishlist Assignee: Bryce Harrington (bryce) Status: Fix Committed ** Tags: needs-ppa-backport ** Changed in: dpdk (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: edk2 (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: libslirp (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: libvirt (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: libvirt-python (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: meson (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: openvswitch (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: qemu (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: rdma-core (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: seabios (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: spice (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: spice-protocol (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: spice-vdagent (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: virglrenderer (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: virt-manager (Ubuntu) Milestone: None => ubuntu-23.05 ** Changed in: dpdk (Ubuntu) Importance: Undecided => High ** Changed in: dpdk (Ubuntu) Status: New => In Progress ** Changed in: dpdk (Ubuntu) Milestone: ubuntu-23.05 => ubuntu-23.10 ** Changed in: dpdk (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: edk2 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: edk2 (Ubuntu) Status: New => Fix Committed ** Changed in: edk2 (Ubuntu) Milestone: ubuntu-23.05 => ubuntu-23.10 ** Changed in: edk2 (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libslirp (Ubuntu) Importance: Undecided => Wishlist ** Changed in: libslirp (Ubuntu) Status: New => Fix Committed ** Changed in: libslirp (Ubuntu) Milestone: ubuntu-23.05 => ubuntu-23.10 ** Changed in: libslirp (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt (Ubuntu) Importance: Undecided => Low ** Changed in: libvirt (Ubuntu) Status: New => Fix Committed ** Changed in: libvirt (Ubuntu) Milestone: ubuntu-23.05 => ubuntu-23.10 ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: libvirt-python (Ubuntu) Importance: Undecided => Wishlist ** Changed in: libvirt-python (Ubuntu) Status: New => Fix Committed ** Changed in: libvirt-python (Ubuntu) Milestone: ubuntu-23.05 => ubuntu-23.10 ** Changed in: libvirt-python (Ubuntu) Assignee: (unassigned) => Bryce Harrington (bryce) ** Changed in: meson (Ubuntu) Importance:
[Desktop-packages] [Bug 1922340] Re: GNOME lock screen wallpaper turns black on main display
*** This bug is a duplicate of bug 2013042 *** https://bugs.launchpad.net/bugs/2013042 ** This bug has been marked a duplicate of bug 2013042 Lock screen wallpaper vanishes (goes black) if a second monitor is plugged in/out -- 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/1922340 Title: GNOME lock screen wallpaper turns black on main display Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Won't Fix Bug description: 1) Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 2) gnome-shell: Installed: 3.38.4-1ubuntu1 Candidate: 3.38.4-1ubuntu1 Version table: *** 3.38.4-1ubuntu1 500 500 http://pl.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3) This bug only appears on Gnome with Wayland. It does not affect Gnome on xorg. After the screen stays off and locked for some time the wallpaper on the main display turns black. It never happens on the secondary display. The issue is also reported, here on gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3206 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 11:50:15 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-04-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922340/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
@Rico: I left CVE-2023-5174 and CVE-2023-5168 out on purpose because according to Mozilla these two vulnerabilities only affect Windows users. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+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 2029913] Re: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL)
The 115 update is being worked on, unfortunately it requires a newer nodejs than the version currently available in 22.04 to build (12.22.12 vs 12.22.9). We will need to figure out if we can revert that requirement somehow or if updating nodejs as a stable update is doable... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/2029913 Title: [SRU request] Update Thunderbird to 115.x (as 102.x is EOL) Status in thunderbird package in Ubuntu: Confirmed Bug description: [ Impact ] * The Thunderbird 102.x series has its final release (12.15.0) planned for release on August 30th. After that, the 102.x series will no longer receive critical security updates. Due to the size and complexity of the Mozilla/Thunderbird codebase, it is extremely unlikely that the Ubuntu team could take on the task of backporting patches to new security issues once official support for the 102.x series has ended. * Updating to Thunderbird 115.x in all currently-supported Ubuntu releases will make sure users stay secure. * It should be noted that 115.x does make changes to the interface. While all these changes are ostensibly for the better, normally this level of change would disqualify an application from getting SRUed. However, running an EOL email client is a security/privacy risk to users that can't be ignored. * Official post detailing the interface changes: https://www.thunderbird.net/en-US/thunderbird/115.0/whatsnew/ * Official changelog for 115.0 release: https://www.thunderbird.net/en-US/thunderbird/115.0/releasenotes/ * Official changelog for 115.1 bugfix release: https://www.thunderbird.net/en-US/thunderbird/115.1.0/releasenotes/ [ Test Plan ] Not sure, I'm just a user [ Where problems could occur ] * New major release, usual concerns apply [ Other Info ] * I'm guessing that this SRU was already planned to happen eventually, but since I couldn't find an official request, here we are To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/2029913/+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
