[Bug 2038492] Re: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
** This bug is no longer a duplicate of bug 2037214 evict_inodes inode xxx, i_count = 1, was skipped! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2038492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1996243] Re: /bin/sh is set to dash, and dpkg-reconfigure doesn't change it
>> The change surprised others, but... Sorry, I clearly missed your comment. To be fair I wouldn't have thought this was a dash issue. Whether you want dash or bash isn't an issue for either dash or bash, but rather for sh. Perhaps a separate bash-or-dash package is needed which just installs the relevant alternatives files? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1996243 Title: /bin/sh is set to dash, and dpkg-reconfigure doesn't change it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dash/+bug/1996243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2038492] Re: workqueue: inode_switch_wbs_work_fn hogged CPU for >10000us 16 times, consider switching to WQ_UNBOUND
*** This bug is a duplicate of bug 2037214 *** https://bugs.launchpad.net/bugs/2037214 The duplicate status is *clearly wrong*, as #2037214 refers to the "evict_inodes" issue (now fixed at some point) whereas this bug report is, according to its title, about the "workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 4" issue. This has not been fixed (I'm seeing it on 6.8.0-31-generic in Noble). There are solutions posted for it. See: https://lkml.org/lkml/2023/8/30/613 https://gitlab.freedesktop.org/drm/intel/-/issues/9245 https://lore.kernel.org/stable/20230@intel.com/T/ which I picked up via: https://ubuntuforums.org/showthread.php?t=2490640 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #9245 https://gitlab.freedesktop.org/drm/intel/-/issues/9245 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2038492 Title: workqueue: inode_switch_wbs_work_fn hogged CPU for >1us 16 times, consider switching to WQ_UNBOUND To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.5/+bug/2038492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066534] Re: kernel segfault reported on inserting any USB device
This is on 24.04 (Noble). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066534 Title: kernel segfault reported on inserting any USB device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2066534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066534] Re: kernel segfault reported on inserting any USB device
apport-bug linux does work, though. So I've re-submitted this as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066537 and will close this one. ** Changed in: linux-meta (Ubuntu) Status: New => Incomplete ** Changed in: linux-meta (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066534 Title: kernel segfault reported on inserting any USB device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2066534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066534] [NEW] kernel segfault reported on inserting any USB device
Public bug reported: Everytime a new device is found on the USB bus a message like this is reported in dmesg and syslog. 2024-05-22T22:50:05.835993+01:00 gmllaptop kernel: w[4942]: segfault at 4c ip 5e15d21dce73 sp 7fff3a087a20 error 4 in w[5e15d21dc000+3000] likely on CPU 2 (core 2, socket 0) It doesn't appear to cause a problem, but then I don't know what it is trying to do when it segfaults. NOTE: Using the ubuntu-bug -p linux suggestions fails. Running it as me, nothing happens. Running it as root it collects a report, but never opens a browser window. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066534 Title: kernel segfault reported on inserting any USB device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/2066534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066537] [NEW] kernel segfault reported on inserting any USB device
Public bug reported: Everytime a new device is found on the USB bus a message like this is reported in dmesg and syslog. 2024-05-22T22:50:05.835993+01:00 gmllaptop kernel: w[4942]: segfault at 4c ip 5e15d21dce73 sp 7fff3a087a20 error 4 in w[5e15d21dc000+3000] likely on CPU 2 (core 2, socket 0) It doesn't appear to cause a problem, but then I don't know what it is trying to do when it segfaults. This is on 24.04 (Noble). ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: linux-image-6.8.0-31-generic 6.8.0-31.31 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:gml44103210 F pipewire /dev/snd/controlC0: gml44103213 F wireplumber CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed May 22 23:03:08 2024 InstallationDate: Installed on 2024-05-17 (5 days ago) InstallationMedia: Kubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=4b6c0c29-71de-4815-8a4c-379fbe17299a ro quiet splash resume=UUID=f5b9be2a-4adb-4102-a08d-ab6ba1e267cd vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.8.0-31-generic N/A linux-backports-modules-6.8.0-31-generic N/A linux-firmware20240318.git3b128b60-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066537 Title: kernel segfault reported on inserting any USB device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2066537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057927] Re: lxd vga console throws "Operation not permitted" error
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057927 Title: lxd vga console throws "Operation not permitted" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057927] Re: lxd vga console throws "Operation not permitted" error
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057927 Title: lxd vga console throws "Operation not permitted" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057927] Re: lxd vga console throws "Operation not permitted" error
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057927 Title: lxd vga console throws "Operation not permitted" error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065367] Re: 24.04 LTS Installation failed on RPI5
Got the auto comment about lack of package. Looked at Finding the Right Package. It happens during the installation of Ubuntu 24.04 LTS so it looks like the right package is ubiquity. ** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065367 Title: 24.04 LTS Installation failed on RPI5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2065367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065367] [NEW] 24.04 LTS Installation failed on RPI5
Public bug reported: I had RaspiOS Debian 12 bookworm desktop running on my 8GB Raspberry Pi 5. I'm attempting to switch to the RPi version of Ubuntu Desktop 24.04 LTS. I've created an install microSD card with raspi-imager and selected Other OS then Ubuntu Desktop 24.04 LTS. After picking English, Los Angeles, etc., then I get to the point where I input details to name the host and create my user account, click next and get Installation Failed. I click OK, some text flashes by fast, then get a basic sign-in screen but can't sign in. It won't accept the username and password I selected, and ubuntu/ubuntu. I tried a terminal session on tty2 to see if I could check any logs but again, no working username/password. In case it was some sort of download error with raspi-imager, I downloaded the "ubuntu-24.04-preinstalled-desktop-arm64+raspi.img.xz" file and used Rufus to write that to the install media. The microSDXC card is a brand new Samsung 256GB Pro Plus A2 V30. What do I do now? ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065367 Title: 24.04 LTS Installation failed on RPI5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2065367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064874] [NEW] Fail to upgrade from 22.04 to 23.10
Public bug reported: Both apt.log and main.log do not appear to contain any help in pinpointing the error ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 640:1000:125:60391:2024-04-29 15:33:53.884913579 +0100:2024-04-29 15:33:53.884913579 +0100:/var/crash/_usr_bin_calibre-parallel.1000.crash CurrentDesktop: KDE Date: Sun May 5 17:45:01 2024 InstallationDate: Installed on 2021-06-26 (1043 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to jammy on 2024-05-05 (0 days ago) VarLogDistupgradeAptHistorylog: Start-Date: 2024-05-05 17:15:21 Requested-By: gmb (1000) End-Date: 2024-05-05 17:15:21 VarLogDistupgradeApttermlog: Log started: 2024-05-05 17:15:21 Log ended: 2024-05-05 17:15:21 modified.conffile..etc.update-manager.release-upgrades: [modified] mtime.conffile..etc.update-manager.release-upgrades: 2024-05-04T14:20:47.834718 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064874 Title: Fail to upgrade from 22.04 to 23.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2064874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059776] Re: plasma-discover updates cannot handle apt *.sources files
** Summary changed: - Updates cannot handle apt *.sources files + plasma-discover updates cannot handle apt *.sources files -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059776 Title: plasma-discover updates cannot handle apt *.sources files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059776] Re: Updates cannot handle apt *.sources files
** Attachment added: "Screenshots and configs with 1 *.sources config file." https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+attachment/5760701/+files/Sources-1.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059776 Title: Updates cannot handle apt *.sources files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059776] Re: Updates cannot handle apt *.sources files
** Attachment added: "Screenshots and configs with 5 *.sources config file." https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+attachment/5760702/+files/Sources-5.tar -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059776 Title: Updates cannot handle apt *.sources files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059776] Re: Updates cannot handle apt *.sources files
Note that this is being reported against mantic (23.10) so what Jammy can/cannot do is not really relevant. The bit about the entire Default section disappearing seems to have sorted itself out, but the absence of any information about sources configured using *.sources files is still present. This applies both to the list shown in "Settings/Default source" and the "Software Sources/Other Software" tab. I'll attach the screenshots and the sources/list.d and trusted.gpg.d directories that led to them (these correspond to the same repositories, but Sources-1 just has 1 *.sources file (winehq) as it has been upgraded from Jammy with each 6-month release (just editing the release name in the *.list files) whereas Sources-5 is from a fresh install of Mantic on a new system with recent add-apt-repository runs (mostly form Launchpad), which now produces *.sources files. The plasma-discover version is: root@parent:/local/configs# dpkg -l plasma-discover | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===-=--== ii plasma-discover 5.27.10-0ubuntu1~ubuntu23.10~ppa1 amd64Discover software management suite -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059776 Title: Updates cannot handle apt *.sources files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059776] [NEW] Updates cannot handle apt *.sources files
Public bug reported: Recent additional software sources from launchpad (e.g. grub-customizer, kubuntu backports) drop *.sources files into /etc/apt/sources.list.d/. It seems that plasma-discover cannot handle these. They do not show up in the list of configurable sources. And, even worse than that, it seems that if you have sufficient *.sources files (I had 5 on a newly installed 23.10 system) the entire Default source section is absent from the plasma-discover Settings page! (I got it back by copying over the older, mostly *.list entries and keys from an older system). PS: I've had to report the package here as "don't know" as the search doesn't recognize plasma-discover, and ubuntu-bug doesn't let me choose "Other problem" as an option (-> You need to specify a package or a PID. See --help for more information.) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 6.5.0-26.26-generic 6.5.13 Uname: Linux 6.5.0-26-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Mar 29 13:33:50 2024 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2024-03-06 (23 days ago) InstallationMedia: Kubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: plasma-discover (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ubiquity-23.10.8 ** Package changed: ubuntu => plasma-discover (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059776 Title: Updates cannot handle apt *.sources files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2059776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2018037] Re: Cannot configure Software Sources in Settings
Not sure how "works for me on 22.04" is taken to be a solution for a problem reported on 23.04. I've just looked on 2 of my systems (both 23.10). The one which has been upgraded from 22.04 is OK. The one which was a fresh install (new system) of 23.10 is not. In fact it doesn't show any sources at all. That issue seem to be related to have *.sources files in sources.list.d/ (which works fine with apt, and is how launchpad now sets things up for, e.g., grub-customizer *and* backports). These entries do not show up in Settings. And it seems that if you have enough of them (I had 5 of them) the entire Default Source section is missing from Settings (and, oddly, the Firmware Updates, Snap and Flatpak section then show in the reverse order). So, it looks as though the Software Sources issue is now OK, but there are other issues. I'll open a new bug report for that. ** Changed in: plasma-discover (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2018037 Title: Cannot configure Software Sources in Settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/2018037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771626] Re: After a security update (red) the taskbar icon continually displays "updates available" (blue) when they are none.
** Changed in: plasma-discover (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771626 Title: After a security update (red) the taskbar icon continually displays "updates available" (blue) when they are none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1771626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797730] Re: Second try fails to prompt for authentication if first was canecelled
I've just checked. This is no longer the case in 23.04 (Mantic). ** Changed in: plasma-discover (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797730 Title: Second try fails to prompt for authentication if first was canecelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-discover/+bug/1797730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951148] Re: Desktop icon for pulseeffects is not displayed correctly.
Confirmed. Having downloaded the file in the commit, put it in place, deleted my .cache/icon-cache.kcache file and logged out/in I now have a different icon that does not show the problem. Not sure what status to put on this, but the fix is in; somewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951148 Title: Desktop icon for pulseeffects is not displayed correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/easyeffects/+bug/1951148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806224] Re: Desktop icons can be incorrected placed on the Desktop at login
PS: I am not alone in seeing this. I just came across this: https://mail.kde.org/pipermail/kde/2018-July/028948.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806224 Title: Desktop icons can be incorrected placed on the Desktop at login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1806224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901608] Re: Mouse binding not working on Desktop
It's working in Mantic. I'll mark it as Fix Released. ** Changed in: plasma-desktop (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901608 Title: Mouse binding not working on Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1901608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806224] Re: Desktop icons can be incorrected placed on the Desktop at login
As I said originally, this is intermittent. All of my systems now have SSDs (see #2) but I have seen it once on 23.10 (Mantic). It's not something that can be reproduced at will. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806224 Title: Desktop icons can be incorrected placed on the Desktop at login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1806224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971630] Re: shaded windows forget their height on restore
It does seem to have gone away. I can't reproduce this in Mantic. Changed the status ** Changed in: kwin (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971630 Title: shaded windows forget their height on restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1971630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975494] Re: nvidia module cant load with 5.13.0-41-generic
I have the same problem. The nvidia drivers (version 470 in my case) don't load after upgrading to 5.13.0-41-generic. Reverting to 5.13.0-39-generic fixes the problem. I did notice that -41 has a lot of changes from the "stable" impish kernel and that the modules loaded on my machine with -41 include lots of wmi and i915 stuff: i915 2400256 1 i2c_algo_bit 16384 1 i915 drm_kms_helper253952 1 i915 cec53248 2 drm_kms_helper,i915 drm 557056 3 drm_kms_helper,i915 video 53248 2 dell_wmi,i915 wmi32768 5 dell_wmi_sysman,dell_wmi,wmi_bmof,dell_smbios,dell_wmi_descriptor which the -39 modules does not load. Black listing these modules does not fix the problem. The 2 machines we are having issues with are Dell Optiplex 7090 with a Nvidia GeForce RTX 3070 so I tried the 5.14.0-1038-oem kernel which fortunately fixes the problem for me. Regards, Ian G. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975494 Title: nvidia module cant load with 5.13.0-41-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1975494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971630] Re: shaded windows forget their height on restore
I've worked out what the issue is! This bug occurs if you try to set a Window border size (any size, other than none) for Breeze. This is Settings under Appearance -> Window Decorations/ Window border size (bottom left). Setting a border size for Plastik (which has one by default anyway) is OK. But Breeze (default none) doesn't like you setting any. I set Tiny, as otherwise overlapping window just merge into one another with no dividing line. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971630 Title: shaded windows forget their height on restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1971630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971630] Re: shaded windows forget their height on restore
Thanks. Useful info as: I had a look at how things behaved on the Installation image. It looks OK there - even if I set the double-click == shade option. So it seems as though it's something odd/unusual in my set-up (which has just been dragged along from previous Kubuntu versions). I'll need to do some experiments -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971630 Title: shaded windows forget their height on restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwin/+bug/1971630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971630] [NEW] shaded windows forget their height on restore
Public bug reported: I have double-click on the titlebar set to (toggle) shade the window. If I shade a window (seems to be any window) on Kubuntu Jammy then when I try to restore the window the height is completely wrong - only a few pixels. If the window is maximized vertically then that is restored correctly. Was all fine in Impish but this is happening on both system that I've updated to Jammy. It might not be sddm's fault, but that's the only common factor I can see. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: sddm 0.19.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Wed May 4 22:23:05 2022 InstallationDate: Installed on 2022-05-04 (0 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971630 Title: shaded windows forget their height on restore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1971630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971426] Re: multiple konsoles overlay each other on start-up
I do have "Allow apps to remember the positions of their own windows, if they support it" turned on in: Window Management -> Window Behaviour / Advanced But I've always had that on, and it's never been a problem before. Konsole needs an option to forget its position. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971426 Title: multiple konsoles overlay each other on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/1971426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971426] [NEW] multiple konsoles overlay each other on start-up
Public bug reported: At 22.04 it appears that konsole will remember its last start position. This means that if you want to start, say, 3 konsoles they will now sit on top of each other, hiding how many there are. At 21.10 and earlier they would start up non-overlapped (if possible). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: konsole 4:21.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CurrentDesktop: KDE Date: Tue May 3 13:14:06 2022 InstallationDate: Installed on 2022-04-29 (3 days ago) InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: konsole UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: konsole (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971426 Title: multiple konsoles overlay each other on start-up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/1971426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867668] Re: Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver
I had *exactly* the (very well) described issues here: o Really weird corrupted font artifacts. o Bizarre semi-tiled blocks on my background screen. Occurred after doing an upgrade of Ubuntu 20.04 on an Dell XPS 7590. Running the suggested command: sudo apt remove xserver-xorg-video-intel And rebooting fixed everything. Thanks very much. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867668 Title: Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1867668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956161] Re: partitionmanager crashes when removing a mount point
The original procedure was done under my own id, being prompted for authentication. I have also run it while logged in as root, which enabled me to strace the entire session. This is attached (xz compressed) ** Attachment added: "strace of procedure, run as root" https://bugs.launchpad.net/ubuntu/+source/partitionmanager/+bug/1956161/+attachment/5550586/+files/gml.log.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956161 Title: partitionmanager crashes when removing a mount point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partitionmanager/+bug/1956161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956161] [NEW] partitionmanager crashes when removing a mount point
Public bug reported: I used partition manager to: 1. add a mountpoint (using UUUID) to a new, empty partition (which was ntfs) 2. mount it 3. unmount it 4. remove the mountpoint 1, 2 and 3 run OK. 4 crashes (without having edited /etc/fstab). ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: partitionmanager 21.08.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jan 1 18:45:18 2022 InstallationDate: Installed on 2020-08-13 (506 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: partitionmanager UpgradeStatus: Upgraded to impish on 2021-10-17 (76 days ago) ** Affects: partitionmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956161 Title: partitionmanager crashes when removing a mount point To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partitionmanager/+bug/1956161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
(In reply to Lukáš Karas from comment #24) > Here is my proposed fix in Gwenview: > https://invent.kde.org/graphics/gwenview/-/merge_requests/125 Do we need a prod on the libexiv2 package as well to indicate that it needs an update to fix the cause of the crash? (The fix for gwenview to handle such crashes better is welcome, but not sufficient). I can't see any bug report with libexiv2 as the product. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1955087] [NEW] bluetooth cannot transfer files to phone although connected
Public bug reported: Ubuntu version: 20.4 Not sure of package (bluez)? (Whatever handles Bluetooth) What I expected: File is transferred. What happened: transfer fails with mysterious error code (0x53) which sometimes shows up on phone and sometimes doesn't. In any case the transfer fails. Additional notes: Error was observed before, see https://bbs.archlinux.org/viewtopic.php?id=202815, however suggested solution on that page doesn't work for me so I assume there is some difference. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 16 18:50:38 2021 InstallationDate: Installed on 2021-01-27 (323 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: HP HP Pavilion Desktop TP01-0xxx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-41-generic root=UUID=d2279364-889e-4dd0-9766-948e06f4ab3d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2020 dmi.bios.release: 15.35 dmi.bios.vendor: AMI dmi.bios.version: F.23 dmi.board.name: 8643 dmi.board.vendor: HP dmi.board.version: SMVB dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 52.41 dmi.modalias: dmi:bvnAMI:bvrF.23:bd07/07/2020:br15.35:efr52.41:svnHP:pnHPPavilionDesktopTP01-0xxx:pvr:sku3UQ92AA#ABA:rvnHP:rn8643:rvrSMVB:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Pavilion Desktop PC dmi.product.name: HP Pavilion Desktop TP01-0xxx dmi.product.sku: 3UQ92AA#ABA dmi.sys.vendor: HP hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:15:83:4E:03:27 ACL MTU: 384:8 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:5837051 acl:16480 sco:0 events:6085 errors:0 TX bytes:44273 acl:1706 sco:0 commands:1272 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bluetooth focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1955087 Title: bluetooth cannot transfer files to phone although connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1955087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
(In reply to Gordon Lack from comment #21) Seems to be related to how old the jpegs are. 2016 and earlier it crashes. 2017 and late its OK. Roughly. If I run gwenview on the command line for a failing one this is what I see reported: [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job [gmllaptop]: gwenview DSCN1657.JPG org.kde.kdegraphics.gwenview.lib: Unresolved mime type "image/x-mng" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-nikon-nrw" org.kde.kdegraphics.gwenview.lib: Unresolved raw mime type "image/x-samsung-srw" terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = gwenview path = /usr/bin pid = 15230 KCrash: Arguments: /usr/bin/gwenview DSCN1657.JPG KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi [1]+ Stopped gwenview DSCN1657.JPG [gmllaptop]: fg gwenview DSCN1657.JPG QSocketNotifier: Invalid socket 8 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... QSocketNotifier: Invalid socket 13 and type 'Read', disabling... QSocketNotifier: Invalid socket 18 and type 'Read', disabling... ; ^C [gmllaptop]: fg bash: fg: current: no such job -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941752]
Created attachment 144559 New crash information added by DrKonqi gwenview (21.08.1) using Qt 5.15.2 - What I was doing when the application crashed: Browsing through images with Dolphin. Select to open one in Gwenview. Crashes every time. -- Backtrace (Reduced): #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140466192913600) at pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140466192913600) at pthread_kill.c:80 #6 __GI___pthread_kill (threadid=140466192913600, signo=signo@entry=6) at pthread_kill.c:91 #7 0x7fc0dafab476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fc0daf917b7 in __GI_abort () at abort.c:79 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950912]
The **NOT** part was feedback on my comment 4: > I'll wait to see whether 91.3.2+ also fixes the drop-down menus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950912 Title: [upstream] Drop-down Calendar menus unreadable in Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1950912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950326] Re: roundcube cannot run in Impish
If it's any help I ended up using a download of the standard 1.5 on Impish. It needed: php-pear php-sqlite3 php-json php-mbstring php-intl libapache2-mod-php sqlite3 from Impish. (I have a sqlite3 database). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950326 Title: roundcube cannot run in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/roundcube/+bug/1950326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
Bug report submitted at Mozilla. https://bugzilla.mozilla.org/show_bug.cgi?id=1742202 ** Bug watch added: Mozilla Bugzilla #1742202 https://bugzilla.mozilla.org/show_bug.cgi?id=1742202 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
The previous entry wasn't entirely correct. 91.2.1 was *also* using the configured Light Theme colours (for the colour of the "quote bar" in HTML messages). What has happened on the update to 91.3.1 is that it is now using the Light background colours for the Dark Theme. (In 91.2.1 it was, correctly, using the Dark Theme colours). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
Also (just noticed) that 91.3.1 has introduced *another* bug. I use the "Quote Colors" extension. It has the option to to set the text and background colours for quoted text. You can configure them separately for Light and Dark Themes. At 91.3.1 it is now using the text and background colours configured for a Light Theme, even though I am using a Dark Theme. It's seems that in many places Thunderbird (where many is a growing number) has lost track of the fact it is using a Dark Theme! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950912] Re: Drop-down Calendar menus unreadable in Thunderbird
Today's update to 91.3.1 has made things WORSE!!! Now the (left hand) sidebar in the Preferences menu and Add-ons manager are ALSO displayed with a light background (and light text!!) when I'm using the Dark Theme!!! The drop-down menus are *still* totally wrong (and unreadable). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950912 Title: Drop-down Calendar menus unreadable in Thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1950912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951148] [NEW] Desktop icon for pulseeffects is not displayed correctly.
Public bug reported: The desktop icon for PulseEffect (presumably the file /usr/share/icons/hicolor/scalable/apps/pulseeffects.svg) is not displayed correctly on the KDE plasma desktop. The shadowing(?) of the 3 lines is absent and instead the bottom right- hand corner background of the icon "space" is black. This was also the case in Hirsute. Groovy was OK (if I remember correctly - it certainly has been OK in the past). Picture of the problem is attached. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: plasma-desktop 4:5.22.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Nov 16 17:28:59 2021 InstallationDate: Installed on 2020-05-03 (562 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: plasma-desktop UpgradeStatus: Upgraded to impish on 2021-11-11 (5 days ago) ** Affects: plasma-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "Screenshot of the incorrectly display icon." https://bugs.launchpad.net/bugs/1951148/+attachment/5541253/+files/Screenshot_2026_172832.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951148 Title: Desktop icon for pulseeffects is not displayed correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1951148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950942] [NEW] Intel OpenCL app stopped working on Impish
Public bug reported: I run BOINC and have been running the Collatz project application for Intel GPUs for a few years. These have been working well. On updating to Impish (for Hirsute) all 3 systems running this (3 Intel NUcs with i5-5250U, i3-8109U and i3-10110U CPUs) started to fail *every* Collatz job. The error messages reported by the app are things like: The verification of the steps for 10573729564897346322432 failed. The OpenCL device calculated 46747248 vs 487 steps by the CPU. Processing aborted. Error: GPU steps do not match CPU steps. Workunit processing aborted. The verification of the steps for 10585314751641536200690 failed. The OpenCL device calculated 1577457360 vs 611 steps by the CPU. Processing aborted. Error: GPU steps do not match CPU steps. Workunit processing aborted. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: intel-opencl-icd 21.32.20609-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon Nov 15 03:14:49 2021 InstallationDate: Installed on 2020-05-14 (549 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: intel-compute-runtime UpgradeStatus: Upgraded to impish on 2021-11-11 (3 days ago) ** Affects: intel-compute-runtime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Summary changed: - Intel OpenCL app stopped workign on Impish + Intel OpenCL app stopped working on Impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950942 Title: Intel OpenCL app stopped working on Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-compute-runtime/+bug/1950942/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950912] [NEW] Drop-down Calendar menus unreadable in Thunderbird
Public bug reported: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. The drop-down menus for editing Calendar events (such as options for Repeat: and Reminder:) have light text on a light background, and are hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: Â USERPID ACCESS COMMAND Â /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: Â default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 Â 169.254.0.0/16 dev wlp64s0 scope link metric 1000 Â 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Description changed: I'm using Thunderbird 91.2.1 in Impish with the Dark Theme. - The drop-down menus for editing events (such as options for Repeat: and - Reminder:) have light text on a light background, and are hence - unreadable. + The drop-down menus for editing Calendar events (such as options for + Repeat: and Reminder:) have light text on a light background, and are + hence unreadable. This only started with the move to Impish. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.2.1+build1-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: gml44103277 F pulseaudio + Â USERPID ACCESS COMMAND + Â /dev/snd/controlC0: gml44103277 F pulseaudio BuildID: 20211020014537 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: KDE Date: Sun Nov 14 18:03:28 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (458 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: - default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 - 169.254.0.0/16 dev wlp64s0 scope link metric 1000 - 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 + Â default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 + Â 169.254.0.0/16 dev wlp64s0 scope link metric 1000 + Â 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=91.2.1/20211020014537 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to impish on 2021-10-17 (28 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name:
[Bug 1950326] Re: roundcube cannot run in Impish
** Summary changed: - roundcube cannot run im Impish + roundcube cannot run in Impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950326 Title: roundcube cannot run in Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/roundcube/+bug/1950326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950326] [NEW] roundcube cannot run im Impish
Public bug reported: /usr/share/roundcube/program/include/iniset.php starts with a test for: if (PHP_VERSION_ID >= 8) and refuses to run if this is true. The version of php shipped in Impish is 8.0, so this test fails and roundcube fails to start. There is no earlier version of php available. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: roundcube 1.4.11+dfsg.1-4 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Nov 9 14:10:37 2021 InstallationDate: Installed on 2020-05-08 (550 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: roundcube UpgradeStatus: Upgraded to impish on 2021-11-08 (0 days ago) ** Affects: roundcube (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950326 Title: roundcube cannot run im Impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/roundcube/+bug/1950326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949615] Re: Notify method not working correctly in 21.10 (impish)
** Description changed: The replaces_id parameter to org.freedesktop.Notifications.Notify no longer works correctly at 21.10. It is OK on 21.04. - At 21.10 if a message with replaces_id === x ever times out then any + At 21.10 if a message with replaces_id == x ever times out then any further message sent with that replaces_id never gets shown. The timeout-over seems to become permanent for that replaces_id. Example program to follow ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: dbus 1.12.20-2ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Nov 3 16:49:18 2021 InstallationDate: Installed on 2020-08-13 (447 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: dbus UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949615 Title: Notify method not working correctly in 21.10 (impish) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1949615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806155] Re: Dolphin is (still) using physical device names - and these can change
This is still a problem in 21.10 (impish). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806155 Title: Dolphin is (still) using physical device names - and these can change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1806155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949615] Re: Notify method not working correctly in 21.10 (impish)
This python program shows the problem *=*=* Cut here *=*=* #!/usr/bin/python3 # -*- coding: utf-8 -*- # from pydbus import SessionBus from time import sleep # Global constants # item= "org.freedesktop.Notifications" path= "/org/freedesktop/Notifications" interface = "org.freedesktop.Notifications" app_name= "NotifyTest" icon= "/usr/share/icons/breeze/devices/64/camera-web.svg" actions_list= [] hint= {} bus = SessionBus() notifications = bus.get('.Notifications') # Global variables # our_notify_id = 0 timeout = 3000 # ms wait4 = 0 # s body = "from NotifyTest.py" while wait4 < 6: wait4 += 1 message = "The next wait will be %ss" % wait4 # This should replace any previous notification still there... # (can do this with notify-send command, but doing it in python allows # us to use a fixed id for replacement). # our_notify_id = notifications.Notify(app_name, our_notify_id, icon, message, body, actions_list, hint, timeout) print("our_notify_id:", our_notify_id) # At Ubuntu 21.10 we have to change this to get the new message seen... # #our_notify_id += 1 print(message) sleep(wait4) print("Done") *=*=* Cut here *=*=* On 21.04 after the sleep exceeds the 3s timeout a new info message box is displayed. On 21.10 after the sleep exceeds the 3s timeout nothing is shown. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949615 Title: Notify method not working correctly in 21.10 (impish) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1949615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949615] [NEW] Notify method not working correctly in 21.10 (impish)
Public bug reported: The replaces_id parameter to org.freedesktop.Notifications.Notify no longer works correctly at 21.10. It is OK on 21.04. At 21.10 if a message with replaces_id === x ever times out then any further message sent with that replaces_id never gets shown. The timeout-over seems to become permanent for that replaces_id. Example program to follow ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: dbus 1.12.20-2ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Nov 3 16:49:18 2021 InstallationDate: Installed on 2020-08-13 (447 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: dbus UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949615 Title: Notify method not working correctly in 21.10 (impish) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1949615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900803] Re: BOINC client fails to detect when the system is idle
Note that there appear to be two different patches that need to be incorporated, to fix different underlying causes: https://github.com/BOINC/boinc/pull/3512 https://github.com/BOINC/boinc/pull/4105 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900803 Title: BOINC client fails to detect when the system is idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1900803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900803] Re: BOINC client fails to detect when the system is idle
Any word on when this upstream fix might make its way to Focal? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900803 Title: BOINC client fails to detect when the system is idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1900803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1231091] Re: Screenreader starts, but does not work with installer (ubiquity) in live session
** Merge proposal linked: https://code.launchpad.net/~thesquash/ubuntu/+source/ubiquity/+git/ubiquity/+merge/407632 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1231091 Title: Screenreader starts, but does not work with installer (ubiquity) in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1231091] Re: Screenreader starts, but does not work with installer (ubiquity) in live session
I'm pretty sure I discovered the bug, and I think I know how to rectify it too. Please note that this was a tricky bug to find and it made my head spin for a while; it was only recently when I figured this out from start to end. Here's what I know now: I discovered that Ubiquity's greeter (`maybe-ubiquity`) starts two D-Busses: the normal session bus, which non-root programs communicate over for pretty much everything (including accessibility communications), and the special accessibility bus, which is only used by root programs like Ubiquity. The accessibility bus uses a special configuration file which allows root to use the bus (normally root would be banned from the bus); that configuration file is stored at /usr/share/defaults/at-spi2/accessibility.conf: [...] [...] Depending on the version of Ubuntu in use, the exact application which requests the accessibility bus in the first place (and thus the application which requests the bus to be launched) differs. On stock Ubuntu, it is a portion of the GNOME Settings Daemon; on Ubuntu MATE, it is consistently the Ubiquity panel. Either way, which application starts the bus doesn't matter, as long as an application starts it. When an application requests the bus be started, the D-Bus daemon requests that SystemD launches the `at-spi-bus-launcher` program. This program starts another, separate D-Bus daemon (separate from the main session bus, that is), and tells this new D-Bus daemon to use the aforementioned configuration file. The bus launcher also requests that the new D-Bus daemon inform the bus launcher about how the new D-Bus daemon can be addressed and contacted; the applications need to know about this bus and they need to know how to communicate on it. The D-Bus daemon tells the bus launcher how to contact it when the D-Bus daemon has initialized itself fully. Once the bus launcher knows how to contact the accessibility bus, the bus launcher is supposed to set an *X11 atom* on the root window of the X session which Ubiquity is using. The atom applied to the root window means that any application, even Ubiquity, can quickly and easily find out how to communicate over the accessibility bus. Here's an example of the atom: $ DISPLAY=":0" xprop -root AT_SPI_BUS AT_SPI_BUS(STRING) = "unix:abstract=/tmp/dbus-jvfzJSsTTp,guid=e1dc67ddfb5b08287b1b9676612460d8" This means that the accessibility bus can be reached using a UNIX domain socket (so it can be accessed only on the local system); a proper call to "bind" to the socket at `/tmp/dbus-jvfzJSsTTp` will connect to the accessibility bus (though the `abstract` part means that the socket is not visible in the file system; this is a Linux-only feature, and you'll sometimes see `path` instead, which means the socket can be viewed as part of the file system); and in order to verify that the application is authenticated to access the bus, it must pass the globally unique identifier `e1dc67ddfb5b08287b1b9676612460d8` as proof that it's not an external attacker. Sounds straightforward, right? Wrong. How does the bus launcher know what the address of the *X server* is? Sure, there is the `DISPLAY` environment variable, and that is what the bus launcher tries to get access to; but in general, on UNIX one process cannot get access to an environment variable unless it inherited that variable from its parent. So who's the parent of the bus launcher? You'd think it would be the Ubiquity panel, for example, or the GNOME Settings Daemon, since those programs *requested* the accessibility bus in the first place. Not so; remember how I said that *the Ubiquity panel requests* that *D-Bus requests* that *SystemD launches* the accessibility bus? (Yes, it really *is* that big of a game of Telephone.) But the D-Bus session bus daemon doesn't know what the contents of the X11 `DISPLAY` variable are -- I verified this -- much less does SystemD know that. So how is the accessibility bus supposed to know what X11 display to use?? This one took a lot of digging. Ultimately, it was just luck that I came across the `/usr/bin/ubiquity-dm` program, which holds the key (excerpted from line 407 et seq.): if ( osextras.find_on_path("kwin") or osextras.find_on_path("kwin_x11") or osextras.find_on_path("gnome-shell") ) and osextras.find_on_path("dbus-update-activation-environment"): subprocess.Popen( [ "dbus-update-activation-environment", "--verbose", "--systemd", "DISPLAY", ], stdin=null, stdout=logfile, stderr=logfile, preexec_fn=self.drop_privileges, ) Okay, what's going on here? Let's break this down: If KWin or the GNOME Shell are installed,
[Bug 1231091] Re: Screenreader starts, but does not work with installer (ubiquity) in live session
It's been well over a month since I last reported on this, so I think it's fine time I reported about the latest on the subject. My above comment was mostly correct and slightly wrong. Interestingly, stock Ubuntu 21.10 does not use Wayland (on my setup, at least, with Intel integrated graphics); it uses X11, just like Ubuntu MATE does. But interestingly, Ubiquity on stock Ubuntu starts the *GNOME Shell*, whereas Ubiquity on Ubuntu MATE only starts Marco, a generic Ubiquity top panel (which is supposed to be stocked with indicators, but Ubiquity's panel only works with Unity indicators and not Ayatana indicators), the MATE Settings Daemon, and a handful of other programs. Furthermore, like I suspected, both Ubuntu and Ubuntu MATE start the Ubiquity greeter as root, except their *effective* user IDs are both the respective live session users (`ubuntu` and `ubuntu-mate`, respectively). The latter is done probably to allow communication over D-Bus, because my experiments show that if the process' effective UID is not 999 (the live session user), neither version of Ubiquity will interact with the screen reader. Here's the proof. The first snippet was taken on an Ubuntu 21.10 system (that took me eons to download); the second is from an Ubuntu MATE 21.10 system. Ubuntu: RUSEREUSERPIDPPID COMMAND ubuntu ubuntu 19481941 /usr/bin/pipewire ubuntu ubuntu 19491941 /usr/bin/pipewire-media-session ubuntu ubuntu 19501941 /usr/bin/pulseaudio --daemonize=no --log-target=journal ubuntu ubuntu 19531941 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ubuntu ubuntu 19661941 /usr/libexec/dconf-service ubuntu ubuntu 19831703 /usr/libexec/gsd-a11y-settings ubuntu ubuntu 19861703 /usr/libexec/gsd-keyboard ubuntu ubuntu 19871703 /usr/libexec/gsd-media-keys ubuntu ubuntu 20041703 /usr/libexec/gsd-power ubuntu ubuntu 20051703 /usr/libexec/gsd-xsettings ubuntu ubuntu 20061703 gnome-shell --sm-disable --mode=ubiquity root ubuntu 20282009 /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only ubuntu ubuntu 21512146 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 ubuntu ubuntu 21661941 /usr/libexec/at-spi2-registryd --use-gnome-session Ubuntu MATE: RUSEREUSERPIDPPID COMMAND ubuntu-+ ubuntu-+18821875 /usr/bin/pulseaudio --daemonize=no --log-target=journal ubuntu-+ ubuntu-+18931875 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only ubuntu-+ ubuntu-+18961875 /usr/libexec/dconf-service ubuntu-+ ubuntu-+19261694 /usr/bin/mate-settings-daemon ubuntu-+ ubuntu-+19271694 marco --sm-disable ubuntu-+ ubuntu-+19311694 /usr/lib/ubiquity/panel ubuntu-+ ubuntu-+19381694 nm-applet ubuntu-+ ubuntu-+20001875 /usr/libexec/at-spi-bus-launcher ubuntu-+ ubuntu-+20072000 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3 root ubuntu-+20081942 /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity --greeter --only ubuntu-+ ubuntu-+20931875 /usr/libexec/at-spi2-registryd --use-gnome-session The output was abbreviated slightly; I remove unrelated processes like the RealtimeKit daemon and UDisks. As you can see, the Ubiquity process (`/usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity` on both of them) runs with a real UID of root, but an effective UID of either `ubuntu` or `ubuntu-mate` (the latter was chopped off by `ps`). So there's no dissimilarity there. ***However...*** With the screen reader enabled, from a command line (Ctrl-Alt-F2) I tried launching a text editor on each of them, first as user 999: DISPLAY=":0" pluma & ...and then as root: sudo env DISPLAY=":0" pluma & ...and then with a real UID of 0 and an effective UID of 999, just like Ubiquity: sudo env DISPLAY=":0" setpriv --ruid 0 --rgid 0 --euid 999 --egid 999 --init-groups pluma & The first command cooperated with the screen reader on both systems (i.e., the screen reader told me stuff like "Edit menu... Select All Ctrl-A"). The last two commands worked fine on Ubuntu but not on Ubuntu MATE. I tried these experiments also on the live desktop, not just at the Ubiquity greeter. The results were the same regardless of whether I tried it on the live desktop or on the Ubiquity greeter. Clearly, Ubuntu and Ubuntu MATE are configured differently, somehow pertaining to user IDs allowed to use accessibility features. But where? I ran the above experiments, but through `strace -s 1048576` to capture all (or most) communications going on between pluma / gedit and D-Bus. The
[Bug 1929444] Re: SD card initialization on insertion fails
I've updated to 5.11.0-25-generic and can confirm that my laptop now sees SDH/XC cards OK. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1231091] Re: Screenreader starts, but does not work with installer (ubiquity) in live session
Regarding @hellsworth's observation (post # 11): Though this observation may well lead us down the correct path, I strongly believe both run as the superuser. Here's why: For the record, the MATE desktop's window manager is Marco; the "window manager" on stock Ubuntu is Mutter since stock Ubuntu uses the GNOME desktop. Another thing to note is that stock Ubuntu tends to use Wayland by default, whereas Ubuntu MATE exclusively uses X11 (mainly because the MATE applications don't work very well on Wayland yet). Marco adds the " (as superuser)" suffix to the end of windows which are owned by the superuser. The Marco code which adds the suffix is located on lines 486-491 in the source file `src/core/window-props.c` (see https://github.com/mate-desktop/marco/blob/master/src/core/window- props.c#L486-L491): if (window_owner==0) { /* Simple case-- don't bother to look it up. It's root. */ *target = g_strdup_printf (_("%s (as superuser)"), title); } I was going to look up whether Mutter has a similar block of code for the function, but I discovered I didn't need to: On stock Ubuntu, the maybe-ubiquity screen uses just a plain old, client-side-decorated header bar, which bypasses the window manager's own decorations. I can prove it since this screenshot (https://phoenixnap.com/kb/wp- content/uploads/2021/04/choose-keyboard-layout-for-ubuntu-20.04.png) shows Ubiquity's title bar without the menu button on the left side of the window title bar; the menu icon (which is a group of three white horizontal lines) always appears with the default Mutter settings if Mutter draws the window title. Note that Mutter never draws the window title on Wayland. So in other words, just because one says it's run as the superuser and the other doesn't say it does not mean that the other is not run as the superuser. To find the real answer, we'd have to boot up a stock Ubuntu to the maybe-ubiquity screen, press Ctrl-Alt-F1 to go to a console, log in, and then use `ps` to find out who owns the `ubiquity` process. However, furthermore it would be a good experiment to find out if the Wayland / X11 difference is the culprit. I wonder if any accessibility information is communicated over the X protocol, or if it's all done via D-Bus? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1231091 Title: Screenreader starts, but does not work with installer (ubiquity) in live session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1231091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931799] Re: audio not working on Raspberry Pi 4
This is log. ** Attachment added: "pulseaudio.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+attachment/5507134/+files/pulseaudio.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931799] Re: audio not working on Raspberry Pi 4
When pulseaudio crashed: daniel@RPi4:~$ systemctl --user restart pulseaudio.service [Child 10555, AudioIPC0] WARNING: 8d8426b0 StateCallback() state 2 cubeb error: file /build/firefox-vFiRwG/firefox-89.0.1+build1/dom/media/AudioStream.cpp:654 [Child 10555, MediaDecoderStateMachine #1] WARNING: Decoder=99667c00 [OnMediaSinkAudioError]: file /build/firefox-vFiRwG/firefox-89.0.1+build1/dom/media/MediaDecoderStateMachine.cpp:3916 This is log after restart. ** Attachment added: "pulseaudio_restart.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+attachment/5507135/+files/pulseaudio_restart.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931799] Re: audio not working on Raspberry Pi 4
Pulseaudio crashes, but not regularly. Usually a failure occurs when I listen music (via VLC, Rhythmbox) or I watch youtube. I heard only noise in the headphones when this app is crashed. Only restarting the pulseaudio service helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933693] [NEW] The app doesn't download the weather forecast
Public bug reported: The app does not work well. The weather forecast is not available. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-weather 3.36.1-1 ProcVersionSignature: Ubuntu 5.8.0-1029.32-raspi 5.8.18 Uname: Linux 5.8.0-1029-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 21:06:25 2021 ImageMediaBuild: 20201022 PackageArchitecture: all SourcePackage: gnome-weather UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-weather (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image ** Attachment added: "Zrzut ekranu z 2021-06-25 21-02-56.png" https://bugs.launchpad.net/bugs/1933693/+attachment/5507107/+files/Zrzut%20ekranu%20z%202021-06-25%2021-02-56.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933693 Title: The app doesn't download the weather forecast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-weather/+bug/1933693/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933692] [NEW] weather applet is not loaded by Gnome
Public bug reported: Dear Maintainer, The extension is not loaded by Gnome. The gnome-tweaks displays for it an error. Best regards. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell-extension-weather 0~20170402.git34506a6-2 ProcVersionSignature: Ubuntu 5.8.0-1029.32-raspi 5.8.18 Uname: Linux 5.8.0-1029-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 25 20:53:21 2021 ImageMediaBuild: 20201022 PackageArchitecture: all SourcePackage: gnome-shell-extension-weather UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-weather (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image ** Attachment added: "Zrzut ekranu z 2021-06-25 20-52-44.png" https://bugs.launchpad.net/bugs/1933692/+attachment/5507103/+files/Zrzut%20ekranu%20z%202021-06-25%2020-52-44.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933692 Title: weather applet is not loaded by Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-weather/+bug/1933692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842320] Re: Out of Memory on boot with 5.2.0 kernel
Just had the problem again after upgrading 20.10 to 21.04. Kernel 5.8.0-55 boots OK. Kernel 5.11.0-18 fails with the memory error. I'm just about to re-add the GFXMODE line to grub, which I hope will (again) work around the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842320 Title: Out of Memory on boot with 5.2.0 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931799] [NEW] audio not working on Raspberry Pi 4
Public bug reported: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931527] Re: I have artifacts on Youtube videos in Firefox.
Heavy artifacts on youtube videos ** Attachment added: "Firefox Bug.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+attachment/5503776/+files/Firefox%20Bug.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931527 Title: I have artifacts on Youtube videos in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931527] [NEW] I have artifacts on Youtube videos in Firefox.
Public bug reported: I use a Raspberry Pi 4, and now I have artifacts on Youtube videos in Firefox after update. Ubuntu 20.10, Firefox 89.0+build2-0ubuntu0.20.10.1 arm64 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: firefox 89.0+build2-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1398 F pulseaudio /dev/snd/pcmC1D0p: daniel 1398 F...m pulseaudio /dev/snd/controlC0: daniel 1398 F pulseaudio BuildID: 20210527174632 CasperMD5CheckResult: skip Channel: Unavailable Date: Thu Jun 10 07:55:19 2021 ForcedLayersAccel: False ImageMediaBuild: 20201022 IpRoute: default via 192.168.1.1 dev eth0 proto dhcp metric 100 default via 192.168.1.1 dev wlan0 proto dhcp metric 600 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.113 metric 100 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.114 metric 600 NoProfiles: True PciNetwork: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image groovy raspi-image -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931527 Title: I have artifacts on Youtube videos in Firefox. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931527/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
I can confirm that the "author" kernel fixes the problem on my laptop. (And for good measure I've also tested it on my old laptop, which didn't show the problem, and it still works there too). Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
Sorry for the delay - the notification mail seems to have gone missing. Good job I decided to look anyway. The result is that final WORKS: == root@gmllaptop:~# uname -a Linux gmllaptop 5.11.0-19-generic #20 SMP Wed Jun 2 11:33:21 CST 2021 x86_64 x86_64 x86_64 GNU/Linux root@gmllaptop:~# dmesg | tail -4 [ 114.286474] mmc0: cannot verify signal voltage switch [ 114.410823] mmc0: new ultra high speed SDR50 SDHC card at address e624 [ 114.427153] mmcblk0: mmc0:e624 SD16G 14.8 GiB [ 114.438100] mmcblk0: p1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
The v3 kernel WORKS. The SD card insertion is detected correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930312] Re: USB disks and SD cards mount for wrong user
For the record, this is not specific to Ubuntu or Ubuntu MATE at all -- I see this on Gentoo regularly, for example. It seems to be caused by a race condition in Caja and UDisks which didn't appear until UDisks started mounting volumes under user-specific subdirectories of `/media` -- so for example `user1` has volumes mounted under `/media/user1` and `user2` has volumes mounted under `/media/user2`. In ye olden days, `user1`'s UDisks-utilizing process (such as Caja) would mount the volume; `user2`'s instance of Caja would wait for the volume to get mounted by `user1`'s Caja, then open the shared mountpoint at `/media/[volume]`. Nowadays this doesn't work in any case, since `user1` puts in the request to mount the volume first and the volume is mounted under `user1`'s private mount directory -- `/media/user1/[volume]`. I'm not sure how to fix this yet, though. Maybe (but just a WAG) UDisks needs some kind of integration with the display manager or logind? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930312 Title: USB disks and SD cards mount for wrong user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
I don't have Secure Boot enabled anyway, so that bit's easy. As for the v2 kernel - it FAILS (with the -84 error). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
I can confirm that that 5.11.0-18-generic kernel fixes the problem, The SD card is now visible and mountable on insertion. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
Further info I've just rebooted the laptop using the kernel that was left over from the upgrade from groovy. The mmc card reader works OK there. A reboot back to the latest hirsute kernel has it failing again. So: 5.8.0-53-generic - mmc reader works 5.11.0-17-generic - mmc reader fails -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
Here's the debug data from card insertion/removal. ** Attachment added: "rtsx debug info" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+attachment/5500291/+files/rtsx.info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
I've tested plugging in an SD card to an older laptop (also on hirsute). That is OK. I've also noticed that the: mmc0: error -84 whilst initialising SD card message appears at boot time if the mmc card slot is empty. (the "mmc0: cannot verify signal voltage switch" message also appears on my old laptop, where things I working, so we can discount that). I'll gather the debug info now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] Re: SD card initialization on insertion fails
Further information: Booting the same laptop into MSWindows lets me insert SD cards whilst the system is running and it all works as expected. (So not a hardware problem). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929444] [NEW] SD card initialization on insertion fails
Public bug reported: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919100] [NEW] Composition window doesn't keep IMAP connexion open
Public bug reported: If you are writing a message and have only the Composition window open (not the main reading pane) then when this tries to save the current state of the reply in the Drafts folder (you've taken a short break whilst writing it) the save will fail. The reason is that there is no connexion to the IMAP server (and the Drafts folder is on the IMAP server). If you then start-up the main reading pane the save to the Drafts folder works. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: thunderbird 1:78.7.1+build1-0ubuntu0.20.10.4 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44102927 F pulseaudio BuildID: 20210203182138 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: KDE Date: Mon Mar 15 00:17:42 2021 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2020-08-13 (213 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev wlp64s0 proto dhcp metric 600 169.254.0.0/16 dev wlp64s0 scope link metric 1000 192.168.1.0/24 dev wlp64s0 proto kernel scope link src 192.168.1.10 metric 600 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:732 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=78.7.1/20210203182138 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to groovy on 2020-10-25 (140 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919100 Title: Composition window doesn't keep IMAP connexion open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1919100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917406] [NEW] Can't Install ZORIN on ASUS S533EA Tiger Lake
Public bug reported: I have a Very New Model Laptop ( ASUS S533EA , i7 , 16gb, Intell M.2 NVME 512gb. I can't find a way to Dissable or Change to Legacy Boot in the Bios. This Machine Will Not Boot up any Distro that is MBR, Only GPT. So I have Created my USB3 Flash Drive with Rufus and Set it as GPT. I have Tested this Flash Drive on Other PC's and Verified it Works and will let me Install ZORIN OS 15.3 as GPT. Now When I Attempt to Install on the S533EA , I get the ZORIN Install Screen. But when I try to go ahead and install I get a Blank Screen. I have Tried all Versions of Install that are Listed there, Like , Standard, Safe Graphics and OEM, But no Luck. I can install Ubuntu 20.10 But I can't Map any Local Network Drives. But with Zorin I can. That's one of the reasons I want to use Zorin. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917406 Title: Can't Install ZORIN on ASUS S533EA Tiger Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1917406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
> If you don't want to this fuse fs to be created I probably don't, but have no idea want it actually does. > then either remove xdg-desktop-portal package or mask xdg-document- portal.service with: Thanks. The masking worked fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
>> You can silence this with "df -x fuse.portal" I can, but that's not the point. Whatever is putting the mountpoint there (it's not my choice) should be putting it there in such a way that this does not happen. I *own* the mountpoint directory and file-system. Why should I get an EPERM error that I cannot remove? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
>> Thanks, that's being discussed upstream on https://github.com/flatpak /xdg-desktop-portal/issues/512 No, it's not, as that issue has been closed. Note that I'm seeing this WITHOUT having flatpak installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1905623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906744] [NEW] xdg-document-portal creates a mountpoint which produces an error report from df
Public bug reported: If I run "df" it starts with an error message: [parent]: df df: /run/user/4410/doc: Operation not permitted Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1630320 1604 1628716 1% /run . The /run/user/4410/doc (mode r-x--) has been created by: /usr/libexec/xdg-document-portal started by: /lib/systemd/systemd --user using: /usr/lib/systemd/user/xdg-document-portal.service I'm not sure why this is there, but i appear to have no control over it. It should not result in simple tools such as df producing error messages just because it exists. /proc/mounts shows it as: portal /run/user/4410/doc fuse.portal rw,nosuid,nodev,relatime,user_id=4410,group_id=1001 0 0 If it is a required mount then perhaps df should be made to ignore portal mounts by default? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xdg-desktop-portal 1.8.0-1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Dec 4 02:09:11 2020 InstallationDate: Installed on 2020-05-03 (214 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: xdg-desktop-portal UpgradeStatus: Upgraded to groovy on 2020-10-26 (39 days ago) ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906744 Title: xdg-document-portal creates a mountpoint which produces an error report from df To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1906744/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899111] Re: kdeconnect sms hangs
This seems to have been fixed. Probably (?) by today's update to the Android ap (-> 1.15.1). I can now see my SMS messages on my laptop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899111 Title: kdeconnect sms hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1899111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902429] [NEW] uvcdynctrl unconditionall starts a debug log that can fill the /var partition
Public bug reported: Bug 1: /lib/udev/uvcdynctrl sets: debug=1 which means that it creates /var/log/uvcdynctrl-udev.log and logs its startup and environment there and each invocation. There is no related logrotate.d file to rotate this log, and there is no option to switch it off. Bug 2: related to the above is the fact that this script runs uvcdynctrl at the end, with the log still open. For my webcam *this* will occasionally (once every few days) get into a loop reporting: [libwebcam] Warning: The driver behind device video0 has a slightly buggy impl$ of the V4L2_CTRL_FLAG_NEXT_CTRL flag. It does not return the next higher control ID if a control query fails. A workaround has been enabled. This eventually (quickly?) fills the /var partition. The one I've just obtained was >8GB in size and contained > 116 million lines. Note that even having a logrotate.d script to rotate logs wouldn't help with this. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: uvcdynctrl 0.2.4-1.1ubuntu2 [modified: lib/udev/uvcdynctrl] ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Nov 1 11:52:52 2020 InstallationDate: Installed on 2020-08-13 (79 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: libwebcam UpgradeStatus: Upgraded to groovy on 2020-10-25 (6 days ago) ** Affects: libwebcam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902429 Title: uvcdynctrl unconditionall starts a debug log that can fill the /var partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebcam/+bug/1902429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902429] Re: uvcdynctrl unconditionall starts a debug log that can fill the /var partition
Here's a copy of the start of the log file produced. Imagine the last line being repeated foreever (or at least until your /var partition was full). ** Attachment added: "First 1831 lines of the log" https://bugs.launchpad.net/ubuntu/+source/libwebcam/+bug/1902429/+attachment/5430002/+files/uvcdynctrl-udev.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902429 Title: uvcdynctrl unconditionall starts a debug log that can fill the /var partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebcam/+bug/1902429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] Re: Dovecot imapd server producing SIGSEGV in groovy
And to confirm things, I've put this in place on the real system, and all looks fine there now too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] Re: Dovecot imapd server producing SIGSEGV in groovy
OK, I've found the problem (but never did find a way to get a core dump). I have an addon module in place (fetchmail_wakeup). I hadn't recompiled this with the latest release dev files. When I do rebuild it and put that in place all is well. Sorry to have troubled you I'll close this. ** Changed in: dovecot (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] Re: Dovecot imapd server producing SIGSEGV in groovy
Can't find any core dumps (looking at docs on dovecot.org as to how to get them..). But i have run an strace and it shows this: 7257 <... read resumed>"50 IDLE\r\n", 5920) = 9 7257 --- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=NULL} --- 7257 +++ killed by SIGSEGV (core dumped) +++ so it's crashing when it's asked to idle(?). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] Re: Dovecot imapd server producing SIGSEGV in groovy
<<< I'm hoping to be able to replicate the set-up (and issue) on my laptop, so might be able to get more info there. I have a test set-up that is exhibiting the same problem. Now to (try to) get some real data... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] Re: Dovecot imapd server producing SIGSEGV in groovy
I reckoned there wasn't much to go on. This was more just a case of reporting the fact, in case anyone else sees the issue - since there is a temporary way out. I'm hoping to be able to replicate the set-up (and issue) on my laptop, so might be able to get more info there. There are no core dumps - dovecot turns them off at start-up: Oct 29 15:39:34 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for imap (core dumps disabled) Oct 29 15:39:49 master: Info: Dovecot v2.3.7.2 (3c910f64b) starting up for imap (core dumps disabled) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806155] Re: Dolphin is (still) using physical device names - and these can change
** Summary changed: - Dolhpin is (still) using physical device names - and these can change + Dolphin is (still) using physical device names - and these can change -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806155 Title: Dolphin is (still) using physical device names - and these can change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1806155/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] Re: Dovecot imapd server producing SIGSEGV in groovy
I have a sort-of workaround. I downloaded the relevant dovecot packages (dovecot-core, dovecot-dev and dovecot-imapd) from focal and installed these (a downgrade) over the groovy ones. I also needed libicu66 from focal. Starting up the dovecot service after that (with exactly the same configuration files) resulted in the SIGSEGVs going away. So I've marked these 4 packages to be held. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902128] [NEW] Dovecot imapd server producing SIGSEGV in groovy
Public bug reported: I have a dovecot IMAP service running. It's all been running for a year or so. All OK. The mail files are on an external disk, and teh service is run on whichever of two systems finds that it has the disk at boot time. I've upgraded these two servers from focal to groovy. So I updated the backup server, switched the disk to it (so the dovecot service ran there) updated the main server then switched the disk back there. All seemed to be OK. I was still reading Mail OK on my laptop with Thunderbird. However, next day my wife (using Windows Live Mail) reported an error message. A Delete operation had not completed and WL Mail was not happy. A look at the dovecot logs showed lots of entries like this: Oct 28 21:22:43 imap(ac...@my.example.com)<4212>: Fatal: master: service(imap): child 4212 killed with signal 11 (core dumped) Oct 28 21:22:43 imap(gordon.l...@my.example.com)<4211>: Fatal: master: service(imap): child 4211 killed with signal 11 (core dumped) Oct 28 21:22:43 imap(ac...@my.example.com)<4213>: Fatal: master: service(imap): child 4213 killed with signal 11 (core dumped) Oct 28 21:23:22 imap(ac...@my.example.com)<4327>: Fatal: master: service(imap): child 4327 killed with signal 11 (core dumped) These started on the backup (groovy) system once I switched to it and continued when the service moved back to the main system (also by then on groovy). As noted, most of the service capability is was still there, but some clients see client-side problems. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: dovecot-imapd 1:2.3.7.2-1ubuntu3.2 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Oct 29 18:57:41 2020 InstallationDate: Installed on 2020-05-14 (168 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: dovecot UpgradeStatus: Upgraded to groovy on 2020-10-28 (0 days ago) ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902128 Title: Dovecot imapd server producing SIGSEGV in groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/1902128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901634] [NEW] The effects of anacron cannot be disabled
Public bug reported: If anacron is installed its effects *cannot* be disabled. You can run: systemctl disable anacron anacron.timer but that will not help. That stops anacron running, but it does *not* prevent the run-parts entries in /etc/crontab from running, as they only check for the presence of /usr/sbin/anacron, *not* whether anacron is actually enabled. The test should really be something like: systemctl -q is-enabled anacron (although that still prints an error message if anacron isn't installed - despite the -q. Errors, even intended ones, seem to be unavoidable). The result is that if you have a desktop system that is permanently on, you need to remove anacron - but the next dist-update will put it back in place. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: anacron 2.3-29 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Oct 27 00:21:48 2020 InstallationDate: Installed on 2020-05-03 (176 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: anacron UpgradeStatus: Upgraded to groovy on 2020-10-26 (1 days ago) ** Affects: anacron (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901634 Title: The effects of anacron cannot be disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1901634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901608] [NEW] Mouse binding not working on Desktop
Public bug reported: Just updated to Groovy (20.10). I have a Mouse binding set for my Desktop, so that Vertical Scroll switches desktop. This has stopped working (tested with both the usual two-fingers on the Touchpad, and with a wheel-mouse). It was working fine before the update (from focal). I can still change desktops with ctl-F1, ctl-F2. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: plasma-desktop 4:5.19.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Oct 26 20:16:42 2020 InstallationDate: Installed on 2020-08-13 (74 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: plasma-desktop UpgradeStatus: Upgraded to groovy on 2020-10-25 (1 days ago) ** Affects: plasma-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901608 Title: Mouse binding not working on Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-desktop/+bug/1901608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs