[Bug 2066174] [NEW] do-release-upgrade crashes and roles back
Public bug reported: do-release-upgrade fails with: " Änderungen werden berechnet Änderungen werden berechnet Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind Ein unlösbares Problem trat während der Berechnung der Systemaktualisierung auf. Wenn keine dieser zutrifft, melden Sie bitte den Fehler mithilfe des Befehls 'ubuntu-bug ubuntu-release-upgrader-core' in einem Terminal. Wenn Sie dies selbst untersuchen möchten, finden Sie in den Protokolldateien unter »/var/log/dist-upgrade« Details zur Systemaktualisierung. Schauen Sie sich insbesondere »main.log« und »apt.log« an. " mail-log: " 2024-05-20 15:49:01,132 DEBUG quirks: running PostDistUpgradeCache 2024-05-20 15:49:01,133 DEBUG running Quirks.PostDistUpgradeCache 2024-05-20 15:49:01,292 DEBUG Comparing 4.10.0-35 with 2024-05-20 15:49:01,292 DEBUG Comparing 4.13.0-36 with 4.10.0-35 2024-05-20 15:49:01,292 DEBUG Comparing 4.13.0-46 with 4.13.0-36 2024-05-20 15:49:01,292 DEBUG Comparing 5.15.0-106 with 4.13.0-46 2024-05-20 15:49:01,293 DEBUG Comparing 5.15.0-107 with 5.15.0-106 2024-05-20 15:49:01,293 DEBUG Comparing 5.4.0-121 with 5.15.0-107 2024-05-20 15:49:01,293 DEBUG Comparing 6.5.0-35 with 5.15.0-107 2024-05-20 15:49:01,422 DEBUG Marking 'kubuntu-desktop' for upgrade 2024-05-20 15:49:02,193 WARNING Can't mark 'kubuntu-desktop' for upgrade (E:Fehler: Unterbrechungen durch pkgProblemResolver::Resolve hervorgerufen; dies könnte durch zurückgehaltene Pakete verursacht worden sein.) 2024-05-20 15:49:02,537 ERROR Dist-upgrade failed: 'Defekte Pakete nach der Aktualisierung: fontconfig-config' 2024-05-20 15:49:02,550 DEBUG abort called 2024-05-20 15:49:02,554 DEBUG openCache() 2024-05-20 15:49:04,775 DEBUG Comparing 4.10.0-35 with 2024-05-20 15:49:04,775 DEBUG Comparing 4.13.0-36 with 4.10.0-35 2024-05-20 15:49:04,775 DEBUG Comparing 4.13.0-46 with 4.13.0-36 2024-05-20 15:49:04,777 DEBUG Comparing 5.15.0-106 with 4.13.0-46 2024-05-20 15:49:04,777 DEBUG Comparing 5.15.0-107 with 5.15.0-106 2024-05-20 15:49:04,778 DEBUG Comparing 5.4.0-121 with 5.15.0-107 2024-05-20 15:49:04,908 DEBUG /openCache(), new cache size 88994 " apt.log: " Investigating (17) kubuntu-settings-desktop:amd64 < 1:22.04.10 -> 1:23.10.2 @ii umU Ib > Broken kubuntu-settings-desktop:amd64 Kollidiert mit on desktop-base:amd64 < 11.0.3ubuntu1 | 12.0.6+nmu1ubuntu1 @ii umH > Conflicts//Breaks against version 12.0.6+nmu1ubuntu1 for desktop-base but that is not InstVer, ignoring Considering desktop-base:amd64 1 as a solution to kubuntu-settings-desktop:amd64 1 MarkKeep kubuntu-settings-desktop:amd64 < 1:22.04.10 -> 1:23.10.2 @ii umU Ib > FU=0 Holding Back kubuntu-settings-desktop:amd64 rather than change desktop-base:amd64 Investigating (18) fontconfig-config:amd64 < 2.13.1-4.2ubuntu5 -> 2.14.2-4ubuntu1 @ii umU Ib > Broken fontconfig-config:amd64 Beschädigt on kubuntu-settings-desktop:amd64 < 1:22.04.10 | 1:23.10.2 @ii umH > (< 1:23.04.3) Considering kubuntu-settings-desktop:amd64 1 as a solution to fontconfig-config:amd64 77 Upgrading kubuntu-settings-desktop:amd64 due to Breaks field in fontconfig-config:amd64 Investigating (18) kubuntu-settings-desktop:amd64 < 1:22.04.10 -> 1:23.10.2 @ii umU Ib > Broken kubuntu-settings-desktop:amd64 Kollidiert mit on desktop-base:amd64 < 11.0.3ubuntu1 | 12.0.6+nmu1ubuntu1 @ii umH > Conflicts//Breaks against version 12.0.6+nmu1ubuntu1 for desktop-base but that is not InstVer, ignoring Considering desktop-base:amd64 1 as a solution to kubuntu-settings-desktop:amd64 1 MarkKeep kubuntu-settings-desktop:amd64 < 1:22.04.10 -> 1:23.10.2 @ii umU Ib > FU=0 Holding Back kubuntu-settings-desktop:amd64 rather than change desktop-base:amd64 Investigating (19) fontconfig-config:amd64 < 2.13.1-4.2ubuntu5 -> 2.14.2-4ubuntu1 @ii umU Ib > Broken fontconfig-config:amd64 Beschädigt on kubuntu-settings-desktop:amd64 < 1:22.04.10 | 1:23.10.2 @ii umH > (< 1:23.04.3) Considering kubuntu-settings-desktop:amd64 1 as a solution to fontconfig-config:amd64 77 Upgrading kubuntu-settings-desktop:amd64 due to Breaks field in fontconfig-config:amd64 Investigating (19) kubuntu-settings-desktop:amd64 < 1:22.04.10 -> 1:23.10.2 @ii umU Ib > Broken kubuntu-settings-desktop:amd64 Kollidiert mit on desktop-base:amd64 < 11.0.3ubuntu1 | 12.0.6+nmu1ubuntu1 @ii umH > Conflicts//Breaks against version 12.0.6+nmu1ubuntu1 for desktop-base but that is not InstVer, ignoring Considering desktop-base:amd64 1 as a solution to kubuntu-settings-desktop:amd64 1 MarkKeep kubuntu-settings-desktop:amd64 < 1:22.04.10 -> 1:23.10.2 @ii umU Ib > FU=0 Holding Back kubuntu-settings-desktop:amd64 rather than change desktop-base:amd64 Done " ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.19 ProcVersionSignature: Ubuntu 5.15.0-107.117-generic 5.15.149 Uname: Linux 5.15.0-107-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult:
[Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
Thank You very much. Works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060659 Title: X11 fractional scaling support is missing in 46.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magpie/+bug/2060659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062554] Re: Enabling keyboard layout plugin crashes session
Yes ibus is installed. # dpkg --get-selections |grep ibus gir1.2-ibus-1.0:amd64 install ibusinstall ibus-data install ibus-gtk:amd64 install ibus-gtk3:amd64 install ibus-gtk4:amd64 install libibus-1.0-5:amd64 install libusb-1.0-0:amd64 install libusbmuxd6:amd64 install libusbredirhost1t64:amd64 install libusbredirparser1t64:amd64 install python3-ibus-1.0install My keyboard layout is Finnish and Swedish is the second. They as far as I know identical. I will try with another user account later today and see if I can reproduce this with a fresh user account. edit: no crash with a freshly created user. I'll check later if I have any logs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062554 Title: Enabling keyboard layout plugin crashes session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2062554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062554] Re: Enabling keyboard layout plugin crashes session
** Description changed: If I try to add the Keyboard Layout Plugin to Budgie Panel my session crashes with an overlay of some sort that doesn't allow me to run - 'budgie-panel --replace --reset'. + 'budgie-panel --replace --reset'. I think the overlay comes from + 'budgie-session-failed'. If a plugin crashes then at least leave me with a desktop that I can try to fix. Well I guess I just submitted two bugs in one :) Noticed while wondering why Ctrl+Shift+U doesn't work in Budgie when I try to enter Unicode chars. Should be a third bug really. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-desktop 10.9.1-3ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Fri Apr 19 16:24:02 2024 InstallationDate: Installed on 2024-03-21 (29 days ago) InstallationMedia: Ubuntu-Budgie 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2024-03-21 (29 days ago) ** Description changed: If I try to add the Keyboard Layout Plugin to Budgie Panel my session crashes with an overlay of some sort that doesn't allow me to run 'budgie-panel --replace --reset'. I think the overlay comes from 'budgie-session-failed'. If a plugin crashes then at least leave me with a desktop that I can try - to fix. + to fix. Or allow Alt-F2 on top of the overlay. Well I guess I just submitted two bugs in one :) Noticed while wondering why Ctrl+Shift+U doesn't work in Budgie when I try to enter Unicode chars. Should be a third bug really. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-desktop 10.9.1-3ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Fri Apr 19 16:24:02 2024 InstallationDate: Installed on 2024-03-21 (29 days ago) InstallationMedia: Ubuntu-Budgie 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2024-03-21 (29 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/2062554 Title: Enabling keyboard layout plugin crashes session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2062554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062554] [NEW] Enabling keyboard layout plugin crashes session
Public bug reported: If I try to add the Keyboard Layout Plugin to Budgie Panel my session crashes with an overlay of some sort that doesn't allow me to run 'budgie-panel --replace --reset'. If a plugin crashes then at least leave me with a desktop that I can try to fix. Well I guess I just submitted two bugs in one :) Noticed while wondering why Ctrl+Shift+U doesn't work in Budgie when I try to enter Unicode chars. Should be a third bug really. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: budgie-desktop 10.9.1-3ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Fri Apr 19 16:24:02 2024 InstallationDate: Installed on 2024-03-21 (29 days ago) InstallationMedia: Ubuntu-Budgie 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all SourcePackage: budgie-desktop UpgradeStatus: Upgraded to noble on 2024-03-21 (29 days ago) ** Affects: budgie-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble 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/2062554 Title: Enabling keyboard layout plugin crashes session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2062554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060659] Re: X11 fractional scaling support is missing in 46.0
I can report that the packages 46.0-1ubuntu8 works like a charm, many thanks! Downloaded the from here: https://launchpad.net/ubuntu/+source/mutter I did however had to use --force-overwrite on mutter-common since there was a conflict with the file ./usr/share/glib-2.0/schemas/org.gnome.mutter.gschema.xml that is also provided by magpie-common. This could also have been a side effect from my testing. What I can tell there's still that conflict. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060659 Title: X11 fractional scaling support is missing in 46.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2060659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
That version is about 100 releases old, it's not my fault linux mint refuses to ship a current inxi. File a bug report with linux mint where it might do some good, not here, the ubuntu version in Jammy is current, and hirsute and impish both have 3.3.0x inxi versions as well. Mint failing to update isn't an inxi bug, it's not an ubuntu bug, and its not a Debian bug, it's a Mint bug, so file the issue there, ask them to update inxi, god knows I've tried doing that enough times to finally give up on trying anymore, but maybe more voices will get them to stop shipping that antique inxi. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
Current inxi release is 3.3.13. What is 'this' referring to? Never use the term 'this' when discussing technical issues, it does not narrow it down enough to convey meaning. Rather than ask if 'this is still an issue', why don't you test it and see? The bug reported here is 50 to 100 releases of inxi ago. jammy has 3.3.13 as of now. An undefined data bug would have been fixed immediately once detected and reported. I believe this issue was closed ages ago, and if not, it should have been. Did you possibly post in the wrong bug issue? If you have a new issue, then file it as such, but make sure you are talking about current inxi, from the github master branch, not a legacy unsupported version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914845] Re: usb-c ports Titan Ridge capped at 480 Mb/s
What is not working is hotplug of any device 5+ Gb/s on Apple computers with Intel cpu, 2016+ At boot time, devices are recognized by efi firmware. After that, any unplugged device is gone until again plugged in during boot https://bugzilla.kernel.org/show_bug.cgi?id=211681 https://apple.stackexchange.com/questions/411321/mac- mini-2018-macmini8-1-linux-usb-c-will-not-recognize-certain-usb-device- typ https://unix.stackexchange.com/questions/632179/ubuntu-mac- mini-2018-macmini8-1-usb-c-capped-at-480-mb-s https://www.reddit.com/r/Gentoo/comments/mlkc57/usb_drive_only_detected_when_attached_at_boot/ ** Bug watch added: Linux Kernel Bug Tracker #211681 https://bugzilla.kernel.org/show_bug.cgi?id=211681 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914845 Title: usb-c ports Titan Ridge capped at 480 Mb/s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914845/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
Hello Frank hm, the output shows absolutely no relationship with AP bus or zcrypt device driver code. Neither the kernel callstack nor the userspace iucvserv application has any relations to my patch series. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1913442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915501] Re: init.d script fails to set socket ownership and permissions on slower systems
Hi Nick, ok then I will close this bug and hope the new server works well. Bye Harald -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915501 Title: init.d script fails to set socket ownership and permissions on slower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915501] Re: init.d script fails to set socket ownership and permissions on slower systems
Fixed by newer version of amavisd-milter package. ** Changed in: amavisd-milter (Ubuntu) Status: In Progress => 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/1915501 Title: init.d script fails to set socket ownership and permissions on slower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940813] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: Build ends with a crash ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-27-generic Date: Mon Aug 23 10:46:48 2021 InstallationDate: Installed on 2020-09-21 (336 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940813 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1940813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926809] Re: WD19 dock stops working in Ubuntu 21.04
I think here are more information: https://gitlab.freedesktop.org/drm/intel/-/issues/2579 ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #2579 https://gitlab.freedesktop.org/drm/intel/-/issues/2579 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926809 Title: WD19 dock stops working in Ubuntu 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
** Changed in: evolution-data-server (Ubuntu) Assignee: Sebastien Bacher (seb128) => Harald Meier (supersluttommy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1915501] Re: init.d script fails to set socket ownership and permissions on slower systems
Dear Nick, first thanks for your bug report the problem is already known (Debian bug #854180) and worked around in commit https://salsa.debian.org/haraldj-guest/amavisd-milter/-/commit/33e39f13387bc29e011ff1d55475c8ead3ca1dad. The real fix was done by the upstream author to create the pipe before returning control to the init script but this fix is only available in version 1.7.0 of amavisd-milter. So my advice would be to either apply the fix from https://salsa.debian.org/haraldj-guest/amavisd-milter/-/commit/33e39f13387bc29e011ff1d55475c8ead3ca1dad which loops forever with a shorter delay time or to rebuild the source package from Ubuntu Hirsute Hippo which incorporates the fix. For rebuilding the source package please look at https://bugs.launchpad.net/bionic-backports/+bug/1905541 where I already documented the requirements. You may also request a official backport by creating a bug report at https://launchpad.net/bionic-backports but mine wasn't considered until now. Again thanks for your report and your work I'm currently unsure what to do with your bug report as I don't know how to best fix this issue in a LTS release. Kind regards Harald Jenny ** Changed in: amavisd-milter (Ubuntu) Status: New => In Progress ** Changed in: amavisd-milter (Ubuntu) Assignee: (unassigned) => Harald Jenny (harald-a-little-linux-box) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915501 Title: init.d script fails to set socket ownership and permissions on slower systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1915501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 27520] Re: cron daemon caches user-non-existent lookup results, causing "ORPHAN" message and skipping jobs for all LDAP/NIS-defined users
I noticed this error on Ubuntu 20.10. Local OpenLDAP, nslcd and a LDAP- user's cron-jobs aren't run because the log says orphaned. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/27520 Title: cron daemon caches user-non-existent lookup results, causing "ORPHAN" message and skipping jobs for all LDAP/NIS-defined users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913698] [NEW] Enabled LDAP, cannot login if user not in /etc/passwd
Public bug reported: I installed nslcd, libnss-ldapd, migration-tools, slapd, ldapscripts. Using the migration-scripts I copied the users to LDAP. getent shadow (as root) shows encrypted passwords and everything works as it should. Lightdm however, doesn't. I'm unable to logon using Xephyr (XDMCP) or locally. As a workaround I can copy the line for the user back into /etc/passwd and then login works. I don't need a line in /etc/shadow, this info comes from LDAP. Is lightdm using some funky stuff to deduce if a user is viable for login that isn't transferred to LDAP? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Jan 29 10:52:44 2021 InstallationDate: Installed on 2010-11-05 (3737 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) RebootRequiredPkgs: linux-image-5.8.0-41-generic linux-base SourcePackage: lightdm UpgradeStatus: Upgraded to groovy on 2021-01-09 (19 days ago) mtime.conffile..etc.pam.d.lightdm: 2021-01-27T18:42:58.039516 mtime.conffile..etc.pam.d.lightdm-greeter: 2021-01-27T18:37:32.863856 ** Affects: lightdm (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/1913698 Title: Enabled LDAP, cannot login if user not in /etc/passwd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1913698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
Note that the option --tty also often takes care of these issues, that was added before 3.0.32, though I'm not positive about which bug this user has, but they can trivially verify by simply testing on current inxi, if it goes away, the bug was fixed long ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911837] Re: inxi, error "Use of uninitialized value $val2"
This version of inxi is obsolete, inxi is on version 3.2.02 right now. Bugs like this are only meaningful if the poster downloads current inxi and reproduces them on current release. I believe the ssh -C bug was fixed quite a while ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911837 Title: inxi, error "Use of uninitialized value $val2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1911837/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818403] Re: cups-pdf ld.so: object 'libsets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file)
Unfortunately, I can no longer check that. I upgraded to Ubuntu 20.04.1 and the problem no longer exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818403 Title: cups-pdf ld.so: object 'libsets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1818403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901609] Re: signond causes qprocess crash
Tested 8.59+17.10.20170606-0ubuntu2.20.10.1 on groovy and the test scenario outlined in the description is working now. The auth dialog no longer crashes singond. ** Tags removed: verification-needed verification-needed-groovy ** Tags added: verification-done verification-done-groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725681] Re: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Closed ** Changed in: amavisd-milter (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725681 Title: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1725681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725681] Re: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Closing bug report due to bug's nature (seems it was an amavisd-new bug) and no reply from bug reporter. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725681 Title: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1725681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901609] Re: signond causes qprocess crash
Also uploaded to groovy and focal as 8.59+17.10.20170606-0ubuntu2.20.10.1 and 8.59+17.10.20170606-0ubuntu2.20.04.1 respectively ** Changed in: signon (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: signon (Ubuntu Groovy) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901609 Title: signond causes qprocess crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 992464] Re: Menu not accessible when run via ssh xforwarding
I'm seeing the same problem with gnome-mines over SSH from 20.04 to 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/992464 Title: Menu not accessible when run via ssh xforwarding To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/992464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901609] Re: signond causes qprocess crash
** Description changed: - I'm reporting this bug upstream from where I found it, since I've - learned that the signond package in KDE Neon is sourced from Ubuntu - focal. + [Impact] + + Without the patch users are unable to add google accounts because signond crashes. + This prevents users from using KDE's online accounts feature for google. + The fix for this is to drop the no-rtti compile flag as qprocess relies on type info. This has no real downside for the user as it simply brings in type info. + + [Test Case] + + - in a plasma session + - install kio-gdrive + - run `systemsettings5 kcm_kaccounts` + - add a new account + - click on google + - wait for login window to appear + - signond shouldn't be crashing + + [Where problems could occur] + + Cannot think of any. It simply adds type info to the objects. Also + upstream has rtti disabled for months and I'm not aware of any problems. + + [Other Info] + + This is a fairly grave issue as far as user experience is concerned. + + + + + + I'm reporting this bug upstream from where I found it, since I've learned that the signond package in KDE Neon is sourced from Ubuntu focal. This was found in signon (signond_8.59+17.10.20170606-0ubuntu2_amd64) from Focal Fossa Steps to reproduce: 1. Install KDE Plasma and qt 5.15.0 on Ubuntu focal base (IE: KDE Neon) 2. Install the kaccounts integration and kio-gdrive packages. 3. Open System settings and navigate to "Online Accounts" 4. Press "+ Add New Account" 5. Select "Google" Observed behaviour: - Window that would ask for authentication fails to load, and Online Accounts goes back to overview - system logs show a segfault in libqt5core.so which can be traced to a failure in qporcess, casued by signond (see links for further details) - Expected behaviour: + Expected behaviour: - New window opens with a webview where Google authentication credentials can be posted. - When qprocess runs it does not crash. - Further reference information at the following links: 1. Bug in KDE Neon: https://bugs.kde.org/show_bug.cgi?id=426034 3. Relevant MR (Since merged) in signond: https://gitlab.com/accounts- sso/signond/-/merge_requests/27 ** Also affects: signon (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: signon (Ubuntu Groovy) 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/1901609 Title: signond causes qprocess crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1901609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584180] Re: new version 1.6.1 out since 2015-05-24
Waiting for new Debian release ** Changed in: amavisd-milter (Ubuntu) Status: Confirmed => In Progress ** Changed in: amavisd-milter (Ubuntu) Assignee: (unassigned) => Harald Jenny (harald-a-little-linux-box) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584180 Title: new version 1.6.1 out since 2015-05-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1584180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1691707] Re: amavisd-milter timing issue on startup
Waiting for new Debian release ** Changed in: amavisd-milter (Ubuntu) Status: Confirmed => In Progress ** Changed in: amavisd-milter (Ubuntu) Assignee: (unassigned) => Harald Jenny (harald-a-little-linux-box) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1691707 Title: amavisd-milter timing issue on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1691707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725681] Re: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Dear Kees van Iwaarden, I don't know if your bug report is still valid could you confirm that with a current version the problem persists? Kind regards Harald Jenny -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725681 Title: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1725681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725681] Re: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd
Look if problem is still an issue. ** Changed in: amavisd-milter (Ubuntu) Status: New => In Progress ** Changed in: amavisd-milter (Ubuntu) Assignee: (unassigned) => Harald Jenny (harald-a-little-linux-box) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725681 Title: package amavisd-milter 1.5.0-5 failed to install/upgrade: vereistenproblemen - blijft ongeconfigureerd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-milter/+bug/1725681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904195] Re: apt cancels holds on uninstalled packages
Huh, so you can, thanks. Confirming that this works too, and agreed that that looks like it should cover all cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904195 Title: apt cancels holds on uninstalled packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1904195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904195] Re: apt cancels holds on uninstalled packages
My understanding of pinning is that that can be used to specify which version to use, which is what I use it for already, but not to force no version to be used. Agreed that this is not a common use case, so low prio and not patching it till it's fixed upstream makes sense, but since it's something I don't have a good alternative for, I have locally just built a modified dpkg to get this working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904195 Title: apt cancels holds on uninstalled packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1904195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904195] Re: apt cancels holds on uninstalled packages
You're right btw that it's a dpkg bug, but it's a bit more subtle. The
cleanup that dpkg performs after installation is meant to preserve the
hold state for non-installed packages. This is handled by the
pkg_is_informative function, which classifies everything with "pkg->want
!= PKG_WANT_UNKNOWN" as informative, so would actually preserve hold for
non-installed packages. However, pkg_parse_verify contains logic to fix
up state left by older dpkg versions, without taking into account that
this also includes valid state by current dpkg versions:
/* XXX: Mark not-installed leftover packages for automatic removal on
* next database dump. This code can be removed after dpkg 1.16.x, when
* there's guarantee that no leftover is found on the status file on
* major distributions. */
if (!(ps->flags & pdb_recordavailable) &&
pkg->status == PKG_STAT_NOTINSTALLED &&
pkg->eflag == PKG_EFLAG_OK &&
(pkg->want == PKG_WANT_PURGE ||
pkg->want == PKG_WANT_DEINSTALL ||
pkg->want == PKG_WANT_HOLD)) {
pkg_set_want(pkg, PKG_WANT_UNKNOWN);
}
We are now at dpkg 1.20.x, well after 1.16.x. If this block of code is
removed (or at least the pkg->want == PKG_WANT_HOLD condition), direct
installation by dpkg works as expected, and presumably installation
using apt will work as expected as well.
** Also affects: dpkg (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/1904195
Title:
apt cancels holds on uninstalled packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904195/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904195] Re: apt cancels holds on uninstalled packages
Whether it's a bug in apt or in something used by apt doesn't really make a difference from an end user perspective. Can this bug be reopened as a dpkg bug, then, or should I report that as a new bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904195 Title: apt cancels holds on uninstalled packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904195] [NEW] apt cancels holds on uninstalled packages
Public bug reported: When a package is not installed and apt dist-upgrade offers to install it, if this is not desired, it is possible to hold the package using multiple tools, which puts it in a state documented in dpkg.1 as: hold A package marked to be on hold is kept on the same version, that is, no automatic new installs, upgrades or removals will be performed on them, unless these actions are requested explicitly, or are permitted to be done automatically with the --force-hold option. Note the "no automatic new installs", suggesting that this is a correct and valid use for packages that are not installed. I use "apt-mark hold" to put packages in this state. This is respected by apt when choosing what to install, but any installation causes this state to be lost for uninstalled packages, even installations of completely unrelated packages. Steps to reproduce: - Add a repository to sources.list that adds new essential packages, and run `apt update`. - Observe that `apt dist-upgrade` will want to install new packages. - Put the packages on hold, using `apt-mark hold `. - Observe that `apt dist-upgrade` will no longer want to install new packages. - Install an unrelated package. - Observe that `apt dist-upgrade` will again want to install new packages. Seen on Ubuntu 20.10, apt 2.1.10. ** Affects: apt (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/1904195 Title: apt cancels holds on uninstalled packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1904195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899483] Re: long hang apt install mariadb-server on Ubuntu 20.04 server
I hade this same problem. Apparently an on apparmor profile left behind
of an old mysql install. This fixed it for me;
echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
systemctl restart mariadb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899483
Title:
long hang apt install mariadb-server on Ubuntu 20.04 server
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.3/+bug/1899483/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899192] Re: inxi 3.1.07-1-1 does not report Desktop version
This apparently has been going on in ubuntu for longer than I realized, I assume one of the fallback tests which used to work must now be failing. Added more filters for these types of changes, and re-ordered some of the detection for gnome to avoid a case where it is gnome but it fails the detection due to unknown values in the id, like ubuntu:, although that specific instance is now filtered out. this update is in pinxi [inxi-perl branch of inxi] but I don't know when it will go out, maybe sooner than later to hit the 20.10 non beta release. These kinds of silly changes are without a question my number one pet peeve with the entire linux ecosystem, distros, random pointless string value changes done for no good reason, and never considering that tools might actually be USING the data that those strings and variables contain. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899192 Title: inxi 3.1.07-1-1 does not report Desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1899192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899192] Re: inxi 3.1.07-1-1 does not report Desktop version
this is a regression in the beta 20.10 gnome ubuntu desktop ID. It is not possible to know if they will correct this regression or not. the value $GDMSESSION should be 'gnome' but is 'ubuntu', that is completely wrong, GDMSESSION is supposed to identify the gnome desktop, not the distro name. This is bug one in the beta. bug two is similar: $XDG_CURRENT_DESKTOP has likewise been corrupted, leading to a secondary detection failure: ubuntu:GNOME the ubuntu name string has no business being in there, but that one is easier to correct. The corruption in $GDMSESSION I suspectc is a straight beta bug, and should be reported to ubuntu since it's just wrong, ubuntu is NOT the gdmsession owner, GNOME is. This issue is invalid because it is relating to beta release ubuntu and we have no way of knowing if these two regressions are going to remain in the final release, or if they were just working ideas that will be removed, as they should be, since they break all existing detection methods, and serve no valid purpose. Note that I realized that it would be largely a waste of time trying to get actual debugging data from the issue poster, so I grabbed the beta iso and ran it in a vm, but I will NOT normally do this because it's a waste of my time, so in this case, it was which would waste less of my time. I do not normally track launchpad issues, nor should it be used for beta release issues since those are beta, not final, release, and thus by definition invalid until confirmed by ubuntu to be the final idea, which I hope it isn't since it just adds another pointless layer of complexity to desktop detection. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899192 Title: inxi 3.1.07-1-1 does not report Desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1899192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899192] Re: inxi 3.1.07-1-1 does not report Desktop version
File an issue, as I already told you, on https://github.com/smxi/inxi about the desktop issue. This requires data and discussion, and launchpad is the wrong place for that. I cannot reproduce your system, nor do I have any actual idea of what you are doing to lead to desktop detection failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899192 Title: inxi 3.1.07-1-1 does not report Desktop version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1899192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896071] Re: inxi 3.1.06-1-1 does not report Compiler an Desktop
Please DO NOT tack on totally unrelated issues, the desktop has NOTHING to do with the compiler. The compiler issue is fixed. If you have other issues, file an issue on github inxi, the desktop logic is totally unrelated, and can be quite complicated to debug, certainly not an appropriate issue for launchpad, file it where it will make a difference: https://github.com/smxi/inxi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896071 Title: inxi 3.1.06-1-1 does not report Compiler an Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1896071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
https://www.kernel.org/doc/Documentation/rtc.txt just a bit of info on rtc drivers. While rtc is something, it's not necessarily the cmos battery, it's just a chip that the system can use to determine time. So it would not be a cmos battery it would be an RTC battery, since there would be no way for inxi to know what it was, there can be more than one for example. This bit of data is unlikely to make it into inxi I have to admit since I would need to see much more information about variation and > 1 rtc systems and systems where the battery was dead or whatever else can happen, but in no case would it be a cmos battery state, it would be an rtc chip state, but, again, since I have no real data on this, no examples of complex systems, etc, it's unlikely this will be added. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
Then there is no data available, which means the issue is not valid, nor is there anything indicating that that data is available. As an aside I do not remember ever seeing CMOS battery state listed when testing or checking inxi -Bx results or datasets, usually the Device-x: battery states belong to things like wifi mice, keyboards, and other external battery driven devices that report their battery state to the linux system. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
As an aside, if you have a feature request, file it on https://github.com/smxi/inxi otherwise it won't really make any difference since I don't routinely follow distro issue trackers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898829] Re: CMOS-battery status missing in "inxi -B"
This is not a valid issue, and it's not a bug. Also, the poster didn't read the help/man at all, since to see other device batteries listed, you have to use -Bx, not -B alone. -B alone only shows results for laptop batteries, basically. If -Bx does not show the cmos battery, then inxi can't find it, the data is not anywhere it can locate. If -Bx shows the device battery then obviously the issue is completely invalid in the first place, and if it doesn't, it means inxi has no access to it, which means the issue is invalid. /proc is not used to get battery data, that comes from /sys. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898829 Title: CMOS-battery status missing in "inxi -B" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1898829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898517] [NEW] kontact packages for data export / import missing in respository
Public bug reported: lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 Hi It is not possible in kontact of kubuntu 20.04 to export or import pim-data. E.g. the packages for pim-data-exporter and program pimsettingexporter are not available in respositories. Thanks for help, Harald ** Affects: kontact (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/1898517 Title: kontact packages for data export / import missing in respository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kontact/+bug/1898517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898293] [NEW] Boot partition too small for snapshotting
Public bug reported: RUnning the 20.04 desktop zfs install, the boot partition is 500 MiB I run 512 MiB without zfs because the default 234 MiB has been too small for a long time, like two years 500 MiB is too little because snapshotting is taking place. boot cannot hold even two kernels macOS boots from a single container that can have any number of installations That would be a better solution for zfs, to have a single pool where any number of bootable installations can coexists, each with their own boot area and encrypted root file system Get-around: # delete all boot snapshots so system, upgrades may complete: zfs list -H -o name -t snapshot -r bpool | xargs -n1 zfs destroy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 2 13:26:21 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2020-08-14 (48 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898293 Title: Boot partition too small for snapshotting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896071] Re: inxi 3.1.06-1-1 does not report Compiler an Desktop
This issue is resolved in the pinxi branch, and will be in next inxi, 3.1.07, whenever that comes out, probably soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896071 Title: inxi 3.1.06-1-1 does not report Compiler an Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1896071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896071] Re: inxi 3.1.06-1-1 does not report Compiler an Desktop
This is caused by a syntax change in /proc/version Since I had no /proc/version for ubuntu I had to guess, the issue was resolved for the distros that I got to see samples from, but I have yet to see a /proc/version output for ubuntu kernel 5.8. Note this is NOT a bug in inxi because the syntax in question has been stable ever since inxi offered the compiler version for kernel, this was a change done for unknown reasons, and in a non standard manner, and will require more /proc/version samples from different distros to fully cover. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896071 Title: inxi 3.1.06-1-1 does not report Compiler an Desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1896071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869363] Re: Marco dies now and then when closing a window.
*** This bug is a duplicate of bug 1871716 *** https://bugs.launchpad.net/bugs/1871716 It still dies on me sometimes when I close a window. [618245.509958] marco[611813]: segfault at 8000fc ip 7f91df0bd9d4 sp 7ffd2d419dc8 error 4 in libcairo.so.2.11600.0[7f91df06a000+cf000] [618245.509964] Code: 41 5c c3 0f 1f 00 4c 89 e7 4c 8d 25 a6 14 08 00 e8 31 ff ff ff eb e1 0f 1f 80 00 00 00 00 e9 23 fc ff ff 0f 1f 00 f3 0f 1e fa <8b> 47 04 85 c0 74 05 31 c0 c3 66 90 48 83 c7 08 e9 27 e9 fa ff 0f -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869363 Title: Marco dies now and then when closing a window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869363] Re: Marco dies now and then when closing a window.
This is getting progressively worse. Every two close of a window crashes the window-manager. So much so I had to create an icon for starting marco, since it isn't re-starting itself anymore. And every time it dies, all windows get shifted some tens of pixels downwards. It feels like sweatpants fighting against gravity. $ dmesg|grep marco [2752234.819367] marco[2202175]: segfault at 147 ip 7f885c0569d4 sp 7ffc5d412f18 error 4 in libcairo.so.2.11600.0[7f885c003000+cf000] [2752314.195043] marco[2355101]: segfault at 7ed ip 7f47e78a89d4 sp 7ffdaab440b8 error 4 in libcairo.so.2.11600.0[7f47e7855000+cf000] [2753080.406368] marco[2356005]: segfault at 5c000c1 ip 7fdc7bbf09d4 sp 7fff6e87d5f8 error 4 in libcairo.so.2.11600.0[7fdc7bb9d000+cf000] [2753138.170552] marco[2360430]: segfault at 5c00055 ip 7ffb290a29d4 sp 7fffa626d1a8 error 4 in libcairo.so.2.11600.0[7ffb2904f000+cf000] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869363 Title: Marco dies now and then when closing a window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
I can confirm THAT also: root@Scotty:~# update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu I: The initramfs will attempt to resume from /dev/sdc3 I: (UUID=0d56817f-d127-457b-b6e1-5fd642a9520b) I: Set the RESUME variable to override this. So this doesn't has to do anything with 3rd-Party-PPA's because I don't have any. It's after a fresh install. BUT update-initramfs doesn't throw any error anymore and runs through to the end. There are only the warnings left. The system works well with this, after a reboot there are no problems despite these warnings: root@Scotty:/boot# ll insgesamt 189597 drwxr-xr-x 4 root root 4096 Mai 18 08:08 ./ drwxr-xr-x 20 root root 4096 Mai 16 17:27 ../ -rw-r--r-- 1 root root 237718 Apr 20 18:33 config-5.4.0-26-generic -rw-r--r-- 1 root root 237718 Apr 29 15:34 config-5.4.0-29-generic drwx-- 3 root root 512 Jan 1 1970 efi/ drwxr-xr-x 4 root root 4096 Mai 16 17:33 grub/ lrwxrwxrwx 1 root root 27 Mai 16 17:33 initrd.img -> initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 80142634 Mai 16 17:31 initrd.img-5.4.0-26-generic -rw-r--r-- 1 root root 80142137 Mai 18 08:08 initrd.img-5.4.0-29-generic lrwxrwxrwx 1 root root 27 Mai 16 17:25 initrd.img.old -> initrd.img-5.4.0-26-generic -rw-r--r-- 1 root root 182704 Feb 14 00:09 memtest86+.bin -rw-r--r-- 1 root root 184380 Feb 14 00:09 memtest86+.elf -rw-r--r-- 1 root root 184884 Feb 14 00:09 memtest86+_multiboot.bin -rw--- 1 root root 4736015 Apr 20 18:33 System.map-5.4.0-26-generic -rw--- 1 root root 4736015 Apr 29 15:34 System.map-5.4.0-29-generic lrwxrwxrwx 1 root root 24 Mai 16 17:33 vmlinuz -> vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 11657976 Apr 23 09:55 vmlinuz-5.4.0-26-generic -rw--- 1 root root 11657976 Apr 29 15:54 vmlinuz-5.4.0-29-generic lrwxrwxrwx 1 root root 24 Mai 16 17:33 vmlinuz.old -> vmlinuz-5.4.0-26-generic root@Schrotty:/boot# uname -a Linux Scotty 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux root@Scotty:/boot# date Mo 18. Mai 08:14:51 CEST 2020 The initrd.img-5.4.0-29-generic was built successfully an works well and the amdgpu is loaded, if it works or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
I can confirm that a clean install on a newly formatted device on a box (which was affected by this problem) runs fine now. The used box is an older intel i7-2600 CPU (8 cores) with an also older Radeon R9 285/380. The amdgpu module _is_ loaded as lsmod shows, but the installation itself and the update to 5.4.0-29-generic by the installer runs without any error by update-initramfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
Sorry, I meant Bug #1869053 of course. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
With the new kernel 5.4.0.29 the missing modules are foubd obviusly, so the Installer runs well and finishes normally. So, also Bug 1873325 was fixed for me, just tested on the same HW with a fresh install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869053] Re: Ubuntu 20.04 daily (25.03.2020) installer crashes
I also can confirm that the Installation works now on the same HW which had the Error(s) before. As there are the amdgpu modules found now with kernel 5.4.0.29, I firmly believe that the bug 1873325 was the originator. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869053 Title: Ubuntu 20.04 daily (25.03.2020) installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869053] Re: Ubuntu 20.04 daily (25.03.2020) installer crashes
Verified also for LTS stable release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869053 Title: Ubuntu 20.04 daily (25.03.2020) installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
I'm also affected by ths bug. This may also be connected to bug #1869053 (https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869053), which happens on the same box during install. Graphics card is an older Radeon R9. Apport and lspci output is attached. ** Attachment added: "sysinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325/+attachment/5365682/+files/sysinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869053] Re: Ubuntu 20.04 daily (25.03.2020) installer crashes
May be connected to https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325 Please see my comment there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869053 Title: Ubuntu 20.04 daily (25.03.2020) installer crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1869053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874892] [NEW] Installation of new, clean system crashed twice
Public bug reported: During fresh install, from USB medium, the installation crashed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 20:55:36 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash oem-config/enable=true --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=nl_NL.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874892 Title: Installation of new, clean system crashed twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1874892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340106]
Git commit f40191a147c9643717fda1cf9d1f42c526550893 by Harald Sitter. Committed on 06/04/2020 at 09:27. Pushed by sitter into branch 'master'. smb: add hack to support spaces in workgroup names Summary: workgroup names are as best I can tell always still netbios names which means they can contain a bunch of characters ordinarily not found in valid host names. e.g. spaces this causes trouble with the IANA SMB URI draft, as used by libsmbc, since the workgroup would be the host field of the RI when browsing a workgroup (i.e. filtering hosts that are member of a given workgroup) because QUrl does not allow invalid hostnames in the host field. to bypass this problem we now put the workgroup name into the query of the url as `kio-workgroup`, should it cause trouble in the host field. SMBUrl takes this query into account when constructing the url for smbc. since the latter has uniquely exciting potential for breakage this entire dance is only done when absolutely necessary and otherwise we continue with all the same code and behavior as without this commit. on a side note: the awkward name flexibility seems to not extend to computer names anymore (supposedly because of LLMNR) so this entire use case is already very niche as we (and libsmbclient) currently only support workgroup browsing for NT1 networks, and NT1 is by default not supported on windows10 or samba. FIXED-IN: 20.04 Test Plan: builds, test passes, can browse workgroup with space in name Reviewers: ngraham Subscribers: kde-frameworks-devel, kfm-devel, thiago Tags: #dolphin, #frameworks Differential Revision: https://phabricator.kde.org/D27804 M +35 -0smb/autotests/smburltest.cpp M +11 -1smb/kio_smb_browse.cpp M +57 -4smb/smburl.cpp https://commits.kde.org/kio- extras/f40191a147c9643717fda1cf9d1f42c526550893 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340106 Title: Dolphin & Konqueror do not support browsing workgroups with spaces in their name To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/340106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870307] Re: fsckd is executed and the system freezes
Sorry, I couldn't find a package for fsckd that I was sure would be correct to name this package. This appears to be a service that consists of the following components: "systemd-fsckd.service, systemd-fsckd.socket, systemd-fsckd - File system check progress reporting" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870307 Title: fsckd is executed and the system freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870307] [NEW] fsckd is executed and the system freezes
Public bug reported: I'm using Ubuntu 18.04.4 LTS, Kernel Linux 4.15.0-91-generic (x86_64), Version # 92-Ubuntu SMP Fri Feb 28 11:09:48 UTC 2020. My system is installed on an SSD. My current session is interrupted once a week. A black screen appears with the following message: /dev/nvme0n1p2: clean, 1159263/60497920 files, 29005368/241961984 blocks fsckd-cancel-msg: Press Ctrl + C to cancel running file system checks. (The numbers may vary from week to week) There are the following problems: 1. The process cannot be interrupted by pressing Ctrl + C. [Error] 2. The user receives no progress information about what the system is doing. [Improvement suggestion] 3. The process remains in this status even if you wait several hours. [Error] 4. The system can only be restarted by a hardware-reset. Hints: nvme0n1 is my SSD nvme0n1p1 contains / boot / efi The root directory is in nvme0n1p2 / In nvme0n1p3 is [SWAP] ** Affects: ubuntu Importance: Undecided Status: New ** Tags: fsckd -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870307 Title: fsckd is executed and the system freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1870307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340106]
https://phabricator.kde.org/D27804 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340106 Title: Dolphin & Konqueror do not support browsing workgroups with spaces in their name To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/340106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869363] [NEW] Marco dies now and then when closing a window.
Public bug reported: Every now and then when I close a window marco dies. Luckily it gets restarted very quickly so I don't get thrown out of my session, the windows don't even have time to re-arrange themselves to one desktop. [584024.122730] marco[1436295]: segfault at 4e00048 ip 7ff5a55f79d4 sp 7ffdb21767a8 error 4 in libcairo.so.2.11600.0[7ff5a55a4000+cf000] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: marco 1.24.0-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 27 14:18:52 2020 InstallationDate: Installed on 2010-11-05 (3429 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: marco UpgradeStatus: Upgraded to focal on 2020-03-20 (6 days ago) ** Affects: marco (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1869363 Title: Marco dies now and then when closing a window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1869363/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I too had this problem in 18.04, and now in 20.04. I am unable to use the headphones for conferencing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553669 Title: Annoying "call from" message when connecting Bose devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340106]
Thanks. With that in mind we cannot really support spaces while also following the smb URI format [1]. I suppose we'll just have to deviate a bit iff the workgroup name contains a space by using a variant of the notation that stuffs the workgroup into the userinfo `smb://work group;@/` and then translate that back to an smb URI for libsmbclient again. Means the urls wont be portable but at least navigation within our tech works. [1] https://www.iana.org/assignments/uri-schemes/prov/smb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340106 Title: Dolphin & Konqueror do not support browsing workgroups with spaces in their name To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/340106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340106]
CCing David Faure for some input
This is either a bug in QUrl or not a bug at all.
We do
```
QUrl u("smb://");
u.setHost(dirpName);
```
to which QUrl says
> Invalid hostname (contains invalid characters); source was \"FOO BAR\";
> scheme = \"smb\", host = \"\"
https://tools.ietf.org/html/rfc3986#section-3.2
defines host as
> host = IP-literal / IPv4address / reg-name`
of which the only relevant group for the bug is reg-name:
> reg-name= *( unreserved / pct-encoded / sub-delims )
of which no group would allow for spaces except for pct-encoded, assuming the
space is percent-encoded of course.
Which would make this a QUrl bug if the RFC didn't also explicitly say:
> URI producing
> applications must not use percent-encoding in host unless it is used
> to represent a UTF-8 character sequence.
I **think** that is meant to say that one must not percent-encode if the
character is plain ASCII, so by extension a space cannot be part of reg-
name at all.
OTOH I ran smb://FOO%20BAR/ through a bunch of other rfc3986/7
implementation and they all found it to be perfectly valid.
So, I am really not sure.
Iff spaces cannot be expressed, then spaces in workgroup and domains are
probably not supportable as it'd impair URI portability. Also QUrl would
then be behaving correctly in declaring the URI invalid, and we use QUrl
all over the place, so that'd be a bit of a problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/340106
Title:
Dolphin & Konqueror do not support browsing workgroups with spaces in
their name
To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/340106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811087] Re: [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary
Hm, I just figured out that I missed the last really useful comment because I did not get an e-mail about it. Anyway, https://github.com/lxc/lxc/issues/3186 now explains in more detail how to quickly build fuidshift from source. Thank you, Stéphane! ** Bug watch added: LXC bug tracker #3186 https://github.com/lxc/lxc/issues/3186 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811087 Title: [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1811087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851113] [NEW] equivs-build fails to create DEB package w/o reporting an error
Public bug reported: I used equivs in the past to build meta packages to ensure that certain packages are installed on my systems. This always worked well. With the Ubuntu 19.10, I am unable to build any meta package with equivs even though the program does not report any error. Running "equivs-build control" in ~/build using the attached demo control file results in the following output: dh_testdir dh_testroot dh_prep dh_testdir dh_testroot dh_install dh_installdocs dh_installchangelogs dh_compress dh_fixperms dh_installdeb dh_gencontrol dh_md5sums dh_builddeb dpkg-deb: building package 'test-deb' in '../test-deb_1_all.deb'. The package has been created. Attention, the package has been created in the current directory, not in ".." as indicated by the message above! However, no DEB package is created at all. Neither in the ~/ nor in ~/build nor anywhere else. ** Affects: equivs (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Demo control file" https://bugs.launchpad.net/bugs/1851113/+attachment/5302427/+files/control -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851113 Title: equivs-build fails to create DEB package w/o reporting an error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/equivs/+bug/1851113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1834480] [NEW] translations in not so ideal language-pack
Public bug reported: currently translations go into language-pack-gnome-$lang-base. this isn't particularly ideal since pwquality is also used by kde plasma's user manager which then also drags in all unrelate gnome software translations. pwquality is desktop independent and it'd be really grand if its translations could be moved to the desktop independent language- packs. ** Affects: libpwquality (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/1834480 Title: translations in not so ideal language-pack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpwquality/+bug/1834480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832624] Re: [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs
Here is a backport done against git clone git://kernel.ubuntu.com/ubuntu/ubuntu-bionic --branch master-next --single-branch Please note, I just did the technical backport without any compiler involvement or similar. However, as I am the owner of this code, it should apply and compile cleanly. regards Harald Freudenberger ** Patch added: "s390-zcrypt-Fix-wrong-dispatching-for-control-domain.ubuntu_bionic.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832624/+attachment/5273391/+files/s390-zcrypt-Fix-wrong-dispatching-for-control-domain.ubuntu_bionic.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832624 Title: [UBUNTU] kernel: Fix wrong dispatching for control domain CPRBs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1832624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827486] Re: Weather data failure
This is not a bug, the weather source that was in inxi 2.x and 3.0.31 and earlier is gone. The only fix for weather is to update to current inxi (3.0.33 in ubuntu, and 3.0.34 in master branch of github inxi). The reason later versions work is because they point to a new weather data source. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827486 Title: Weather data failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inxi/+bug/1827486/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
Was there a question in there? I did also see this on installed kubuntu systems, it's just far harder to reproduce there because of the racy nature of the issue. In fact, the only reason I know about the issue is because the colors are just so far off that they tripped up our openqa tests and flaked every so often. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728012] Re: Many 3rd party scanner drivers are broken by a sane change
I have with the multifunction printer Samsung CLX-3185N and Simple Scan
the following problem:
After starting Simple Scan, I can scan the 1st page; every other page no
longer. Error message: "Scan failed Scan failed to start."
What have I done so far:
Linux unified driver uld_V1.00.39_01.17.tar.gz downloaded from Samsung
through HP website and unpacked in my download directory.
Then the command
sudo ~ / downloads / uld / install.sh
called and installed the driver. There were no error messages.
Since the scanner was not recognized at the beginning, I created the
following links.
sudo ln -sfv /usr/lib/sane/libsane-smfp.so* / usr / lib / x86_64-linux-
gnu / sane
Now the scanner is found with sane-find-scanner and scanimage -L; but
that above Problem occurs now.
I tested the following before calling Simple-Scan:
haraldbraun @ Fulda: ~ $ lsusb | grep -e samsung
Bus 001 Device 005: ID 04e8: 343d Samsung Electronics Co., Ltd
haraldbraun @ Fulda: ~ $ sudo sane-find-scanner
Found USB scanner (vendor = 0x04e8 [Samsung Electronics Co., Ltd.], product =
0x343d [CLX-3180 Series]) at libusb: 001: 005
haraldbraun @ Fulda: ~ $ scanimage -L
device `smfp: usb; 04e8; 343d; Z52IBAIB600104R 'is a Samsung CLX-3180 series on
USB scanner
haraldbraun @ Fulda: ~ $ ls -al / dev / bus / usb / 001/005
crw-rw-r - + 1 root lp 189, 4 Mar 17 08:00 / dev / bus / usb / 001/005
haraldbraun @ Fulda: ~ $ groups
Harald Brown Lp Sudo Backup Lpadmin Scanner Saned Public
haraldbraun @ Fulda: /etc/udev/rules.d$ ls -l
a total of 68
-rwxr-xr -x 1 root root 5666 Mar 16 17:56 39-smfp_samsung.rules
-rw-r - r-- 1 root root 58549 Feb 18 11:28 70-snap.core.rules
In 39-smfp_samsung.rules ist der Multifunktionsdrucker wie folgt
aufgeführt (Datei-Auszug):
# This file is a part of Unified Linux Driver
# Rules to allow low level USB device access for smfpautoconf
#
# For new distributions,
# Permissions and group are set according to common libsane rules
#
ACTION!="add", GOTO="smfp_label_end"
# Check device type
ENV{DEVTYPE}=="usb_device", GOTO="smfp_create_usb_dev"
# Check SUBSYSTEM (should be either "usb" or "usb_device")
SUBSYSTEM=="usb", GOTO="smfp_create_usb_dev"
SUBSYSTEM=="usb_device", GOTO="smfp_create_usb_dev"
GOTO="smfp_label_end"
LABEL="smfp_create_usb_dev"
# Check Vendor ID
ATTR{idVendor}!="04e8", GOTO="smfp_label_end"
ATTRS{idProduct}=="3425", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="341c", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="342a", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="343d", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="3456", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="345a", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="3427", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="343a", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="3428", ENV{libsane_matched}="yes"
ATTRS{idProduct}=="343b", ENV{libsane_matched}="yes"
<==
ATTRS{idProduct}=="3455", ENV{libsane_matched}="yes"
.
.
.
ENV{libsane_matched}=="yes", OWNER="root", MODE="664", GROUP="lp"
LABEL="smfp_label_end"
Then I have the command in the terminal:
sudo tail -f / var / log / syslog
entered, Simple-Scan started.
The first start attempt of Simple-Scan fails.
The second start attempt succeeds; I then did the following activities:
- 1st picture scanned in (successfully)
- scanned the following image (failure, with o.a.
- Simple scan ends without saving
- tail finished.
The syslog excerpt is listed below:
haraldbraun@Fulda:~$ sudo tail -f /var/log/syslog
[sudo] Passwort für haraldbraun:
Mar 17 09:50:17 Fulda kernel: [11120.507310] usb 1-12: new high-speed USB
device number 6 using xhci_hcd
Mar 17 09:50:18 Fulda kernel: [11120.656159] usb 1-12: New USB device found,
idVendor=04e8, idProduct=343d
Mar 17 09:50:18 Fulda kernel: [11120.656165] usb 1-12: New USB device strings:
Mfr=1, Product=2, SerialNumber=3
Mar 17 09:50:18 Fulda kernel: [11120.656169] usb 1-12: Product: CLX-3180 Series
Mar 17 09:50:18 Fulda kernel: [11120.656173] usb 1-12: Manufacturer: Samsung
Electronics Co., Ltd.
Mar 17 09:50:18 Fulda kernel: [11120.656176] usb 1-12: SerialNumber:
Z52IBAIB600104R
Mar 17 09:50:18 Fulda kernel: [11120.657637] usblp 1-12:1.1: usblp1: USB
Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04E8 pid 0x343D
Mar 17 09:50:18 Fulda upowerd[1235]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb1/1-12/1-12:1.1
Mar 17 09:50:18 Fulda upowerd[1235]: unhandled action 'bind' on
/sys/devices/pci:00/:00:14.0/usb1/1-12
Mar 17 09:50:19 Fulda color
[Bug 1819487] Re: sshd crashed on s390x with hw crypto enabled
enough ffdc data Thanks This happens at ibmca destruction time. Looks like there is some kind of double free or so in the destructor for the ibmca engine. We had some issues like this in the past already. I'll have a look onto the code ... Thanks Frank and Xnox regards Harald Freudenberger -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819487 Title: sshd crashed on s390x with hw crypto enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1819487/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818403] [NEW] cups-pdf ld.so: object 'libsets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file)
Public bug reported: I'am using: -Ubuntu 18.04.2 LTS -printer-driver-cups-pdf 3.0.1-5 -thunderbird 1:60.5.1+build2-0ubuntu0.18.04.1 No directory /usr/share/doc/cups-pdf If I want to create a mail as Generic-Cups PDF-Printer under Thunderbird 60.5.1 (64-Bit), the error message "ld.so: object 'libsets_pac.so' from /etc/ld.so.preload can not be preloaded (can not open shared object file)" Appears in the printer selection menu after the entry Generic- Cups-PDF-Printer. What measures have I tried: 1. Search for file libesets_pac.so. I found it under /usr/lib/x86_64-linux-gnu. 2. Open the file /etc/ld.so.preload as root and prefix the path with 1.. File saved and service CUPS restarted. Episode: 1. When first printing a Thunderbird mail after the service restarta in the printer selection menu behind Generic Cups PDF Printer NO error message. 2. Each time you print a Thunderbird email, the Error message again. PS: Translated from german to english by Google Translator ** Affects: cups-pdf (Ubuntu) Importance: Undecided Status: New ** Attachment added: "20190303_cups-pdf_statusmessage.png" https://bugs.launchpad.net/bugs/1818403/+attachment/5243062/+files/20190303_cups-pdf_statusmessage.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818403 Title: cups-pdf ld.so: object 'libsets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1818403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777994] Re: the header xcb/xinput.h is missing
uploaded bionic SRU libxcb_1.13-1.1 by Jonathan Riddell ** Description changed: - I suspect this means there should be another package, libxcb-xinput-dev - perhaps? + [Impact] + Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. + + [Test Case] + Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. + + [Regression Potential] + None that I can see, it's just packaging a few new header files. + + + + + I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: - Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: Lenovo UHD Graphics 620 [17aa:3802] + Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. - Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. - Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. + Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. + Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Changed in: libxcb (Ubuntu Bionic) Status: Won't Fix => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815368] [NEW] Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side
Public bug reported: At first this may not sound like much of a issue, but this tiny white border actually makes it look like there's something wrong with the Ubuntu dock/panel or like the screen is shifted 1 pixel to the right. If the user has automatic wallpaper change enabled it may not be obvious that the issue is only the wallpaper. Either way, it makes this otherwise beautiful wallpaper that is shipped with 18.04 unpleasant. See the attached picture, the issue is even more noticeable on a highres. screen. ** Affects: wallpaper (Ubuntu) Importance: Undecided Status: New ** Attachment added: "White 1px border" https://bugs.launchpad.net/bugs/1815368/+attachment/5237508/+files/white_border.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815368 Title: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallpaper/+bug/1815368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815368] Re: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side
Please see the attached corrected wallpaper. ** Attachment added: "Wall_with_door_on_Gozo_by_Matthias_Niess_FIX.jpg" https://bugs.launchpad.net/ubuntu/+source/wallpaper/+bug/1815368/+attachment/5237509/+files/Wall_with_door_on_Gozo_by_Matthias_Niess_FIX.jpg ** Description changed: At first this may not sound like much of a issue, but this tiny white - border actually makes it look like like there's something wrong with the + border actually makes it look like there's something wrong with the Ubuntu dock/panel or like the screen is shifted 1 pixel to the right. If the user has automatic wallpaper change enabled it may not be obvious that the issue is only the wallpaper. Either way, it makes this otherwise beautiful wallpaper that is shipped with 18.04 unpleasant. See the attached picture, the issue is even more noticeable on a highres. screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815368 Title: Wallpaper "Wall with door on Gozo" has a ugly white 1 pixel border on the left side To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wallpaper/+bug/1815368/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759528] Re: Pressing the F10 shortcut on the desktop opens up the Nautilus menu
Thanks for the reply. I just retested it today and the issue is reproducible in both 18.04 LTS and 18.10, all updated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759528 Title: Pressing the F10 shortcut on the desktop opens up the Nautilus menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1759528/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815100] Re: qemu-user-static needs to binfmt with --fix-binary
Thanks, I've updated the description accordingly. ** Description changed: + [Impact] + + qemu static binaries disadvantageously get their binfmt rule created + without the fix-binary flag. This breaks cross-architecture dockers, + flatpak-builder, chroots and generally most use cases that entail kernel + namespaces or chroots. By default the binfmt module will only open the + interpreter file (e.g. qemu-arm-static for armhf binaries) when the + kernel actually encounters a file for which the interpreter is needed. + This is generally fine, except when the root at the time the file is + encountered is no longer the root of the system (IOW: if / is in fact + /foo on the system then the interpreter will effectively be looked for + in /foo/usr/bin/qemu-arm-static, where it of course does not exist). + This is generally fine for regular interpreters such as python, which + you want to install inside the namespace/chroot if you want to interpret + a python file. Since in qemu's case the interpreter is actually a static + emulator it really must come from the host system and not the + namespace/chroot. No root file system ever comes with an emulator on + board, much less one suitable for the host system. + + As this effectively breaks qemu-based container-use the missing flag + really should get rectified. For example you can't easily cross compile + for arm inside a chroot. Primary example of this is flatpak-builder + which is used to build flatpak bundles. It has cross compilation + capabilities expecting a suitable binfmt setup which will fail with + obscure execvp errors (on account of not being able to open the + interpreter/qemu binary inside the chroot). https://docs.plasma- + mobile.org/AppDevelopment.html#creating-a-flatpak-for-the-phone + + The fix-binary flag of binfmt is meant to specifically deal with this. + The interpreter file (e.g. qemu-arm-static) is loaded when its binfmt + rule is installed instead of when a file that requires it is + encountered. When the kernel then encounters a file which requires that + interpreter it simply execs the already open file descriptor instead of + opening a new one (IOW: the kernel already has the correct file + descriptor open, so possibly divergent roots no longer play into finding + the interpreter thus allowing namespaces/containers/chroots of a foreign + architecture to be run like native ones). + + [Test Case] + + Do note that once successfully loaded, the interpreter likely won't need + opening again. So, testing generally should be done after a cold-boot to + ensure binfmt hasn't already loaded the interpreter. + + $ sudo apt install docker.io qemu-user-static + $ sudo docker run --rm -it armhf/ubuntu /bin/sh + + Without fix-binary this gives an error "exec user process caused 'no such file or directory" (this is referring to the interpreter not being found). + With fix-binary this correctly opens a prompt. + + [Regression Potential] + + Since the file descriptor is always held open I guess memory consumption goes up by a couple bytes. There isn't any opportunity of regression with fix-binary as it simply changes the interpreter file opening from lazy to instant. + There is potential for the actual SRU patch going wrong, which would manifest in the binfmt rules not getting set up correctly (this would be shown by the aforementioned test case though; breaking the rule setup would result in no improvement to the docker run command). + + [Other Info] + I also should point out that the exec() still happens inside the namespace/confinement, so while this essentially loads a file from the host it does not impair security as any confinement restrictions will apply to executable all the same, it is merely the binary data blob that comes from the host. + + - + qemu-user-static in 18.04 invokes update-binfmts without --fix-binary which can break the binfmt emulation when namespaces or chroots are involved. Specifically this defuncts cross compiling when relying on binfmt. Newer versions already set --fix-binary for the static package. It'd be really grand if this was actually SRU'd though. Currently 18.04's binfmt for arm can inobviously fail with obscure errors. Notable example is bubblewrap and flatpak, which will squarely hit this problem 100% of the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815100 Title: qemu-user-static needs to binfmt with --fix-binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815100] [NEW] qemu-user-static needs to binfmt with --fix-binary
Public bug reported: qemu-user-static in 18.04 invokes update-binfmts without --fix-binary which can break the binfmt emulation when namespaces or chroots are involved. Specifically this defuncts cross compiling when relying on binfmt. Newer versions already set --fix-binary for the static package. It'd be really grand if this was actually SRU'd though. Currently 18.04's binfmt for arm can inobviously fail with obscure errors. Notable example is bubblewrap and flatpak, which will squarely hit this problem 100% of the time. ** Affects: qemu (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/1815100 Title: qemu-user-static needs to binfmt with --fix-binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1815100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811087] [NEW] [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary
Public bug reported: lxd-tools used to ship the fuidshift command which is useful for shifting UIDs and GIDs of the container root filesystem in order to convert privileged into unprivileged containers. lxd-tools is now a meta package that will enforce that the lxd snap package is being installed. However, lxd snap (tested: stable channel, version 3.0.3 and 3.9) does not seem to provide fuidshift. To get fuidshift back, I had to forcibly install an older version of lxd-tools: https://ubuntu.pkgs.org/18.04/ubuntu-updates-universe-amd64 /lxd-tools_3.0.3-0ubuntu1~18.04.1_amd64.deb.html Being a replacement also for lxd-tools, lxd snap should ship all binaries that used to be shipped. ** Affects: snap (Ubuntu) Importance: Undecided Status: New ** Tags: fuidshift lxd missing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811087 Title: [cosmic] lxd-tools replaced by lxd snap, which is missing 'fuidshift' binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snap/+bug/1811087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762726] Re: Context menu does not show on passwords fields
A update to Ubuntu received today seems to have fixed the issue. --- $ less /var/log/apt/history.log Upgrade: gedit:amd64 (3.28.1-1ubuntu1, 3.28.1-1ubuntu1.1), libgweather-3-15:amd64 (3.28.1-1, 3.28.2-1~ubuntu18.04.1), gir1.2-gweather-3.0:amd64 (3.28.1-1, 3.28.2-1~ubuntu18.04.1), gnome- shell-common:amd64 (3.28.3-0ubuntu0.18.04.3, 3.28.3-0ubuntu0.18.04.4), gedit-common:amd64 (3.28.1-1ubuntu1, 3.28.1-1ubuntu1.1), gnome- shell:amd64 (3.28.3-0ubuntu0.18.04.3, 3.28.3-0ubuntu0.18.04.4), libgweather-common:amd64 (3.28.1-1, 3.28.2-1~ubuntu18.04.1) --- I'm no longer able to reproduce the issue. It seems to have been fixed by this patch: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762726 Title: Context menu does not show on passwords fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762726] Re: Context menu does not show on passwords fields
If the website has the option to let you see what you enter into the password field then the menu will show. Example: https://mail.protonmail.com/login Running Firefox from the terminal after unsetting GTK_IM_MODULE fixes it: $ unset GTK_IM_MODULE $ firefox Since upgrading to 18.04 I'm unable to use autotype in password managers like KeePassXC, it always enters the wrong password. I quite positive the problem with autotyping is actually caused by this same issue as it skips some characters when the password is hidden, but it do enters it correctly if the website have the option to make the field visible (like in the example above) or after unsetting GTK_IM_MODULE. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762726 Title: Context menu does not show on passwords fields To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767454]
Git commit 55eb68ff63646050311f8b689752ad500246c916 by Harald Sitter. Committed on 07/12/2018 at 12:55. Pushed by sitter into branch 'master'. fallback to dnssd service discovery if smb listDir failed on root Summary: This elevates a problem with newer SMB protocol versions and smbclient not supporting discovery/browsing. when not using older (as in: ancient) protocol versions discovery doesn't work and smb:/ gives no results. By falling back to DNSSD based discovery we can ensure discovery of DNSSD remotes (namely linux and osx) is always working. Windows unfortunately does not support DNSSD and as such will not benefit from this mode of discovery and continue to be unlisted when using a protocol version without browsing support. CHANGELOG: When SMB Discovery is not working (protocol > SMB1) host discovery will now fall back to DNS-SD/Avahi/Bonjour. Related: bug 390551 Test Plan: smb.conf: ``` [global] client min protocol = SMB2 ``` Lists devices Reviewers: #frameworks, #dolphin, broulik Reviewed By: broulik Subscribers: acrouthamel, alexde, bcooksley, ngraham, kde-frameworks- devel, kfm-devel Tags: #dolphin, #frameworks Differential Revision: https://phabricator.kde.org/D16299 M +6-0CMakeLists.txt M +3-0config-runtime.h.cmake M +16 -3smb/CMakeLists.txt M +1-0smb/kio_smb.h M +126 -3smb/kio_smb_browse.cpp https://commits.kde.org/kio- extras/55eb68ff63646050311f8b689752ad500246c916 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767454 Title: "Other Locations" does not automatically find Samba servers in Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/dolphin/+bug/1767454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Can confirm that this is reproducible with the standard Ubuntu session in 18.04.01 and 18.10, tested both with the vanilla install with no updates and also fully updated. However, notice a few things: - If you repeatedly click the checkbox it will sometimes trigger the authentication window - The issue is *only* reproducible when the user do not have the permission to apply the changes (ie. before triggering the authentication window). It will also not be reproducible in a live session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1727908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1732245] Re: [wayland] Fullscreen games offset after returning from alt-tab
Please also see upstream reports: https://gitlab.gnome.org/GNOME/mutter/issues/397 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1732245 Title: [wayland] Fullscreen games offset after returning from alt-tab To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1732245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800135] Re: libssh-dev is missing cmake find module
Are you sure this is still incorrect in cosmic? It seems to me this is only broken in bionic. Cosmic build log has libssh-dev_0.8.1-1_amd64.deb new debian package, version 2.0. size 217956 bytes: control archive=1172 bytes. 918 bytes,21 lines control 845 bytes,12 lines md5sums Package: libssh-dev Source: libssh Version: 0.8.1-1 Architecture: amd64 Maintainer: Ubuntu Developers Original-Maintainer: Laurent Bigonville Installed-Size: 1064 Depends: libssh-4 (= 0.8.1-1), libssl-dev, zlib1g-dev Suggests: libssh-doc Conflicts: libssh-gcrypt-dev Section: libdevel Priority: optional Homepage: https://www.libssh.org/ Description: tiny C SSH library. Development files (OpenSSL flavor) The ssh library was designed to be used by programmers needing a working SSH implementation by the mean of a library. The complete control of the client is made by the programmer. With libssh, you can remotely execute programs, transfer files, use a secure and transparent tunnel for your remote programs. With its SFTP implementation, you can play with remote files easily. . This package contains development files to build the OpenSSL flavor. drwxr-xr-x root/root 0 2018-08-14 07:43 ./ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/include/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/include/libssh/ -rw-r--r-- root/root 37596 2018-08-09 09:18 ./usr/include/libssh/callbacks.h -rw-r--r-- root/root 6867 2016-03-03 19:05 ./usr/include/libssh/legacy.h -rw-r--r-- root/root 29642 2018-08-13 20:21 ./usr/include/libssh/libssh.h -rw-r--r-- root/root 20102 2018-08-10 11:23 ./usr/include/libssh/libsshpp.hpp -rw-r--r-- root/root 12393 2018-08-09 09:18 ./usr/include/libssh/server.h -rw-r--r-- root/root 31787 2018-08-10 09:06 ./usr/include/libssh/sftp.h -rw-r--r-- root/root 2735 2018-08-10 11:23 ./usr/include/libssh/ssh2.h drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/libssh/ -rw-r--r-- root/root 377 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config-version.cmake -rw-r--r-- root/root 493 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/cmake/libssh/libssh-config.cmake -rw-r--r-- root/root906476 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/libssh.a lrwxrwxrwx root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/libssh.so -> libssh.so.4 drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/pkgconfig/ -rw-r--r-- root/root 121 2018-08-14 07:43 ./usr/lib/x86_64-linux-gnu/pkgconfig/libssh.pc drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/share/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/share/doc/ drwxr-xr-x root/root 0 2018-08-14 07:43 ./usr/share/doc/libssh-dev/ lrwxrwxrwx root/root 0 2018-08-14 07:43 ./usr/share/doc/libssh-dev/changelog.Debian.gz -> ../libssh-4/changelog.Debian.gz -rw-r--r-- root/root 13682 2018-08-14 07:43 ./usr/share/doc/libssh-dev/copyright -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800135 Title: libssh-dev is missing cmake find module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1800135/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797945] Re: Lightning incompatible with Thunderbird 60.2.1
I'm affected too and thanks to the users here - especially piraten-kris
- we got an overview about the workarounds.
It was a bad suprise to start Thunderbird after regular Ubuntu update
with missing core-functionality. And it is very hard and time consuming
for an user to discover which SW-part is responsible for the misfunction
(normally you start with the plugin or the host program).
Therefore it was a surprise that Ubuntu is responsible for the error and
it is pretty annoying that automatically the responsibility will be
denied ("it's not our bug...").
Ubuntu must really asap correct this bug, because it breaks core
functionality of an application which Ubuntu take care of!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797945
Title:
Lightning incompatible with Thunderbird 60.2.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1797945/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798090] Re: Xenial update of thunderbird seems to have broken lightning/gdata provider
Yes - my comment #4 is related to bug #1797945 Thanks to smb for the clarification -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798090] Re: Xenial update of thunderbird seems to have broken lightning/gdata provider
same here - on 16.04. the "internal" Lightning calendar disappearead since it is not longer compatible with TB60. Need to install the package "xul-ext-lightning" which I removed in the past, because it provides only the english version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798090 Title: Xenial update of thunderbird seems to have broken lightning/gdata provider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1798090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782880] Re: KDE applications can not select anymore fstab or cifs mounted NTFS partions
Unfortunately after system update the bug appeared again! Kubuntu applications hide mounted NTFS folders so that the the data can not be accessed by Kubuntu applications. GTK Applications do work as expected. Test fstab: # # # / was on /dev/sda8 during installation UUID=ac1d18ac-8ad5-4565-997e-59c90bd00e71 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sda2 during installation UUID=C4DD-77E3 /boot/efi vfatumask=0077 0 1 # /home was on /dev/sda7 during installation UUID=21b47237-4d1b-4eac-8f72-a96e8d323c91 /home ext4defaults 0 2 # --> mount instructions ignored and modified, see below mount -l UUID=BA702B4E702B10A5 /home/a1/DatenAllg ntfsdefaults,umask=007,gid=46 0 0 # --> mount instructions ignored and modified, see below mount -l UUID=802A9A512A9A43D6 /home/a1/SSD-SYS ntfsdefaults,umask=007,gid=46 0 0 # --> mount instructions ignored and modified, see below mount -l #UUID=272007F45F29DEA2 /ntfs/Video ntfsrw,auto,gid=1000,uid=1000,nls=utf8 0 0 # swap was on /dev/sda6 during installation UUID=8ad70c4f-10d1-4ce5-ab5b-828bfd4a2f56 noneswapsw 0 0 # mount instructions correct taken UUID=b8c34934-ab20-479a-9861-18fdd1211bf6 /home/a1/Video ext4 defaults0 2 Lines starting with # - - > are mounted but can not seen and not accessed by kubuntu applications. The last fstab line, ext4, does a correct mounting. It looks like that ntfs mount instructions are ignored and replaced by somewhat else. ~$ mount -l sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=16408676k,nr_inodes=4102169,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=3295220k,mode=755) /dev/sda8 on / type ext4 (rw,relatime,errors=remount-ro,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/freezer type cgroup
[Bug 1782880] Re: KDE applications can not select anymore fstab or cifs mounted NTFS partions
After apt-get update on 18.04.1 the problem still existed. Than, I performed a complete new installation of kubuntu 18.04.1 from CDROM on the same computer(s), empty home directory too. The issue disappeared on all computers?! The fresh kubuntu 18.04.1 installation fixed the bag. No idea why. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782880 Title: KDE applications can not select anymore fstab or cifs mounted NTFS partions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785596] Re: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics
Just tried Ubuntu 18.04.1 LiveCD. LiveCD starts applications can be executed. However, after installation of 18.04.1 just the graphical login screen was displayed. I can enter user and password but after pressing enter the login screen always is displayed again and again. But I could login by terminal (ALT-CTL-F2). So I performed apt-get install nvidia-384. The command replaced the installed the nouveau driver and installed the nvidia 390-48 driver. Now I can login on graphical login screen without problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785596 Title: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785596] Re: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics
Thanks for fast answer. Downloaded latest image 2018-07-23 available. The nouveau driver of that image works. Ubuntu Desktop could be installed now. ubuntu@ubuntu:~$ uname -a Linux ubuntu 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ubuntu@ubuntu:~$ lspci -nnk | grep -i VGA -A2 29:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP108 [10de:1d01] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP108 [GeForce GT 1030] [1462:8c98] Kernel driver in use: nouveau Hopefully the driver and corrected nvidia driver version will be distributed soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785596 Title: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785596] Re: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics
Installation of Ubuntu 18.04 desktop is not possible. There is no display output at all. Info: At the same prepared multi-boot-system Windows works well. Test result with an old Radeon HD4050 graphics card: Ubuntu LiveDVDs run well. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785596 Title: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785596] [NEW] No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics
Public bug reported: Hi, I tried to install Ubuntu 18.04 on a system with MSI X370 SLI PLUS motherboard (Bios Version 7A33v3C of 2018-05-04), Ryzen 7 1700 and Nvidia GT 1030 graphics card. The 18.04 LiveDVDs do not work at all. There is no display output. On BIOS version 7A33v39 of 2018-01-29 MSI put the note: It must install nvidia graphic driver ver 391.01 or latest version when using AMD Raven Ridge CPU and nVidia graphic card. It looks like that the current nouveau driver, used by 18.04 LiveDVDs, blocks the display output. But, an old LiveDVD of Kubuntu 17.04 starts and Kubuntu seems to be working. I have recorded the attached lshw data with that disk. Thanks, ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "System data, recorded with liveDVD Kubuntu 17.04.html" https://bugs.launchpad.net/bugs/1785596/+attachment/5172074/+files/System%20data%2C%20recorded%20with%20liveDVD%20Kubuntu%2017.04.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785596 Title: No LiveDVD start of 18.04 on MSI AM4 with Ryzen 7 with Nvidia graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782880] Re: KDE applications can not select anymore fstab or cifs mounted NTFS partions
Thanks for answer. Command apport-collect 1782880 has been executed successfully. The problem seems not to be related to any kernel version. It looks like that it is a plasma issue only. The reported problem pop up after an update some time ago, also on another computer that contains kubuntu 16.04.1, kubuntu 18.04 and windows 8.1. If I execute KDE applications on running plasma desktop, they fail at selection NTFS mounted partions. If I execute the same KDE applications on ubuntu-desktop, they do as expected. Means, on ubuntu-desktop, NTFS mounted partitions are displayed and can be selected, e.g. by digikam, while digikam running on plasma-desktop. Test scenario: original installed desktop: kubuntu-desktop additional installed desktop: ubuntu-desktop fstab: # / was on /dev/sda5 during installation UUID=5ca944c9-9bd2-46f6-a7c1-bc4c7104239e / ext4 errors=remount-ro 0 1 # /home/a1/Data was on /dev/sda2 during installation UUID=02181F59181F4B55 /home/user/Data ntfsdefaults,umask=007,gid=46 0 0 While the file open dialog of digikam on ubuntu-desktop knows the nTFS mounted partition “Data”, the file open dialog of digikam on kubuntu- desktop does not display partition “Data”. I included a picture of the digikam file open dialog about to select the picture folder. Additional plasma bug: the application on kubuntu-desktop do not consider the change of language to english. Just the KDE Application Launcher menu changed the language from german to english. In opposite, applications on ubuntu-desktop consider the new language setting to english. ** Attachment added: "file open dialog of digikam on kubuntu-desktop, NTFS partition "Data" does not exist" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782880/+attachment/5168605/+files/digikam%20on%20ubuntu-desktop%20does%20not%20recocnize%20the%20ntfs%20partition%20data%20in%20the%20file%20open%20dialog%20%28language%20bug%20too%29.png ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782880 Title: KDE applications can not select anymore fstab or cifs mounted NTFS partions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
