[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 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 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 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 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 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 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 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 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
[Bug 1806155] Re: Dolhpin is (still) using physical device names - and these can change
Still a problem in Groovy (20.10) -- 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: Dolhpin 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 1800752] Re: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance
This has been fixed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1800752 Title: [regression] Wrong EU count for i5-5250U, reducing OpenCL performance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/beignet/+bug/1800752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899111] Re: kdeconnect sms hangs
Still a problem in Groovy. -- 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 1901310] [NEW] Error from VBOX_VERSION_STRING_RAW not being replaced in VNC extension.
Public bug reported: The ExtPack.xml for the VNX ExtensionPack in VirtualBox 6.1.14 (Groovy) contains: @VBOX_VERSION_STRING_RAW@ That @VBOX_VERSION_STRING_RAW@ should have been replaced by 6.1.14, but hasn't been. Editing the file so that this *is* 6.1.14 allows the extension to load. NOTE: that this causes an error to be reported in a Focal -> Groovy update. At least I suspect it does, as one was reported for VirtualBox and this is the only thing I can see wrong with it. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: virtualbox 6.1.14-dfsg-4 [modified: usr/lib/virtualbox/ExtensionPacks/VNC/ExtPack.xml] 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: Sat Oct 24 13:09:17 2020 InstallationDate: Installed on 2020-04-28 (178 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: virtualbox UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) ** Affects: virtualbox (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/1901310 Title: Error from VBOX_VERSION_STRING_RAW not being replaced in VNC extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1901310/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899111] [NEW] kdeconnect sms hangs
Public bug reported: If I try the SMS Message option in KDE Connect the "KDE Connect SMS" window opens up, but it just contains a spinning "busy" cursor, and stays this way forever (or at least for as long as I leave it...). I'd expect to be able to send an SMS message and/or view current ones. Running in a terminal window shows: [parent]: kdeconnect-sms qrc:/qml/main.qml:36: ReferenceError: _initialMessage is not defined kdeconnect.sms.conversations_list: setDeviceId "51dbcd6d1fc8d266" of ConversationListModel(0x559a3c4b5e60) QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken QGridLayoutEngine::addItem: Cell (0, 0) already taken QGridLayoutEngine::addItem: Cell (0, 1) already taken This is on Kubuntu 20.04. (Ubuntu 20.04.1 LTS) kdeconnect (1.4-0ubuntu5) The phone is a MotoG8 Power (Android 10). ** Affects: kdeconnect (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/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 1895874] Re: Can't access phone filesystem with KDE Connect
I see the same. It can access the internal storage OK, but not the SD card. That may well be because KDE Connect hasn't asked (and obtained) access to it, either directly (if possible) or using the Storage Access Framework. For me, the phone is on Android 10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895874 Title: Can't access phone filesystem with KDE Connect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeconnect/+bug/1895874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827778] Re: Can no longer Unmount a removable drive - only Remove it.
If you are interested in a workaround... Put this into a *.desktop file in ~/.local/share/solid/actions/ == NOT THIS LINE == # Add an entry to the Devices menus in the Taskbar to just unmount a # device (not power it down). # Based on code in: # https://bugs.kde.org/show_bug.cgi?id=270808#c64 # # Needs to be in .local/share/solid/actions/ # so just symlink to it from there # # NOTE: that to power off use: # udisksctl power-off -b /dev/sd... # Iff we could determine whether the *whole* device is unmounted we # could add an option for that, but we can't... # [Desktop Action open] Exec=udisksctl unmount -b %d Icon=uninstall Name=Just Unmount device [ADDDED] [Desktop Entry] Actions=open Type=Service X-KDE-Action-Custom=true # This would be better, but doesn't work... #X-KDE-Solid-Predicate=[[IS StorageVolume AND StorageVolume.ignored == false] AND StorageAccess.accessible == 'true'] X-KDE-Solid-Predicate=[IS StorageVolume AND StorageVolume.ignored == false] == NOT THIS LINE EITHER == It will add a "just unmount" option on the Device Notifier section. ** Bug watch added: KDE Bug Tracking System #270808 https://bugs.kde.org/show_bug.cgi?id=270808 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827778 Title: Can no longer Unmount a removable drive - only Remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1827778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864689] Re: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox
>> You can override this via command-line, a system config file, or a local config file + environment variable pointing to it. Some hints as to how to achieve that "local config file + environment variable" would be extremely useful. I've tried it and got nowhere, although I know that setting SECLEVEL=1 would fix my immediate problem, as I can set it on a command line for openssl s_client. See: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1878519 Forcing a minimum SECLEVEL of 2 by default is fine, but there has to be some-way of letting users reduce this when they are talking to external services, or providing services for external clients that cannot, for some reason,change at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864689 Title: openssl in 20.04 can't connect to site that was fine in 19.10 and is fine in Chrome and Firefox To manage notifications about this bug go to: https://bugs.launchpad.net/openssl/+bug/1864689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878519] [NEW] Unable to use TLSv1.1 to connect to external servers
Public bug reported: I'm on 20.04 LTS (Focal Fossa). (Kubuntu) openssl (I'm on 1.1.1f-1ubuntu2) appears to now be set to use a minimum of TLSv1.2 This is despite the fact that the Changelog (https://launchpad.net/ubuntu/+source/openssl/+changelog) says: Revert "Enable system default config to enforce TLS1.2 as a minimum" & "Increase default security level from 1 to 2". As a result of this I can't get fetchmail to connect to an external IMPA server I use, which only uses TLSv1.1 I *can* get: openssl s_client -state -cipher "DEFAULT:@SECLEVEL=1" -connect ... -starttls imap to open a connexion, but I can find no way of getting that option into a configuration file such that it is used. Consequently I cannot use a secure connexion to retrieve my emails. All was fine in 19.10. ** Affects: openssl (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/1878519 Title: Unable to use TLSv1.1 to connect to external servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1878519/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
So this is a real problem for anyone trying to talk to a server over which they have no control. I get this error message when running fetchmail to (try to, but fail to) download mail from an IMAP server. In 19.10 it worked. Making 1.2 the minimum default is OK, but there has to be some simple way that users can tell pre-built *client* packages to use 1.1 if they need to. There is no way i can get fetchmail to call SSL_CTX_set_security_level, and there is no openssl.cfg config file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I had a problem with a *missing* internal microphone today (well, I spotted it today - probably been like this for ages...). Note that this was PulseAudio saying that there were no input devices. The problem (as I eventually spotted) was that I'd set the Profile to be Analgue Stereo Output (under Configuration in PA Volume Control). Setting this to Analogue Stereo Duplex made the internal mic show up. Might not be the problem for most people, but you never know. I did notice that if I plugged in an *external* mic the Profile switched to Duplex automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770044]
A workaround is to cancel all jobs, or at least the duplicates(?). See: https://bugs.launchpad.net/ubuntu/+source/plasma- workspace/+bug/1770044/comments/82 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770044 Title: plasmashell crashes on login - so I can't use my desktop system. To manage notifications about this bug go to: https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.
>>> This is incorrect, as I've just had it happen to me (again) and I'm using Eoan. Although if that actually meant the problem wasn't with plasma-workspace but rather with print-manager then I disagree. Clearly plasma-workspace has the ability to crash when presented with incorrect data. That itself is a bug! Applications should validate their input and handle errors appropriately. A crash is not an appropriate handling. Also, will the Focal fix be backported to the earlier, still suffering releases? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770044 Title: plasmashell crashes on login - so I can't use my desktop system. To manage notifications about this bug go to: https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770044] Re: plasmashell crashes on login - so I can't use my desktop system.
>>> no longer affects: plasma-workspace (Ubuntu Eoan) This is incorrect, as I've just had it happen to me (again) and I;m using Eoan. Here is my print queue: [gmllaptop]: lpstat -R 0 MFCJ6930DW-111gml4410 1024 Fri 24 Jan 2020 17:14:13 GMT 1 MFCJ6930DW-111gml4410 1024 Fri 24 Jan 2020 17:14:13 GMT 2 MFCJ6930DW-111gml4410 1024 Fri 24 Jan 2020 17:14:13 GMT Note that despite the time (>9 days ago) it only caused the problem just now (I suspect at approximately the midnight rollover from Sunday Feb 2nd to Monday 3rd). A "cancel -x -a" has removed these records and my laptop is now OK again. Attached is the saved crash text file. ** Attachment added: "plasmashell-20200203-000819.kcrash.txt" https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1770044/+attachment/5324881/+files/plasmashell-20200203-000819.kcrash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770044 Title: plasmashell crashes on login - so I can't use my desktop system. To manage notifications about this bug go to: https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857788] Re: vulkaninfo fails to initialize
Well, that's weird then. My laptop has an i5-4330M and, according to Intel, that has Intel HD Graphics 4600. According to the list at that link this doesn't work with Vulkan. But the steam game (Civ VI) that doesn't run on my i5-2500K runs perfectly OK on my i5-4330M. Although vulkaninfo does report: Vulkan Instance Version: 1.1.114 INTEL-MESA: warning: Haswell Vulkan support is incomplete it does seem that the Mesa drivers have different support to Intel's ones? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857788 Title: vulkaninfo fails to initialize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan-tools/+bug/1857788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857788] Re: vulkaninfo fails to initialize
Thanks. I suspected this to be the case, but couldn't find any information on which GPUs are supported. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857788 Title: vulkaninfo fails to initialize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan-tools/+bug/1857788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857788] [NEW] vulkaninfo fails to initialize
Public bug reported: vulkaninfo fails to initialize with: [parent]: vulkaninfo == VULKANINFO == Vulkan Instance Version: 1.1.114 /build/vulkan-tools-IZAxVX/vulkan- tools-1.1.114.0+dfsg1/vulkaninfo/vulkaninfo.c:5884: failed with VK_ERROR_INITIALIZATION_FAILED This actually really showed up while trying to run a game under Steam. This does run on my other systems, so I'm not sure whether this is a bug, or whether the integrated graphics on the system (it's an Intel Core i5-2500K, so Intel HD 3000 - I think) isn't supported. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: vulkan-tools 1.1.114.0+dfsg1-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: KDE Date: Sun Dec 29 00:38:23 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-14 (348 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: vulkan-tools UpgradeStatus: Upgraded to eoan on 2019-10-22 (67 days ago) ** Affects: vulkan-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857788 Title: vulkaninfo fails to initialize To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vulkan-tools/+bug/1857788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770044]
>>> Anyone knows what exactly happened on Cups side? I was wondering a similar thing. But rather what the "cups database" of past jobs looked like when it has multiple jobs with teh same id. When I went looking the info was only in /var/spool/cups and the job number was taken from the filename, so what does this look like when there are multiple ids? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770044 Title: plasmashell crashes on login - so I can't use my desktop system. To manage notifications about this bug go to: https://bugs.launchpad.net/print-manager/+bug/1770044/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848927] [NEW] Update for Thunderbird 68 means it shows as a (incompatible) Firefox extension
Public bug reported: Updated to Kubuntu 19.10, which updates Thunderbird to 68 (new add-on API). The enigmail (Thunderbird) extension now show up in Firefox Add-ons labelled as "Enigmail is incompatible with Firefox 69.0.3." ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: enigmail 2:2.1.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Sun Oct 20 14:36:50 2019 InstallationDate: Installed on 2017-11-01 (717 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: enigmail UpgradeStatus: Upgraded to eoan on 2019-10-20 (0 days ago) ** Affects: enigmail (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848927 Title: Update for Thunderbird 68 means it shows as a (incompatible) Firefox extension To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/enigmail/+bug/1848927/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770044]
FWIW. That comment about that multiple jobs with the same id shouldn't exist. I just decided to use the taskbar print-queue viewer (kde-print-queue) and selected "All Jobs". At that point it crashed (but only it - plasma was OK). But "lpstat -W completed" shows this - several multiple entries... [parent]: lpstat -W completed MFCJ4410DW-52 gml44108081408 Sun 01 Sep 2019 22:31:09 BST MFCJ4410DW-51 gml44103419136 Sun 01 Sep 2019 22:28:35 BST MFCJ4410DW-49 gml4410 667648 Sun 01 Sep 2019 22:20:14 BST MFCJ4410DW-48 gml4410 12908544 Sun 01 Sep 2019 22:18:02 BST MFCJ4410DW-47 gml4410 522240 Sun 01 Sep 2019 22:16:27 BST MFCJ4410DW-46 gml4410 667648 Sun 01 Sep 2019 22:15:51 BST MFCJ4410DW-45 gml4410 633856 Sun 01 Sep 2019 22:15:19 BST MFCJ4410DW-44 gml44103618816 Sun 01 Sep 2019 22:13:56 BST MFCJ4410DW-43 gml44103674112 Sun 01 Sep 2019 22:13:06 BST MFCJ4410DW-40 gml44101386496 Sun 01 Sep 2019 21:48:04 BST MFCJ4410DW-39 gml44101386496 Sun 01 Sep 2019 21:47:16 BST MFCJ4410DW-38 gml44101199104 Sun 01 Sep 2019 21:44:59 BST MFCJ4410DW-37 gml44101199104 Sun 01 Sep 2019 21:44:16 BST MFCJ4410DW-36 gml44101832960 Sun 01 Sep 2019 21:42:29 BST MFCJ4410DW-35 gml44105528576 Sun 01 Sep 2019 21:37:53 BST MFCJ4410DW-33 gml44101867776 Sun 01 Sep 2019 21:32:38 BST MFCJ4410DW-33 gml44101867776 Sun 01 Sep 2019 21:32:38 BST MFCJ4410DW-31 gml4410 104448 Tue 13 Aug 2019 12:52:43 BST MFCJ4410DW-31 gml4410 104448 Tue 13 Aug 2019 12:52:43 BST MFCJ4410DW-30 gml4410 256000 Tue 06 Aug 2019 08:09:15 BST MFCJ4410DW-30 gml4410 256000 Tue 06 Aug 2019 08:09:15 BST MFCJ4410DW-29 gml44105049344 Tue 06 Aug 2019 08:08:49 BST MFCJ4410DW-29 gml44105049344 Tue 06 Aug 2019 08:08:49 BST MFCJ4410DW-28 gml4410 131072 Mon 05 Aug 2019 03:10:27 BST MFCJ4410DW-28 gml4410 131072 Mon 05 Aug 2019 03:10:27 BST MFCJ4410DW-27 gml4410 437248 Sat 03 Aug 2019 05:52:51 BST MFCJ4410DW-27 gml4410 437248 Sat 03 Aug 2019 05:52:51 BST MFCJ4410DW-26 gml4410 178176 Fri 02 Aug 2019 00:24:39 BST MFCJ4410DW-26 gml4410 178176 Fri 02 Aug 2019 00:24:39 BST MFCJ4410DW-25 gml4410 312320 Sat 15 Jun 2019 08:55:55 BST MFCJ4410DW-25 gml4410 312320 Sat 15 Jun 2019 08:55:55 BST MFCJ4410DW-24 gml44101629184 Sun 09 Jun 2019 18:51:18 BST MFCJ4410DW-24 gml44101629184 Sun 09 Jun 2019 18:51:18 BST MFCJ4410DW-23 gml4410 211968 Sun 02 Jun 2019 11:11:43 BST MFCJ4410DW-23 gml4410 211968 Sun 02 Jun 2019 11:11:43 BST MFCJ4410DW-22 gml4410 521216 Sun 02 Jun 2019 11:05:51 BST MFCJ4410DW-22 gml4410 521216 Sun 02 Jun 2019 11:05:51 BST MFCJ4410DW-21 gml4410 32768 Wed 15 May 2019 12:17:19 BST MFCJ4410DW-21 gml4410 32768 Wed 15 May 2019 12:17:19 BST MFCJ4410DW-20 gml4410 294912 Wed 15 May 2019 10:58:47 BST MFCJ4410DW-20 gml4410 294912 Wed 15 May 2019 10:58:47 BST MFCJ4410DW-19 gml4410 250880 Wed 15 May 2019 10:58:16 BST MFCJ4410DW-19 gml4410 250880 Wed 15 May 2019 10:58:16 BST MFCJ4410DW-18 gml4410 81920 Tue 14 May 2019 10:25:39 BST MFCJ4410DW-18 gml4410 81920 Tue 14 May 2019 10:25:39 BST MFCJ4410DW-14 gml4410 245760 Mon 13 May 2019 11:10:57 BST MFCJ4410DW-14 gml4410 245760 Mon 13 May 2019 11:10:57 BST MFCJ4410DW-14 gml4410 245760 Mon 13 May 2019 11:10:57 BST MFCJ4410DW-13 gml4410 300032 Sat 11 May 2019 15:43:22 BST MFCJ4410DW-13 gml4410 300032 Sat 11 May 2019 15:43:22 BST MFCJ4410DW-13 gml4410 300032 Sat 11 May 2019 15:43:22 BST MFCJ4410DW-12 gml44107809024 Sun 05 May 2019 01:04:45 BST MFCJ4410DW-12 gml44107809024 Sun 05 May 2019 01:04:45 BST MFCJ4410DW-12 gml44107809024 Sun 05 May 2019 01:04:45 BST MFCJ4410DW-11 gml4410 137216 Wed 24 Apr 2019 18:56:44 BST MFCJ4410DW-11 gml4410 137216 Wed 24 Apr 2019 18:56:44 BST MFCJ4410DW-11 gml4410 137216 Wed 24 Apr 2019 18:56:44 BST MFCJ4410DW-10 gml4410 137216 Wed 24 Apr 2019 18:53:34 BST MFCJ4410DW-10 gml4410 137216 Wed 24 Apr 2019 18:53:34 BST MFCJ4410DW-10 gml4410 137216 Wed 24 Apr 2019
[Bug 1755314] Re: When the tab bar is hidden, windows open with two extra rows
I want 80x24. So a current workaround is to set 80x22. But that is not "correct". I'm still seeing this on 19.04 (Disco Dingo). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755314 Title: When the tab bar is hidden, windows open with two extra rows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/konsole/+bug/1755314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825733] Re: ubuntu-release-upgrader-core shows upgrading from 18.10 to 18.10 in nl
It's not the first occurrence of "18.10" that's the issue; it's the second, which should have been 19.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825733 Title: ubuntu-release-upgrader-core shows upgrading from 18.10 to 18.10 in nl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1825733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827778] [NEW] Can no longer Unmount a removable drive - only Remove it.
Public bug reported: If I right-click on a mounted Removable Device in dolphin I get the option to "Safely remove it". This will unmount it and *power it off*! Which means I need to remove it and plug it back in again to get it to show up. Not what I want... This is a change at 19.04. Previously it would just unmount it. (Or rather, it would just unmount an external disk-drive, but would remove a usb-stick). There should be an option to just unmount (which is perfectly possible to do - "udisksctl unmount" achieves it). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: dolphin 4:18.12.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: KDE Date: Sun May 5 13:53:05 2019 InstallationDate: Installed on 2019-01-14 (110 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) SourcePackage: dolphin UpgradeStatus: Upgraded to disco on 2019-05-04 (1 days ago) ** Affects: dolphin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827778 Title: Can no longer Unmount a removable drive - only Remove it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dolphin/+bug/1827778/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825733] Re: ubuntu-release-upgrader-core shows upgrading from 18.10 to 18.10 in nl
FYI: There's a screenshot (in English, so not a translation issue) at https://bugs.launchpad.net/bugs/1825733 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825733 Title: ubuntu-release-upgrader-core shows upgrading from 18.10 to 18.10 in nl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1825733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
