[Bug 2064123] Re: dpkg: dependency problems prevent configuration of plymouth-theme-ubuntutext
is done, old installation files have been deleted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064123 Title: dpkg: dependency problems prevent configuration of plymouth-theme- ubuntutext To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2064123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064123] Re: dpkg: dependency problems prevent configuration of plymouth-theme-ubuntutext
** Changed in: plymouth (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064123 Title: dpkg: dependency problems prevent configuration of plymouth-theme- ubuntutext To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2064123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064123] [NEW] Nach Server upgrade von 23.10 auf 24.04
Public bug reported: System läuft mit diesen Fehler. Geht dieser Error mit einem update wieder weg? MfG Klaus Kuntsch ** Affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Error-plymouth.pdf" https://bugs.launchpad.net/bugs/2064123/+attachment/5772502/+files/Error-plymouth.pdf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064123 Title: Nach Server upgrade von 23.10 auf 24.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2064123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061832] Re: Firefox startet nicht
Eine der wesentlichen Eigenschaften von Unix ist die Netzwerkfähigkeit. Hier
ist besonders der Aspekt des "Remote login" hervorzuheben: Man kann sich an
einen beliebigen Rechner des Netzwerks setzen, loggt sich mit seinen
Benutzernamen und seinem Passwort ein und befindet sich in seinem
Home-Verzeichnis. Dies wird durch das "Lightweight Directory Access Protocol
(LDAP)" (entsprechend konfiguriert) und "Automount" (autofs) ermöglicht.
Das Home-Verzeichnis des Benutzers ist ein Teil eines (oder ist ein) NFS-Export
(Network File System), der auf dem Login-Rechner per „mount“ importiert wird.
Das Verzeichnis „/home“ scheidet als Mount-Point aus.
Üblicherweise wird als Mount-Point ein Verzeichnisname gewählt, der aus dem
Namen des exportierenden Rechners und dem Namen des NFS-Export gebildet wird.
Ein Verzeichnis mit diesem Namen wird auf dem Import-Rechner angelegt und im
LDAP konfiguriert. Im Verzeichnis „/home“ wird dann ein symbolischer Link auf
das Home-Verzeichnis des Benutzers eingerichtet (verwaltet von LDAP / autofs).
Beide Varianten (/${LOGNAME} und /home/${LOGNAME} ->
/${LOGNAME}) werden von „snap“ nicht akzeptiert. Wie kann diese
Konstellation von „ubuntu“ mit „snap“ gelöst werden? (In älteren Version von
„ubuntu“ war das kein Problem.)
Auf meinem PC mit den zwei Platten (zweite Platte für die vier Benutzer)
habe ich die beschriebene Konstellation nur nachempfunden, um dann, wenn
zusätzlicher Speicherplatz benötigt wird (Aufteilung der Benutzer auf
mehrere Platten), die neue Aufteilung einfach eingerichtet werden kann.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061832
Title:
Firefox startet nicht
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/2061832/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061832] [NEW] Firefox startet nicht
Public bug reported: Ich habe einen PC mit zwei Festplatten: eine SSD für das System und eine HDD für die Benutzer. Auf der SSD ist nur der Root-User und ein Benutzer mit "sudu"-Berechtigung eingerichtet. Die HDD ist eingehängt auf "/Users". Von "/home" sind symbolische Links zu den einzelne Benutzern eingerichtet (analog zu "automount" zusammen mit Lightweight Directory Access Protocol (LDAP)). Wenn ich den "firefox" starten will erhalte ich folgende Fehlermeldung: baer@wutz3:~$ firefox cannot create user data directory: /home/baer/snap/firefox/3252: Not a directory baer@wutz3:~$ Folgender Befehle liefert: baer@wutz3:~$ file /home/baer/snap/firefox/3252 /home/baer/snap/firefox/3252: directory baer@wutz3:~$ Eintrag in "/etc/passwd": baer@wutz3:~$ grep -w baer /etc/passwd baer:x:1001:1001:Kxxxs-Gr Hxxt,,,:/home/baer:/bin/bash baer@wutz3:~$ ls -l /home/baer lrwxrwxrwx 1 root root 11 Okt 10 2017 /home/baer -> /Users/baer baer@wutz3: Ändere ich den Eintrag in "/etc/passwd": baer@wutz3:~$ grep -w baer /etc/passwd baer:x:1001:1001:Kxxxs-Gr Hxxt,,,:/Users/baer:/bin/bash baer@wutz3:~$ firefox Sorry, home directories outside of /home needs configuration. See https://forum.snapcraft.io/t/11209 for details. baer@wutz3:~$ Ein ähnliches Verhalten zeigt z.B. auch der "Adobe Acrobat Reader". Wie man aus dem Verhalten bei der Änderung des Home-Verzeichnisses in "/etc/passwd" erkennt, wird der zu benutzende Pfad analysiert. Wird bei der Prüfung, ob ein Teilpfad ein Directory ist, "dies ist ein Link" geliefert, bricht das Programm mit der Fehlermeldung "Not a directory" ab. Wird bei der Prüfung "dies ist ein Link" geliefert, müsste weiter geprüft werden, ob der Link auf eine Datei oder ein Directory zeigt und entweder "dies ist ein Link auf eine Datei" oder "dies ist ein Link auf ein Directory" geliefert werden. Das anfragende Programm müsste als Ergebnis seiner Anfrage "dies ist eine Datei" oder "dies ist ein Link auf eine Datei" bzw. "dies ist ein Directory" oder "dies ist ein Link auf ein Directory" akzeptieren. persbaer@wutz3:~$ lsb_release -rd Description:Ubuntu 22.04.4 LTS Release:22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.15.0-102.112-generic 5.15.148 Uname: Linux 5.15.0-102-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 16 13:28:24 2024 InstallationDate: Installed on 2017-10-07 (2383 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: snap UpgradeStatus: Upgraded to jammy on 2023-05-15 (336 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061832 Title: Firefox startet nicht To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 572074]
For anyone coming this way: set browser.tabs.insertAfterCurrent in about:config to true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/572074 Title: New tabs open to the right of all existing tabs instead of opening next to the current tab To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/572074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948346] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih1 which has multiple installed
The same error. The system was previously upgraded from 21.04 to 21.10. sudo apt purge libnih1:i386 libnih-dbus1:i386 && sudo apt upgrade -y solved the problem. No problems since then. I hope I don't get any dependency problems later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948346 Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co- installable with libnih1 which has multiple installed instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1948346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1945524] Re: package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert
Hello to all, as announced I repeated all steps to migrate my WSL-distribution from Xubuntu 20.10 to Xubuntu 21.04. Before I removed all levels of symbolic links of "/etc/mysql/my.cnf". In deed the upgrade finished without any errors. Hence in my opinion the incident is really "solved". Thank You very much for Your support. Regards J. Klaus Krieger OMS-/eForm-/EAI-Solutions WeDoIT4U Heidenstr. 5 (1. OG) D-16278 Angermünde OT Biesenbrow Tel.: +49 (4) 852906 Mobil: +49 (170) 5269593 Fax: +49 (4) 852908 mailto:j.klaus_krie...@t-online.de <mailto:j.klaus_krie...@t-online.de> Am 04.10.2021 um 17:35 schrieb J. Klaus Krieger: > > Thank You very much for Your immediate reply. I was absent from my > working place a few days, hence my answer is late. I will try to > repeat the step of migrating my WSL-distribution from a backup with > special attention on the levels of symbolic links of > "/etc/mysql/my.cnf". This will take some time. Please feel free to > change the Status of the incident to "solved" in the mean time. > > Regards > > J. Klaus Krieger > > OMS-/eForm-/EAI-Solutions > WeDoIT4U > > Heidenstr. 5 (1. OG) > D-16278 Angermünde OT Biesenbrow > > Tel.: > > > > +49 (4) 852906 > > Mobil: > > > > +49 (170) 5269593 > > Fax: > > > > +49 (4) 852908 > > mailto:j.klaus_krie...@t-online.de <mailto:j.klaus_krie...@t-online.de> > > Am 30.09.2021 um 15:41 schrieb Paride Legovini: >> Thank you for taking the time to report this bug and helping to make >> Ubuntu better. >> >> The bug description says that: >> >> MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of >> symbolic links: '/etc/mysql/my.cnf' >> >> which can happen when there is a recursive chain of symlinks. Since it >> seems likely to me that this is a local configuration problem, rather >> than a bug in Ubuntu, I'm marking this bug as Incomplete. >> >> If indeed this is a local configuration problem, you can find pointers >> to get help for this sort of problem here: >> https://ubuntu.com/support/community-support >> >> Or if you believe that this is really a bug, then you may find it >> helpful to read "How to report bugs effectively" >> http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful >> if you would then provide a more complete description of the problem, >> explain why you believe this is a bug in Ubuntu rather than a problem >> specific to your system, and then change the bug status back to New. >> >> ** Changed in: mysql-8.0 (Ubuntu) >> Status: New => Incomplete >> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945524 Title: package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1945524] Re: package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert
Thank You very much for Your immediate reply. I was absent from my working place a few days, hence my answer is late. I will try to repeat the step of migrating my WSL-distribution from a backup with special attention on the levels of symbolic links of "/etc/mysql/my.cnf". This will take some time. Please feel free to change the Status of the incident to "solved" in the mean time. Regards J. Klaus Krieger OMS-/eForm-/EAI-Solutions WeDoIT4U Heidenstr. 5 (1. OG) D-16278 Angermünde OT Biesenbrow Tel.: +49 (4) 852906 Mobil: +49 (170) 5269593 Fax: +49 (4) 852908 mailto:j.klaus_krie...@t-online.de <mailto:j.klaus_krie...@t-online.de> Am 30.09.2021 um 15:41 schrieb Paride Legovini: > Thank you for taking the time to report this bug and helping to make > Ubuntu better. > > The bug description says that: > > MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of > symbolic links: '/etc/mysql/my.cnf' > > which can happen when there is a recursive chain of symlinks. Since it > seems likely to me that this is a local configuration problem, rather > than a bug in Ubuntu, I'm marking this bug as Incomplete. > > If indeed this is a local configuration problem, you can find pointers > to get help for this sort of problem here: > https://ubuntu.com/support/community-support > > Or if you believe that this is really a bug, then you may find it > helpful to read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem, > explain why you believe this is a bug in Ubuntu rather than a problem > specific to your system, and then change the bug status back to New. > > ** Changed in: mysql-8.0 (Ubuntu) > Status: New => Incomplete > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945524 Title: package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945524] [NEW] package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1
Public bug reported: i did an upgrade from focal to hirsute on wsl. ProblemType: Package DistroRelease: Ubuntu 21.04 Package: mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 Uname: Linux 5.10.16.3-microsoft-standard-WSL2 x86_64 ApportVersion: 2.20.11-0ubuntu65.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Sep 29 20:22:37 2021 ErrorMessage: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück KernLog: Logs.var.log.daemon.log: Logs.var.log.mysql.error.log: MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many levels of symbolic links: '/etc/mysql/my.cnf' MySQLConf.etc.mysql.mysql.cnf: MySQLVarLibDirListing: ['private_key.pem', '#ib_16384_1.dblwr', 'ibdata1', 'binlog.000271', 'ib_logfile0', 'binlog.000272', 'auto.cnf', 'performance_schema', 'public_key.pem', 'server-cert.pem', '#innodb_temp', 'binlog.000274', 'ca-key.pem', 'undo_002', 'ca.pem', 'client-key.pem', 'server-key.pem', 'ib_logfile1', 'mysql', '#ib_16384_0.dblwr', 'undo_001', 'mysql.ibd', 'm4a88t-p2x4945.err', 'binlog.000273', 'sys', 'debian-5.7.flag', 'binlog.000270', 'guacamole_db', 'postfixadmin', 'binlog.index', 'ib_buffer_pool', 'mysql_upgrade_info', 'xc1505-i74720hq.err', 'client-cert.pem'] ProcCmdline: initrd=\initrd.img panic=-1 pty.legacy_count=0 nr_cpus=4 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to hirsute on 2021-09-29 (0 days ago) modified.conffile..etc.mysql.mysql.cnf: [modified] modified.conffile..etc.mysql.mysql.conf.d.mysql.cnf: [deleted] mtime.conffile..etc.mysql.mysql.cnf: 2020-08-19T14:23:33.78 ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945524 Title: package mysql-server-8.0 8.0.26-0ubuntu0.21.04.3 failed to install/upgrade: »installiertes mysql-server-8.0-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1945524/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908279] Re: Unable to upgrade from 18.04LTS to 20.04LTS
Thanks Brian, I have bitten into that sour apple and reformatted the hard-drive and installed the version 20.04.2 . ;-( Klaus On 2021/06/11 23:13, Brian Murray wrote: > Sorry for the delay in getting back to you. If you are still having an > issue with this upgrade could you please open a new bug report using > "ubuntu-bug ubuntu-release-upgrader"? Once you've done that let me know. > Thanks! > -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. Dit bericht kan informatie bevatten die niet voor u is bestemd. Indien u niet de geadresseerde bent of dit bericht abusievelijk aan u is toegezonden, wordt u verzocht dat aan de afzender te melden en het bericht te verwijderen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908279 Title: Unable to upgrade from 18.04LTS to 20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908279] Re: Unable to upgrade from 18.04LTS to 20.04LTS
Hi Brian, Thanks for the reply. I have added a comment on the internet side for #1908279 and now as a reply to your e-mail . As I am not so clued up with Bug reporting I hope one is correct. As I had no problems for upgrading from 16.04 LTS to 18.04 LTS , I am bit confused with the problem. --- copy of my comment - Thanks Brian for the info but sorry no go. I realize I made a mistake to reply, my reply was on #1893930 Below I have copied my reply : After first trying to upgrade with : do-release-upgrade -p the result was : An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu I then unticked all " PPA 's " The result was : Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. Can't the upgrader indicate [ Which "Unofficial" software is a problem ? ] My next option is to get a fourth hard drive installed on the PC and install 20.04.lts there. [ I have drive 1 = Win XP , drive 2 = Win 7 , drive 3 = Ubuntu 18.04 LTS ] Thanks Klaus - end of copy --- Regards Klaus Richter On 10/04/2021 01:14, Brian Murray wrote: > Unable to upgrade from 18.04LTS to 20.04LTS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908279 Title: Unable to upgrade from 18.04LTS to 20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908279] Re: Unable to upgrade from 18.04LTS to 20.04LTS
Thanks Brian for the info but sorry no go. I realize I made a mistake to reply, my reply was on #1893930 Below I have copied my reply : After first trying to upgrade with : do-release-upgrade -p the result was : An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu I then unticked all " PPA 's " The result was : Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. Can't the upgrader indicate [ Which "Unofficial" software is a problem ? ] My next option is to get a fourth hard drive installed on the PC and install 20.04.lts there. [ I have drive 1 = Win XP , drive 2 = Win 7 , drive 3 = Ubuntu 18.04 LTS ] Thanks Klaus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908279 Title: Unable to upgrade from 18.04LTS to 20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893930] Re: I am unable to upgrade ubuntu 20.04, after sudo do-release-upgrade -d
After first trying to upgrade with : do-release-upgrade -p the result was : An unresolvable problem occurred while calculating the upgrade. This was likely caused by: * Unofficial software packages not provided by Ubuntu I then unticked all " PPA 's " the result was : Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. Can't the upgrader indicate [ Which "Unofficial" software is a problem ? ] My next option is to get a fourth hard drive installed on the PC and install 20.04.lts there. [ I have drive 1 = Win XP , drive 2 = Win 7 , drive 3 = Ubuntu 18.04 LTS ] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893930 Title: I am unable to upgrade ubuntu 20.04, after sudo do-release-upgrade -d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1893930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909494] Re: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56"
This also affects kernel 5.4.0-58-generic. ** Also affects: linux-meta (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/1909494 Title: wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1909494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled (wpa_supplicant[..]: l2_packet_send - sendto: No buffer space available)
*** This bug is a duplicate of bug 1909494 *** https://bugs.launchpad.net/bugs/1909494 ** This bug has been marked a duplicate of bug 1909494 wpa_supplicant and iwlwifi failing with "No buffer space available" since "kernel 5.4.0-56" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908823 Title: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled (wpa_supplicant[..]: l2_packet_send - sendto: No buffer space available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908823] Re: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled
This BUG is intensively discussed in german forum: https://forum.ubuntuusers.de/topic/funknetz-schluessel-werden-staendig- abgefragt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908823 Title: sporadic WiFi aborts with opening a window requesting to enter the WiFi password that is pre-filled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1908823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908496] [NEW] Unable to upgrade to 20.04lts from 18.04lts
Public bug reported: I have anticked all ppa's still getting error [ Could not determine the upgrade ] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Dec 17 09:45:32 2020 InstallationDate: Installed on 2014-05-24 (2398 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-12-17 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1908496 Title: Unable to upgrade to 20.04lts from 18.04lts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908496/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908391] [NEW] Unable to upgrade to 20.04LTS from 18.04LTS
Public bug reported:
I have un-ticked all the ppa's and still no go ? Error note { Could not
determine the upgrade } ?
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.41
ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18
Uname: Linux 4.15.0-128-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.20
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 16 12:36:51 2020
InstallationDate: Installed on 2014-05-24 (2397 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2020-12-16 (0 days ago)
VarLogDistupgradeTermlog:
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic dist-upgrade 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/1908391
Title:
Unable to upgrade to 20.04LTS from 18.04LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908391/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908279] [NEW] Unable to upgrade from 18.04LTS to 20.04LTS
Public bug reported: Apparently some problems with ppa's, can I remove all ppa's? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.41 ProcVersionSignature: Ubuntu 4.15.0-128.131-generic 4.15.18 Uname: Linux 4.15.0-128-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Dec 15 17:42:28 2020 InstallationDate: Installed on 2014-05-24 (2396 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-12-15 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1908279 Title: Unable to upgrade from 18.04LTS to 20.04LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1908279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906970] Re: dpkg hook hostname error
This is just an error in the postfix dpkg script. Having "search ." is completely valid. I also asked in IRC. In IRC we had consensus that "search ." is the catch all as it references the DNS-Root domain. ``` [root@ ~]# ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 32 Nov 25 2019 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf [root@ ~]# ls -la /run/systemd/resolve/resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 751 Dec 9 11:23 /run/systemd/resolve/resolv.conf [root@ ~]# cat /run/systemd/resolve/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 2a02:c205::1:53 nameserver 2a02:c205::2:53 nameserver 9.9.9.9 # Too many DNS servers configured, the following entries may be ignored. nameserver 8.8.8.8 search . [root@ ~]# systemd-resolve --status Global Protocols: -LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: uplink Fallback DNS Servers: 1.1.1.1 9.9.9.10 8.8.8.8 2606:4700:4700:: 2620:fe::10 2001:4860:4860:: Link 2 (eth0) Current Scopes: DNS Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Current DNS Server: 8.8.8.8 DNS Servers: 2a02:c205::1:53 2a02:c205::2:53 9.9.9.9 8.8.8.8 Link 3 (sit0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (br-4e6ai9437685) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 5 (br-859c2b6c2616) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 6 (br-9d44fdf2dc39) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 7 (br-055c241e7b4a) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 8 (br-915a9b534b30) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 9 (br-697dfb18ce2a) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 10 (br-591acc92bcad) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 11 (docker0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 12 (br-982c9ab14428) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 13 (br-c5eca9924b69) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 14 (br-4d8950262cec) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 15 (br-78750716d6c0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 16 (br-98473521) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 17 (br-b6ac847de088) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 18 (br-129e10059293) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 20 (vethe611647) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 24 (veth51fabb6) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 26 (vethf83897a) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 32 (veth1d1b13e) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 36 (vethf7a0e95) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 42 (veth81027e9) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 44 (veth761ee16) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 46 (vethf7c249c) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 50 (vethcad10ff) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 52 (vethefe4bb5) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 56 (vethed874ab) Current Scopes: none Protocols:
[Bug 1906970] Re: dpkg hook hostname error
This is the content of the hosts /etc/resolv.conf: ``` # This file is managed by man:systemd-resolved(8). Do not edit. # # This is a dynamic resolv.conf file for connecting local clients to the # internal DNS stub resolver of systemd-resolved. This file lists all # configured search domains. # # Run "resolvectl status" to see details about the uplink DNS servers # currently in use. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.53 options edns0 trust-ad search . ``` ** Changed in: postfix (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906970 Title: dpkg hook hostname error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1906970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906970] Re: dpkg hook hostname error
This is the default name of the docker container. That's why I reported
it here. For me it is a problem with the install script. It shouldn't
fail to install within a default docker container.
regarding b) how do I make docker select that automatically? I wasn't
able to find any way to install postfix silently except by the commands
and environment variables listed above.
{quote}
Fqdn's are a defined standard, and if your name would be like one it should
work.
Never the less we try to catch and handle some common issues.
It might be worth for your to look at your hostname in general (report your
full name here please) and the code that the install runs you can find in
/var/lib/dpkg/info/postfix.postinst - check the function myfqdn for that.
If therein is an issue that could be improved to support your kind of hostname
better that might be worth a talk.
{quote}
I already provided that. The hostname is just "cc1a572af0dc" without
domain. It is set by docker. I don't know how I would influence that at
build time.
I also provided where in the post install script it fails and why. It fails
within that function when you try to work around the missing domain part in the
fqdn by appending the "search" part from /etc/resolv.conf. That part generates
an invalid host name and writes that into the postfix configuration and than
tries to start postfix using it which makes dpkg fail.
THe resolv.conf is also written by docker and therefore also outside of my
control.
And here is an asciinema recording, maybe that helps to show what the problem
is:
* https://asciinema.org/a/MszFQIxhFi5l5Agh8EQAGC26n
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906970
Title:
dpkg hook hostname error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1906970/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906970] Re: dpkg hook hostname error
** Description changed: I tried to install postfix (3.4.13-0ubuntu1) within a Dockerfile (Ubuntu 20.04.01 LTS) and it failed because there is an error in the dpkg info file. I'm attaching the log of the 2nd time "apt install -y postfix" is executed, as it is way shorter and still shows the error message. ``` root@cc1a572af0dc:/etc# apt install -y postfix Reading package lists... Done Building dependency tree Reading state information... Done postfix is already the newest version (3.4.13-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up postfix (3.4.13-0ubuntu1) ... Postfix (main.cf) configuration was untouched. If you need to make changes, edit /etc/postfix/main.cf (and others) as needed. To view Postfix configuration values, see postconf(1). After modifying main.cf, be sure to run 'systemctl reload postfix'. Running newaliases newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc.. newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: cc1a572af0dc.. dpkg: error processing package postfix (--configure): installed postfix package post-installation script subprocess returned error exit status 75 Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Errors were encountered while processing: postfix E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I then looked into the /etc/postfix/main.cf file and tried to manually change the hostname, but it automatically gets overwritten by dpkg when apt install is ran. After that I was able to track the issue into the script "/var/lib/dpkg/info/postfix.postinst" more exactly the sed command in line 52. It reads the content of the search parameter from /etc/resolv.conf, and concatenates it with a "." as delimiter with the hostname, but it doesn't honor the special case of "search ." and therefore constructs an incorrect myhostname parameter for postfix of "cc1a572af0dc..". I'd propose to remove this resolve.conf lookup entirely so that the package installation doesn't fail within docker containers... It is a bad practice in my opinion to overwrite existing config files upon package installation. Also I'd suggest not executing postfix after the configuration is written, so that in case of unforeseen circumstances (like this one) a user can just simply run a sed against the config file after installing the package. - And the Dockerfile for reference: ``` FROM ubuntu:latest ENV DEBIAN_FRONTEND=noninteractive - ENV DEBIAN_PRIORITY=low + #ENV DEBIAN_PRIORITY=low RUN apt update \ - && echo "postfix postfix/main_mailer_type select Internet Site" | debconf-set-selections \ - && echo "postfix postfix/mailname string mysubdomain.mydomain.com" | debconf-set-selections \ - && apt install -y postfix + && echo "postfix postfix/main_mailer_type select Internet Site" | debconf-set-selections \ + && echo "postfix postfix/mailname string mysubdomain.mydomain.com" | debconf-set-selections \ + && apt install -y postfix ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1906970 Title: dpkg hook hostname error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1906970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1906970] [NEW] dpkg hook hostname error
Public bug reported: I tried to install postfix (3.4.13-0ubuntu1) within a Dockerfile (Ubuntu 20.04.01 LTS) and it failed because there is an error in the dpkg info file. I'm attaching the log of the 2nd time "apt install -y postfix" is executed, as it is way shorter and still shows the error message. ``` root@cc1a572af0dc:/etc# apt install -y postfix Reading package lists... Done Building dependency tree Reading state information... Done postfix is already the newest version (3.4.13-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up postfix (3.4.13-0ubuntu1) ... Postfix (main.cf) configuration was untouched. If you need to make changes, edit /etc/postfix/main.cf (and others) as needed. To view Postfix configuration values, see postconf(1). After modifying main.cf, be sure to run 'systemctl reload postfix'. Running newaliases newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc.. newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: cc1a572af0dc.. dpkg: error processing package postfix (--configure): installed postfix package post-installation script subprocess returned error exit status 75 Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Errors were encountered while processing: postfix E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I then looked into the /etc/postfix/main.cf file and tried to manually change the hostname, but it automatically gets overwritten by dpkg when apt install is ran. After that I was able to track the issue into the script "/var/lib/dpkg/info/postfix.postinst" more exactly the sed command in line 52. It reads the content of the search parameter from /etc/resolv.conf, and concatenates it with a "." as delimiter with the hostname, but it doesn't honor the special case of "search ." and therefore constructs an incorrect myhostname parameter for postfix of "cc1a572af0dc..". I'd propose to remove this resolve.conf lookup entirely so that the package installation doesn't fail within docker containers... It is a bad practice in my opinion to overwrite existing config files upon package installation. Also I'd suggest not executing postfix after the configuration is written, so that in case of unforeseen circumstances (like this one) a user can just simply run a sed against the config file after installing the package. And the Dockerfile for reference: ``` FROM ubuntu:latest ENV DEBIAN_FRONTEND=noninteractive #ENV DEBIAN_PRIORITY=low RUN apt update \ && echo "postfix postfix/main_mailer_type select Internet Site" | debconf-set-selections \ && echo "postfix postfix/mailname string mysubdomain.mydomain.com" | debconf-set-selections \ && apt install -y postfix ``` ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Description changed: I tried to install postfix (3.4.13-0ubuntu1) within a Dockerfile (Ubuntu 20.04.01 LTS) and it failed because there is an error in the dpkg info file. I'm attaching the log of the 2nd time "apt install -y postfix" is executed, as it is way shorter and still shows the error message. ``` root@cc1a572af0dc:/etc# apt install -y postfix Reading package lists... Done Building dependency tree Reading state information... Done postfix is already the newest version (3.4.13-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up postfix (3.4.13-0ubuntu1) ... Postfix (main.cf) configuration was untouched. If you need to make changes, edit /etc/postfix/main.cf (and others) as needed. To view Postfix configuration values, see postconf(1). After modifying main.cf, be sure to run 'systemctl reload postfix'. Running newaliases newaliases: warning: valid_hostname: misplaced delimiter: cc1a572af0dc.. newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: cc1a572af0dc.. dpkg: error processing package postfix (--configure): - installed postfix package post-installation script subprocess returned error exit status 75 + installed postfix package post-installation script subprocess returned error exit status 75 Processing triggers for libc-bin (2.31-0ubuntu9.1) ... Errors were encountered while processing: - postfix + postfix E: Sub-process /usr/bin/dpkg returned an error code (1) ``` I then looked into the /etc/postfix/main.cf file and tried to manually change the hostname, but it automatically gets overwritten by dpkg when apt install is ran. After that I was able to track the issue into the script "/var/lib/dpkg/info/postfix.postinst" more exactly the sed command in line 52. It reads the content of the search parameter from /etc/resolv.conf, and concatenates
[Bug 1906153] [NEW] During update 18.04lts to 20.04.1lts, Info : Could not determine the upgrade
Public bug reported: During upgrade on item "Setting new software channels" - error massage "Could not determine the upgrade" Unable to find "/var/log/dist-upgrade" on my PC ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.40 ProcVersionSignature: Ubuntu 4.15.0-124.127-generic 4.15.18 Uname: Linux 4.15.0-124-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Nov 29 12:54:17 2020 InstallationDate: Installed on 2014-05-24 (2380 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-11-29 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1906153 Title: During update 18.04lts to 20.04.1lts, Info : Could not determine the upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1906153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905560] Re: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
Thanks a lot. You are absolutely right. After removing the old stuff from /usr/local/lib und rebuilding ld.so.cache there is no problem any longer. Xserver runs fine with version: 2.34.2-0ubuntu2~20.04.1 now. Sorry for your inconvenience and again, many thanks. Klaus p.s. will close this bug ** Changed in: at-spi2-atk (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1905560] Re: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
Hello Sebastien, first let me thank you for your fast response! In the course of narrowing down the problem, I moved latest libatk-bridge-2.0.so.0.0.0 to a dedicated new subdirectory named sav and installed previous version: root@WS010:/usr/lib/x86_64-linux-gnu# dpkg -s libatk-bridge2.0-0 | grep -i version Version: 2.26.2-1 Now, to reproduce the prob as requested, I renamed productive libatk-bridge-2.0.so.0.0.0 to libatk-bridge-2.0.so.0.0.0.2.26.2-1 and created a hard link to sav/libatk-bridge-2.0.so.0.0.0 and then rebooted. Again the X-server continuously crashed and restarted. To be able to login from console (Ctrl-Alt-F1), I first logged in via ssh and then called telinit 3. From the console of my lenovo T61, I called startx. The result is shown in the screen-dump attached. The above procedure restores the prob. ldd returns: root@WS010:~# ldd -r /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 | grep atk libatk-1.0.so.0 => /usr/local/lib/libatk-1.0.so.0 (0x7f29f0ee9000) libatk-bridge-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x7f29f0eb2000) undefined symbol: atk_component_scroll_to_point (/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0) undefined symbol: atk_component_scroll_to (/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0) undefined symbol: atk_text_scroll_substring_to (/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0) undefined symbol: atk_text_scroll_substring_to_point (/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0) undefined symbol: atk_object_get_accessible_id (/usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0) after restoring the 2.26.2-1 version ldd returns root@WS010:/usr/lib/x86_64-linux-gnu# ldd -r /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 | grep atk libatk-1.0.so.0 => /usr/local/lib/libatk-1.0.so.0 (0x7fe79818) libatk-bridge-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-bridge-2.0.so.0 (0x7fe797f4f000) and xserver starts as expected. Hope that helps. Thank you for your valuable work. Regards, Klaus On 26.11.20 10:04, Sebastien Bacher wrote: > Thank you for your bug report, could share a photo showing the error > screen? xserver doesn't use atk so the error is probably in another > component. > > Could you also reinstall the package see if that restores the issue and > provide the output of > > $ ldd -r /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 | grep atk > > > ** Changed in: at-spi2-atk (Ubuntu) > Importance: Undecided => Low > > ** Changed in: at-spi2-atk (Ubuntu) > Status: New => Incomplete > -- Klaus Bühler Schafstraße 16 72622 Nürtingen Tel.: +49-7022-979780 Mobil: +49-1522-8721468 ** Attachment added: "xserver-crash.png" https://bugs.launchpad.net/bugs/1905560/+attachment/5438212/+files/xserver-crash.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905560] [NEW] XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used
Public bug reported: System: - Lenovo ThinkPad T61 with - Intel Core 2 Duo T7500 @ 2,2 GHz - NVIDIA G86M (Quadro NVS 140M) graphics chipset. - Samsung SSD 750, 250GByte - 4Gbyte Hauptspeicher OS: Ubuntu from 14.4 LTS, continuously upgraded to 18.04 LTS. NVIDIA third-party free driver installed via ubuntu-drivers. Notebook runs fine with 18.04. After upgrade to 20.04 LTS there is no GUI any longer. startx called from command-line reveals a crash of xserver due to an undefined symbol (atk_component_scroll_to_point) in libatk-bridge2.0-0. In the course of upgrading to 20.04 LTS, this lib has been updated from 2.26.2-1 to 2.34.2. I found this workaround: uninstall libatk-bridge2.0-0 (Purge). It has only 5 dependencies (some Python and Gnome-Orca) which are of no use to me. Downloaded 2.26.2-1 out of 18.04-repo and installed it via dpkg. Install runs smooth without any error message. After restart, GUI is back again. There is no doubt, the problem is caused by libatk-bridge2.0-0 > 2.26.2 due to the missing export of atk_component_scroll_to_point. Please restore this (and possibly other) exports, that have been dropped between 2.26.2 and 2.34.2, even if the corresponding functions are left empty. One must not drop any function from ABI without increasing library version. You can never tell, what relies on the existence of these functions. Regards, Klaus ** Affects: at-spi2-atk (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/1905560 Title: XServer Crashes with atk_component_scroll_to_point if NVIDIA Driver 340 is Used To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1905560/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471415] Re: clock date ignores xfce language settings
It is still an issue.. 2020-10-20 Xubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471415 Title: clock date ignores xfce language settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1471415/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897462] [NEW] GRUB2 freezes after removing at_keyboard
Public bug reported: Try these commands on GRUB command line: insmod at_keyboard terminal_input at_keyboard console terminal_input console Now GRUB doesn't accept any keypress. Or chainload to another GRUB with at_keyboard active on terminal_input. New GRUB cannot controlled by keyboard, but starts default menuentry after timeout. Module at_keyboard is important for localisation, e.g. using a german keyboard layout. ** Affects: grub2 (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/1897462 Title: GRUB2 freezes after removing at_keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1897462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893663] [NEW] touchpad not detected
Public bug reported: Fujitsu Lifebook U7410 core7 10th generation (Model: 7U14A1) S26391-K502-V100 no information on the touchpad fresh install ubuntu 20.04LTS * touchpad is not detected * sudo lspci -vnvn > lspci-vnvn.log more lspci-vnvn.log 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9b61] (rev 0c) Subsystem: Fujitsu Client Computing Limited Device [1e26:003f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Client Computing Limited UHD Graphics [1e26:004a] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ FLReset+ DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- TransPend- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, NROPrPrP-, LTR- 10BitTagComp-, 10BitTagReq-, OBFF Not Supported, ExtFmt-, EETLPPrefix- EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit- FRS- AtomicOpsCap: 32bit- 64bit- 128bitCAS- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled AtomicOpsCtl: ReqEn- Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee00018 Data: Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [100 v1] Process Address Space ID (PASID) PASIDCap: Exec- Priv-, Max PASID Width: 14 PASIDCtl: Enable- Exec- Priv- Capabilities: [200 v1] Address Translation Service (ATS) ATSCap: Invalidate Queue Depth: 00 ATSCtl: Enable-, Smallest Translation Unit: 00 Capabilities: [300 v1] Page Request Interface (PRI) PRICtl: Enable- Reset- PRISta: RF- UPRGI- Stopped+ Page Request Capacity: 8000, Page Request Allocation: Kernel driver in use: i915 cat /proc/version_signature > version.log more version.log Ubuntu 5.4.0-42.46-generic 5.4.44 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tmadmin2348 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 16:22:12 2020 InstallationDate: Installed on 2020-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=4dadb030-fc54-4457-a7cd-6934b85d602c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/23/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7410:pvr10601115935:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D4:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7410: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7410 dmi.product.sku: SK00 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED ** Affects: linux (Ubuntu) Importance: Undecided
[Bug 1890944] [NEW] try upgrade lubuntu 18.04LTS to 20.04
Public bug reported: in /ver/log seen problems with python-minimal and other packages to remove and upgrade, though no real error flagged. "sudo do-release-upgrade" stops after several succsessful reads and status checks with "Es konnte nicht ermittelt werden, welche Systemaktualisierungen verfügbar sind" No further reason stated. Description:Ubuntu 18.04.5 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-112.113-lowlatency 4.15.18 Uname: Linux 4.15.0-112-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: LXDE Date: Sun Aug 9 12:44:52 2020 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-08-09 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2020-08-09T12:08:13.822995 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890944 Title: try upgrade lubuntu 18.04LTS to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890944/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
NOT fixed in 5.4.0; it just recurred here on cold start from battery power. OS: Ubuntu 20.04 focal Kernel: x86_64 Linux 5.4.0-37-generic Uptime: 17m Packages: 2908 Shell: bash 5.0.16 Resolution: 5360x1440 DE: GNOME 3.36.2 WM: BudgieWM WM Theme: Pocillo GTK Theme: Pocillo-dark [GTK2/3] Icon Theme: Pocillo Font: Noto Sans 11 Disk: 191G / 412G (49%) CPU: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx @ 8x 2.3GHz GPU: AMD RAVEN (DRM 3.35.0, 5.4.0-37-generic, LLVM 9.0.1) RAM: 3801MiB / 30049MiB While sadly this event dashed my hopes that it went away, it also confirmed that the hack from ~alexander-s-m works even with LUKS present. ~vicamo can you please transition status back to confirmed? Not sure what the etiquette here is or if I am supposed to change it myself. ... Jun 20 20:54:34 redacted kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=5 Jun 20 20:54:34 redacted kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1367 thread Xorg:cs0 pid 1387 Jun 20 20:54:34 redacted kernel: amdgpu :05:00.0: GPU reset begin! Jun 20 20:54:35 redacted kernel: amdgpu :05:00.0: GPU reset succeeded, trying to resume Jun 20 20:54:35 redacted kernel: [drm] PCIE GART of 1024M enabled (table at 0x00F40090). Jun 20 20:54:35 redacted kernel: [drm] PSP is resuming... Jun 20 20:54:35 redacted kernel: [drm] reserve 0x40 from 0xf47f80 for PSP TMR Jun 20 20:54:36 redacted kernel: [drm] psp command failed and response status is (0x7) Jun 20 20:54:36 redacted kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring gfx uses VM inv eng 0 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.0.0 uses VM inv eng 1 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.1.0 uses VM inv eng 4 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.2.0 uses VM inv eng 5 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.3.0 uses VM inv eng 6 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.0.1 uses VM inv eng 7 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.1.1 uses VM inv eng 8 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.2.1 uses VM inv eng 9 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring comp_1.3.1 uses VM inv eng 10 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring sdma0 uses VM inv eng 0 on hub 1 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring vcn_dec uses VM inv eng 1 on hub 1 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring vcn_enc0 uses VM inv eng 4 on hub 1 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring vcn_enc1 uses VM inv eng 5 on hub 1 Jun 20 20:54:36 redacted kernel: amdgpu :05:00.0: ring vcn_jpeg uses VM inv eng 6 on hub 1 Jun 20 20:54:36 redacted kernel: [drm] recover vram bo from shadow start Jun 20 20:54:36 redacted kernel: [drm] recover vram bo from shadow done Jun 20 20:54:36 redacted kernel: [drm] Skip scheduling IBs! Jun 20 20:54:36 redacted kernel: [ cut here ] Jun 20 20:54:36 redacted kernel: WARNING: CPU: 0 PID: 5 at include/linux/dma-fence.h:533 drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] Jun 20 20:54:36 redacted kernel: Modules linked in: veth nft_masq nft_chain_nat bridge stp llc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) ebtable_filter ebtables ip6table_raw ip6table_mangle ip6table_nat ip6table_filter ip6_tables iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter nf_> Jun 20 20:54:36 redacted kernel: ucsi_acpi typec_ucsi typec soundcore mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amdgpu rtsx_pci_sdmmc amd_iommu_v2 gpu_sched i2c_algo_bit ttm aesni_intel drm_kms_helper crypto_simd cryptd syscopyarea glue_helper p> Jun 20 20:54:36 redacted kernel: CPU: 0 PID: 5 Comm: kworker/0:0 Tainted: P O 5.4.0-37-generic #41-Ubuntu Jun 20 20:54:36 redacted kernel: Hardware name: LENOVO 20NE000BGE/20NE000BGE, BIOS R11ET36W (1.16 ) 03/30/2020 Jun 20 20:54:36 redacted kernel: Workqueue: events drm_sched_job_timedout [gpu_sched] Jun 20 20:54:36 redacted kernel: RIP: 0010:drm_sched_resubmit_jobs+0x152/0x160 [gpu_sched] Jun 20 20:54:36 redacted kernel: Code: 41 5c 41 5d 41 5e 41 5f 5d c3 49 8b 46 10 31 c9 48 c7 80 80 00 00 00 00 00 00 00 49 8b 7f 70 31 c0 83 e7 01 74 04 0f 0b eb bf <0f> 0b eb c7 0f 0b eb 8b 66 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 Jun 20 20:54:36 redacted kernel: RSP:
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
At the time of my first comment, and the occurrences, the kernel installed was 5.4.0.33.38 on Ubuntu. On Jun 10 this was updated to 5.4.0.37.40 and so far I did not observe any recurrence. Note however that the effect was intermittent. If it does not recur until end of the month I guess it can be considered fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734541] Re: encrypted home-directory is not unmounted on logout
See for workaround: - https://wiki.ubuntuusers.de/ecryptfs/Einrichten/#Problembehebung - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854#107 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734541] Re: encrypted home-directory is not unmounted on logout
** Bug watch added: Debian Bug tracker #765854 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 ** Also affects: ecryptfs-utils (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765854 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734541 Title: encrypted home-directory is not unmounted on logout To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session-shutdown/+bug/1734541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870971] Re: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API
Seen on ThinkPad E495. Updated BIOS to 1.16 -- good but did NOT solve this particular issue. Still getting the boot-to-black issue on battery power, on a random basis. Attempting the workaround from Alexander in #3 and #5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870971 Title: [amdgpu] Xubuntu 20.04 boots to black screen on Lenovo Ideapad L340-17API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
Sorry for bad handling. #4 is attachment belonging to #5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
Suggested workaround: 1. Copy file /lib/NetworkManager/conf.d/no-mac-addr-change.conf to dir /etc/NetworkManager/conf.d/ 2. Edit file /etc/NetworkManager/conf.d/no-mac-addr-change.conf: Move 2 lines with cloned-mac-address to new chapter [connection-mac-addr- change-wifi], cf. attachment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf
** Attachment added: "no-mac-addr-change.conf" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+attachment/5352633/+files/no-mac-addr-change.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826639 Title: wpasupplicant: unknown keys in no-mac-addr-change.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1826639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869860] [NEW] Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source
Public bug reported: I am using Ubuntu 18.04 with kernel 4.15.0-91-generic and packet bcmwl- kernel-source version 6.30.223.271+bdcom-0ubuntu5~18.04.1 from bionic- updates. Wifi BCM43228 802.11a/b/g/n [14e4:4359] is fine working. But working stops after installing ubuntu mainline kernel v5.6 (image, modules, headers-all, headers-amd64). While installing kernel there were error messages regarding dkms and no dkms-modul was built. bcmwl-kernel-source should support kernel v5.6 ** Affects: bcmwl (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/1869860 Title: Ubuntu mainline kernel v5.6 not supported by bcmwl-kernel-source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1869860/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1199304] Re: alacarte removes /.config/menus/xfce-applications.menu
Ahoi, I don't know, havn't tryed since then (2013) thanks for your work klaus --- GnuPG Fingerprint: 39DE 7747 5968 007C AFB4 B82E D97B C653 A860 E9D2 Homepage: https://bashtel.de/KR/ Analog: Klaus Richert Hauptstraße 10a 67753 Relsberg Phone: 06363/9949404 --- Am 17.03.20 um 14:36 schrieb Alberts Muktupāvels: > Is this still problem in newer versions? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1199304 Title: alacarte removes /.config/menus/xfce-applications.menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alacarte/+bug/1199304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685754] Re: gnome-terminal unduly forces umask=0022
I think it's an systemd issue, which is already reported on GitHub but not fixed yet: https://github.com/systemd/systemd/issues/6077 ** Bug watch added: github.com/systemd/systemd/issues #6077 https://github.com/systemd/systemd/issues/6077 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685754 Title: gnome-terminal unduly forces umask=0022 To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862617] [NEW] Whoopsie sends non-existent crash
Public bug reported: apport-cli says: Keine aktuellen Absturzberichte. (Means: No crash report.) But Whoopsie insist on sending a report on every re-boot. Das nervt!!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-terminal 3.28.2-1ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Feb 10 12:06:21 2020 ExecutablePath: /usr/lib/gnome-terminal/gnome-terminal-server InstallationDate: Installed on 2018-10-22 (475 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862617 Title: Whoopsie sends non-existent crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1862617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851504] Re: encrypted root fails to cryptsetup on disco
I can confirm that the soft link /lib -> usr/lib/ fixes this issue. Did a clean re-install of cryptsetup-initramfs and tested the updated initramfs boots okay. Issue is fixed in disco. ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released ** Changed in: cryptsetup Status: New => 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/1851504 Title: encrypted root fails to cryptsetup on disco To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977996] Re: gnome-screenshot in Gnome 3 captures wrong area and invert image
No longer reproducible (tested Ubuntu budgie 19.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977996 Title: gnome-screenshot in Gnome 3 captures wrong area and invert image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/977996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
I own model NT950SBE, same issue: No sound at headphones and speaker. I tried Ubuntu and Manjaro with latest kernels - no progress. After changing Alss-config according to post #6, haedphones are working now. Thanks. /etc/modprobe.d/alsa-base.conf: options snd-hda-intel model=mono-speakers I attach my Realtek dump-file made in Windows. Hope that helps a bit to get a solution for the problem. ** Attachment added: "RtHDDump.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+attachment/5309144/+files/RtHDDump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1851518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853619] [NEW] Update dialog boxes way to wide and won't resize.
Public bug reported: Update dialog boxes way to wide and won't resize. I am using Xubuntu 18.04LTS. I have the DPI set to 160 because of my eyesight and 1080P. Changing DPI is not an option for me. These are the dialog boxes that won't resize. https://postimg.cc/w7Fk6QvD and here. https://postimg.cc/n9j7jLkB ** Affects: update-manager (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/1853619 Title: Update dialog boxes way to wide and won't resize. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1853619/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851504] Re: encrypted root fails to cryptsetup on disco
+source: https://git.launchpad.net/ubuntu/+source/cryptsetup/tree/debian/initramfs/hooks/cryptroot?id=applied/2%252.1.0-6#n414 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851504] Re: encrypted root fails to cryptsetup on disco
** Also affects: cryptsetup 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/1851504 Title: encrypted root fails to cryptsetup on disco To manage notifications about this bug go to: https://bugs.launchpad.net/cryptsetup/+bug/1851504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851504] Re: encrypted root fails to cryptsetup on disco
WORKAROUND: Change line 429 to read: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; do copy_exec "$so" done This changes the first regexp group from "(/lib.*)" to "(/.*)" allowing /usr/lib.* as well. After running update-initramfs -v -k 5.0.0-32-generic -c cryptsetup succeeds in mounting the encrypted root. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851504 Title: encrypted root fails to cryptsetup on disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1851504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851504] [NEW] encrypted root fails to cryptsetup on disco
Public bug reported: There is a subtle error message during update-initramfs: find: '': No such file or directory I could trace this to /usr/share/initramfs-tools/hooks/cryptroot line 430: # libargon2 uses pthread_cancel LIBC_DIR="$(ldd /sbin/cryptsetup | sed -nr 's#.* => (/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')" > find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; > do copy_exec "$so" done ldd output shows: libc.so.6 => /usr/lib/x86_64-linux-gnu/libc.so.6 (0x7f41aa8c4000) so the library is not in /lib anymore but /usr/lib The root cause of this may be an update to libc, however the script may need adjusting anyway. cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.04 DISTRIB_CODENAME=disco DISTRIB_DESCRIPTION="Ubuntu 19.04" ** Affects: initramfs-tools (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/1851504 Title: encrypted root fails to cryptsetup on disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1851504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771] Re: Reboot after resume from suspend (deep)
Thank you for pointing that out. I was actually not quite sure. But it sounded similar. The logs were almost the same. But in my case the notebook actually doesn't get to sleep mode at all, although according to the log it should be. Thanks for the hint. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848771] Re: Reboot after resume from suspend (deep)
Hello, everybody. My notebook (ThinkPad T530) apparently goes into sleep mode according to the log (see below). In reality it hangs up: The screen (backlights) stays on, but shows no content (black image). The device can't be woken up anymore. I have to switch it off (Power Off for 5 sec.). The problem occurred immediately after upgrading Kubuntu from version 19.04 to 19.10. The system was put into operation years ago with version 14.04 and has not been reinstalled since then, but has always been upgraded to the next version by "do-release-upgrade". journalctl -b -1 -e: Okt 23 15:23:13 kubuntumobile NetworkManager[1075]: [1571836993.8059] manager: sleep: sleep requested (sleeping: Okt 23 15:23:13 kubuntumobile NetworkManager[1075]: [1571836993.8090] device (eth0): state change: unavailable -> Okt 23 15:23:14 kubuntumobile org.kde.kpasswdserver[2591]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 Okt 23 15:23:14 kubuntumobile kernel: e1000e: eth0 NIC Link is Down Okt 23 15:23:14 kubuntumobile charon[2233]: 11[KNL] interface eth0 deactivated Okt 23 15:23:14 kubuntumobile NetworkManager[1075]: [1571836994.0943] device (cdc-wdm2): state change: unavailabl Okt 23 15:23:14 kubuntumobile NetworkManager[1075]: [1571836994.0983] manager: NetworkManager state is now ASLEEP Okt 23 15:23:14 kubuntumobile whoopsie[2172]: [15:23:14] offline Okt 23 15:23:14 kubuntumobile ModemManager[1036]: [/dev/cdc-wdm2] channel destroyed Okt 23 15:23:24 kubuntumobile org.kde.kpasswdserver[2591]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 Okt 23 15:23:34 kubuntumobile org.kde.kpasswdserver[2591]: org.kde.kio.kpasswdserver: User = "" , WindowId = 0 Okt 23 15:23:38 kubuntumobile mission-control[2912]: disconnect_cb: Disconnect failed: Did not receive a reply. Possible Okt 23 15:23:38 kubuntumobile systemd[1]: Starting TLP suspend/resume... Okt 23 15:23:39 kubuntumobile systemd[1]: Started TLP suspend/resume. Okt 23 15:23:39 kubuntumobile systemd[1]: Reached target Sleep. Okt 23 15:23:39 kubuntumobile systemd[1]: Starting Suspend... Okt 23 15:23:39 kubuntumobile systemd-sleep[21511]: Suspending system... Okt 23 15:23:39 kubuntumobile kernel: PM: suspend entry (deep) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1848771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
I'm on Debian Buster, seeing the same behaviour (i.e. long timeout before being shown the login screen in GDM3). Before the upgrade from Stretch all worked as expected. Uninstalling fprintd and libpam-fprintd solves the issue. But I like to have the fingerprint reader working ;-) This is on a Lenovo T430 laptop, fingerprint reader ID 147e:2020 Upek TouchChip Fingerprint Coprocessor. So, I now downgraded both of those packages to version 0.8.0-2, and all works fine. Note, I did not change the installed version of libfprint0, currently this is 0.8.2-3. Installed version of systemd is 241-7~deb10u1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845893] [NEW] Dell Latitude 7400 Touchpad unresponsive in power saving mode
Public bug reported: >From /proc/bus/input/devices: I: Bus=0018 Vendor=06cb Product=cd97 Version=0100 N: Name="DELL08E1:00 06CB:CD97 Touchpad" P: Phys=i2c-DELL08E1:00 S: Sysfs=/devices/pci:00/:00:15.1/i2c_designware.1/i2c-9/i2c-DELL08E1:00/0018:06CB:CD97.0002/input/input30 U: Uniq= H: Handlers=mouse0 event4 B: PROP=1 B: EV=1b B: KEY=e520 3 0 0 0 0 B: ABS=2e08003 B: MSC=20 The touchpad becomes unresponsive when it enters power saving mode (/sys/devices/pci\:00/\:00\:15.1/power/control = auto). The problem is fixed when disabling the power saving mode. The problem happens both with Synaptics and Libinput as driver. ** Affects: xorg-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-input-libinput-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Affects: xserver-xorg-input-synaptics-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-input-libinput-hwe-18.04 (Ubuntu) Importance: Undecided Status: New ** Also affects: xserver-xorg-input-synaptics-hwe-18.04 (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/1845893 Title: Dell Latitude 7400 Touchpad unresponsive in power saving mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-hwe-18.04/+bug/1845893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844907] [NEW] add-apt-repository fails working with keys
Public bug reported: I tried on Ubuntu 18.04 "sudo add-apt-repository ppa:mozillateam/ppa" and got error: Error: retrieving gpg key timed out. I suspect: PGP/GPG-Keyserver interface was changed recently. add-apt- repository doesn't work any more. ** 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/1844907 Title: add-apt-repository fails working with keys To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1844907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
I get this error from the sessiom of GDM3: $ journalctl -b -u user-120.slice -p 0..6 | grep -e gdm -e icc Aug 19 16:28:21 lieselotte systemd[1]: Created slice User Slice of gdm. Aug 19 16:28:21 lieselotte systemd[911]: pam_unix(systemd-user:session): session opened for user gdm by (uid=0) Aug 19 16:28:41 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung Aug 19 16:28:42 lieselotte gsd-color[1021]: failed to set screen _ICC_PROFILE: Datei »/home/klaus/.local/share/icc/edid-7c4f47b635a0342d129ec38f20009786.icc« konnte nicht geöffnet werden: Keine Berechtigung gsd-color from user id 120 trys reading a private file of user id 1000. That seems wrong by design. It's a security fault. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1067951] Re: Firefox loses window decorations in GNOME Classic and MATE with Compiz
Just as info: The bug still persists: Opening a link in thunderbird, forwarded to a minimized firefox => window decoration is gone. Alt-space, Alt-tab workaround still works $> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial nothing in /var/crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1067951 Title: Firefox loses window decorations in GNOME Classic and MATE with Compiz To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1067951/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800722] Re: EFI booting + /boot on LVM == inaccessible boot menu
I see a similar behaviour on my EFI system with BTRFS root on bionic, which recently upgraded to: grub-common/bionic-updates,now 2.02-2ubuntu8.10 amd64 GRUB_TIMEOUT is overridden to be 30 seconds. GRUB_TIMEOUT_STYLE=hidden is also overridden. Workaround for the timeout in /etc/default/grub: GRUB_RECORDFAIL_TIMEOUT=$GRUB_TIMEOUT -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800722 Title: EFI booting + /boot on LVM == inaccessible boot menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1800722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814339] [NEW] package mysql-server-5.7 5.7.25-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Hi, I initially setup my system with ubuntu 14.04 (some years ago) There I (obviously) installed mysql and worked with it Later I upgraded to ubuntu 16.04 Now I realized that mysql is not available as a package. But the configuration etc. seems to still be there in /etc/mysql I decided to install mysql via: https://www.digitalocean.com/community/tutorials/how-to-install-mysql-on-ubuntu-16-04 namely: sudo apt-get update sudo apt-get install mysql-server mysql_secure_installation The error here occurs at: sudo apt-get install mysql-server Thanks for taking care. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: mysql-server-5.7 5.7.25-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Feb 1 22:20:02 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-01 (761 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf: [mysqld_safe] syslog MySQLVarLibDirListing: ['ibtmp1', 'server-key.pem', 'ib_logfile0', 'performance_schema', 'server-cert.pem', 'debian-5.7.flag', 'auto.cnf', 'atsp0010', 'ca.pem', 'mysql', 'ib_logfile1', 'client-cert.pem', 'ibdata1', 'private_key.pem', 'public_key.pem', 'atsp2', 'client-key.pem', 'ca-key.pem', 'sys', 'ib_buffer_pool'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic root=UUID=dfcf042a-fdea-49da-bdbc-088ee28b97b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: mysql-5.7 Title: package mysql-server-5.7 5.7.25-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-5.7 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814339 Title: package mysql-server-5.7 5.7.25-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1814339/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1117684] Re: simple-image-reducer crashed with ImportError in __main__: No module named Image
*** This bug is a duplicate of bug 1112496 *** https://bugs.launchpad.net/bugs/1112496 It's caused by a bug in file: /usr/bin/simple-image-reducer. In line 28, replace "import Image" with "from PIL import Image" ** Attachment added: "simple-image-reducer" https://bugs.launchpad.net/ubuntu/+source/simple-image-reducer/+bug/1117684/+attachment/5191707/+files/simple-image-reducer -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1117684 Title: simple-image-reducer crashed with ImportError in __main__: No module named Image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-image-reducer/+bug/1117684/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779092] Re: [regression] cyclic reboot caused by the amd microcode updater
The latest update does not solve it for me. Ubuntu server 18.04 I have a AMD 2300G processor. I can start my server if I choose this kernel Linux 4.15.0-24-generic x86_64 but not the latest (linux-image-4.15.0-29-generic). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779092 Title: [regression] cyclic reboot caused by the amd microcode updater To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/1779092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1781678] [NEW] installation crushes
Public bug reported: nop ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: ubiquity 2.10.26 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 CasperVersion: 1.315.1 Date: Sat Jul 14 00:55:33 2018 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- maybe-ubiquity LiveMediaBuild: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1) MarkForUpload: True ProcEnviron: LANGUAGE=de_DE.UTF-8 TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise ubiquity-2.10.26 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1781678 Title: installation crushes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1781678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756439] [NEW] gnome-shell causes high CPU load with dual monitors
Public bug reported: I have ubuntu 10.10 with Xorg Gnome desktop, intel i915 driver and two monitors attached. gnome-shell causes a very high CPU load which seems to make the system unusable sluggish. When moving a window the CPU usage of gnome-shell raises to over 90 %. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 16 21:30:31 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop', 'thunderbird.desktop', 'jameica_2_6_6.desktop', 'org.gnome.Calculator.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-18 (210 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-05 (131 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756439 Title: gnome-shell causes high CPU load with dual monitors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1756439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748889] Re: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files
*** This bug is a duplicate of bug 1748999 *** https://bugs.launchpad.net/bugs/1748999 Worth to add: LibreOffice through 6.0.1 allows remote attackers to SEND arbitrary files to arbitrary servers via =WEBSERVICE calls in a document! Tested on Ubuntu 16.04 LTS with LibreOffice Calc version 5.1.6.2 (packet 1:5.1.6~rc2-0ubuntu1~xenial2 from main/xenial-security). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748889 Title: [CVE-2018-6871] LibreOffice allows remote attackers to read arbitrary files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1748889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743432] [NEW] package libservlet3.1-java 8.0.32-1ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Cannot provide details. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libservlet3.1-java 8.0.32-1ubuntu1.5 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Mon Jan 15 18:17:17 2018 Dependencies: DuplicateSignature: package:libservlet3.1-java:8.0.32-1ubuntu1.5 Processing triggers for ureadahead (0.100.0-19) ... dpkg: error processing package libservlet3.1-java (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-07-25 (538 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: tomcat8 Title: package libservlet3.1-java 8.0.32-1ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: tomcat8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743432 Title: package libservlet3.1-java 8.0.32-1ubuntu1.5 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1743432/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1295267] Re: Windows change Monitor/Desktop after screen lock
I can confirm, that answer #45 by James McKenna solved the problem for me! James, thank you! I am running Linux Mint Cinnamon on an Eglobal i7 fanless barebone and the problem drove me nuts. There are two monitors connected to my computer: - Main monitor: LG 21:9 connected with DP - Second monitor: Acer 16:9 connected with HDMI The main monitor wakes up in less than 1 second from suspend mode, the second screen takes up to 5 seconds. Nevertheless all windows were move to the second - the slow! - monitor. Disabling SNA fixed the problem for me! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295267 Title: Windows change Monitor/Desktop after screen lock To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1295267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741167] Re: Mainline kernel 4.14.11 not booting on Lenovo X220
Yes, mainline kernel 4.15-rc6 kernel has the same issue for arch i386: Fails to boot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741167 Title: Mainline kernel 4.14.11 not booting on Lenovo X220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741167] [NEW] Mainline kernel 4.14.11 not booting on Lenovo X220
Public bug reported: With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10 or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After GRUB message 'loading initrd' screen is cleared and machine restarts BIOS. Nothing is written to screen or system log. Mainline kernels up to 4.14.9 for arch i386 works fine. Booting same machine with mainline kernel 4.14.11 for arch amd64 works fine. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci (kernel 4.14.9 running)" https://bugs.launchpad.net/bugs/1741167/+attachment/5030860/+files/lspci-vnvn.log ** Description changed: - With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel - 4.14.10 or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. - After GRUB message 'loading initrd' screen is cleared and machine - restarts BIOS. Nothing is written to screen or system log. + With Ubuntu 16.04.3 LTS (Xenial Xerus), Ubuntu mainline kernel 4.14.10 + or 4.14.11 for arch i386 does not boot on Lenovo Thinkpad X220. After + GRUB message 'loading initrd' screen is cleared and machine restarts + BIOS. Nothing is written to screen or system log. Mainline kernels up to 4.14.9 for arch i386 works fine. Booting same machine with mainline kernel 4.14.11 for arch amd64 works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1741167 Title: Mainline kernel 4.14.11 not booting on Lenovo X220 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1741167/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737005] Re: Mainline kernel 4.14 does not start apparmor
Behavior was explained and confirmed by comment #2. Proposed kernel parameter works for me. Adding logs seems not helpfull to me, confirming anyway. ** 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/1737005 Title: Mainline kernel 4.14 does not start apparmor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737005] [NEW] Mainline kernel 4.14 does not start apparmor
Public bug reported: With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and ureadahead.service. Sometimes udisks2.service fails too. $ uname -a Linux lieselotte 4.14.4-041404-generic #201712050630 SMP Tue Dec 5 12:07:25 UTC 2017 i686 i686 i686 GNU/Linux $ systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● apparmor.service loaded failed failed LSB: AppArmor initialization ● udisks2.serviceloaded failed failed Disk Manager ● ureadahead.service loaded failed failed Read required files in advance $ systemctl status apparmor.service ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min ago Docs: man:systemd-sysv-generator(8) Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, status=1/FAILURE) Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization... Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel LSM. Dez 07 18:04:51 lieselotte apparmor[689]:...fail! Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process exited, code=exited status=1 Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor initialization. Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed state. Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 'exit-code'. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor kernel-bug xenial ** Description changed: - With Ubuntu 16.04.3 LTS (Xenial Xerus), and mainline kernel 4.14.3 or - 4.14.4 systemd fails allways starting apparmor.service and + With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel + 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and ureadahead.service. Sometimes udisks2.service failes too. $ systemctl --failed - UNIT LOAD ACTIVE SUBDESCRIPTION + UNIT LOAD ACTIVE SUBDESCRIPTION ● apparmor.service loaded failed failed LSB: AppArmor initialization ● udisks2.serviceloaded failed failed Disk Manager ● ureadahead.service loaded failed failed Read required files in advance - $ systemctl status apparmor.service + $ systemctl status apparmor.service ● apparmor.service - LSB: AppArmor initialization -Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) -Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min ago - Docs: man:systemd-sysv-generator(8) - Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, status=1/FAILURE) + Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) + Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min ago + Docs: man:systemd-sysv-generator(8) + Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, status=1/FAILURE) Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization... Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor not available as kernel LSM. Dez 07 18:04:51 lieselotte apparmor[689]:...fail! Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Control process exited, code=exited status=1 Dez 07 18:04:51 lieselotte systemd[1]: Failed to start LSB: AppArmor initialization. Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Unit entered failed state. Dez 07 18:04:51 lieselotte systemd[1]: apparmor.service: Failed with result 'exit-code'. ** Description changed: With Ubuntu 16.04.3 LTS (Xenial Xerus), and Ubuntu mainline kernel 4.14.3 or 4.14.4 systemd fails allways starting apparmor.service and - ureadahead.service. Sometimes udisks2.service failes too. + ureadahead.service. Sometimes udisks2.service fails too. $ systemctl --failed UNIT LOAD ACTIVE SUBDESCRIPTION ● apparmor.service loaded failed failed LSB: AppArmor initialization ● udisks2.serviceloaded failed failed Disk Manager ● ureadahead.service loaded failed failed Read required files in advance $ systemctl status apparmor.service ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Do 2017-12-07 18:04:51 CET; 52min ago Docs: man:systemd-sysv-generator(8) Process: 689 ExecStart=/etc/init.d/apparmor start (code=exited, status=1/FAILURE) Dez 07 18:04:51 lieselotte systemd[1]: Starting LSB: AppArmor initialization... Dez 07 18:04:51 lieselotte apparmor[689]: * Starting AppArmor profiles Dez 07 18:04:51 lieselotte apparmor[689]: * AppArmor
[Bug 1550950] Re: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-head
** Changed in: openjdk-9 (Ubuntu) Assignee: satyender (bluejteacher) => Klaus Eder (kiecmi-23) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1550950 Title: package openjdk-9-jdk 9~b102-1 failed to install/upgrade: trying to overwrite '/usr/lib/jvm/java-9-openjdk-amd64/include/linux/jawt_md.h', which is also in package openjdk-9-jdk-headless:amd64 9~b107-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1550950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727776] [NEW] notifyChanges() does not work
Public bug reported: After changing data in a column of a table, the table.notifyChanges() does not change the curves in the existing graphs in which the changed column of the table is plotted. I've updated to the new version a week ago and before it worked. The old version was about two years old. The new version: QtiPlot 0.9.9.12 (64-bit) Copyright (C) 2004-2017 Ion Vasilief Herausgegeben: 2017/09/23 Version Qt: 4.8.6 Ubuntu version: Distributor ID: Ubuntu Description:Ubuntu 14.04.5 LTS Release:14.04 Codename: trusty ** Affects: qtiplot (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/1727776 Title: notifyChanges() does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtiplot/+bug/1727776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1722092] [NEW] deutsch
Public bug reported: gib es diese seite auf deutsch? ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun Oct 8 19:08:13 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (primary) [1179:ff01] Subsystem: Toshiba America Info Systems Mobile GM965/GL960 Integrated Graphics Controller (secondary) [1179:ff01] InstallationDate: Installed on 2017-10-08 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) MachineType: TOSHIBA Satellite P200 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=0b7217c2-ca7e-457e-89b3-ad2f7f22a02c ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2007 dmi.bios.vendor: TOSHIBA dmi.bios.version: V1.50 dmi.board.name: ISRAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV1.50:bd07/11/2007:svnTOSHIBA:pnSatelliteP200:pvrPSPB3E-06300JGR:rvnTOSHIBA:rnISRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Satellite P200 dmi.product.version: PSPB3E-06300JGR dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Sun Oct 8 19:04:35 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu zesty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722092 Title: deutsch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1722092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)
** Description changed: Hi, on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion 4.4.0-28-generic) chromium stop working today. It just won't start - anymore. When try to run the launcher from shell it just reports: + anymore. When I try to run the launcher from shell it just reports: /usr/lib/chromium-browser/chromium-browser: error while loading shared libraries: libffmpeg.so: cannot open shared object file: No such file or directory - The funny thing is ffmpeg was never installed in the first place and + The funny thing is ffmpeg was'n installed in the first place and chromium runs just fine in the context of a normal userprofile. - I check the apt histroy and saw chromium was updated and I installed - ffmpeg in the hopes to solve the issue but to no avail. Now I can find - libffmpeg in the guest user contest via locate but chromium still - repsonds with the same error message. + I checked the apt histroy and saw chromium was updated today. I then + tried to install ffmpeg in the hopes to solve the issue but to no avail. + Now I can find libffmpeg in the guest user contest via locate but + chromium still repsonds with the same error message. apt-cache policy chromium-browser chromium-browser: - Installiert: 61.0.3163.79-0ubuntu0.16.04.1300 - Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300 - Versionstabelle: - *** 61.0.3163.79-0ubuntu0.16.04.1300 500 - 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages - 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages - 100 /var/lib/dpkg/status - 49.0.2623.108-0ubuntu1.1233 500 - 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 18.0.1025.151~r130497-0ubuntu1 500 - 500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 Packages + Installiert: 61.0.3163.79-0ubuntu0.16.04.1300 + Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300 + Versionstabelle: + *** 61.0.3163.79-0ubuntu0.16.04.1300 500 + 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages + 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages + 100 /var/lib/dpkg/status + 49.0.2623.108-0ubuntu1.1233 500 + 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages + 18.0.1025.151~r130497-0ubuntu1 500 + 500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 Packages I start chromium via a custom starter with line: chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php -- kiosk - and the behavior started after unattende upgrades + The behavior started after unattended upgrades Start-Date: 2017-09-22 09:28:13 Commandline: /usr/bin/unattended-upgrade Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubun tu0.16.04.11), libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg -0ubuntu0.16.04.11), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+ dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 (60.0.3112.113-0ubuntu0.16.04.12 98, 61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu 0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), libsmbcli ent:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.0 4.11), chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163 .79-0ubuntu0.16.04.1300) End-Date: 2017-09-22 09:28:30 Start-Date: 2017-09-22 10:32:17 Requested-By: gast-settings (1001) End-Date: 2017-09-22 10:32:17 Start-Date: 2017-09-22 10:43:42 Requested-By: gast-settings (1001) Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), ffmp eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut omatic) End-Date: 2017-09-22 10:43:44 - Any ideas? Best Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718885 Title: chromium doesn't start in guest session (xubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1718885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
Re: [Bug 1718885] Re: chromium doesn't start in guest session (xubuntu 16.04)
I have done that to no avail. libffmpeg is installed in /usr/lib/chromoium-browser/libffmpeg.so and /usr/lib/x86_64-linux-gnu/oxide-qt/libffmpeg.so On 22/09/2017 12:20, Olivier Tilloy wrote: I can't reproduce the problem in a clean xenial VM. When you say you can locate libffmpeg.so, where is it installed? Does the following command improve things? sudo apt install --reinstall chromium-codecs-ffmpeg-extra -- -- Klaus Merkel IT Specialist -- LAN1 Hotspots GmbH Gau?stra?e 158 22765 Hamburg Hotline +49 40 317 66 66 66 Tel. +49 40 317 66 66 - 59 Fax +49 40 317 66 66 - 33 Mobil 01522 260 22 00 k.mer...@lan1.de<mailto:k.mer...@lan1.de> www.lan1.de<http://www.lan1.de> Sitz der Gesellschaft: Hamburg Handelsregister Hamburg HRB 118700 Gesch?ftsf?hrer: J?rg H?mmer Ust.-ID-Nr. DE277065194 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718885 Title: chromium doesn't start in guest session (xubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1718885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718885] [NEW] chromium doesn't start in guest session (xubuntu 16.04)
Public bug reported: Hi, on one of my kiosk systems running xubuntu 16.04.2 (Kernelversion 4.4.0-28-generic) chromium stop working today. It just won't start anymore. When try to run the launcher from shell it just reports: /usr/lib/chromium-browser/chromium-browser: error while loading shared libraries: libffmpeg.so: cannot open shared object file: No such file or directory The funny thing is ffmpeg was never installed in the first place and chromium runs just fine in the context of a normal userprofile. I check the apt histroy and saw chromium was updated and I installed ffmpeg in the hopes to solve the issue but to no avail. Now I can find libffmpeg in the guest user contest via locate but chromium still repsonds with the same error message. apt-cache policy chromium-browser chromium-browser: Installiert: 61.0.3163.79-0ubuntu0.16.04.1300 Installationskandidat: 61.0.3163.79-0ubuntu0.16.04.1300 Versionstabelle: *** 61.0.3163.79-0ubuntu0.16.04.1300 500 500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages 100 /var/lib/dpkg/status 49.0.2623.108-0ubuntu1.1233 500 500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 18.0.1025.151~r130497-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu precise/universe amd64 Packages I start chromium via a custom starter with line: chromium-browser %U --app=http://quickborn.library4you.de/iopac/main.php -- kiosk and the behavior started after unattende upgrades Start-Date: 2017-09-22 09:28:13 Commandline: /usr/bin/unattended-upgrade Upgrade: python-samba:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubun tu0.16.04.11), libwbclient0:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg -0ubuntu0.16.04.11), samba-libs:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+ dfsg-0ubuntu0.16.04.11), chromium-browser:amd64 (60.0.3112.113-0ubuntu0.16.04.12 98, 61.0.3163.79-0ubuntu0.16.04.1300), samba-common:amd64 (2:4.3.11+dfsg-0ubuntu 0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), chromium-codecs-ffmpeg-extra:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163.79-0ubuntu0.16.04.1300), libsmbcli ent:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.04.11), sam ba-common-bin:amd64 (2:4.3.11+dfsg-0ubuntu0.16.04.9, 2:4.3.11+dfsg-0ubuntu0.16.0 4.11), chromium-browser-l10n:amd64 (60.0.3112.113-0ubuntu0.16.04.1298, 61.0.3163 .79-0ubuntu0.16.04.1300) End-Date: 2017-09-22 09:28:30 Start-Date: 2017-09-22 10:32:17 Requested-By: gast-settings (1001) End-Date: 2017-09-22 10:32:17 Start-Date: 2017-09-22 10:43:42 Requested-By: gast-settings (1001) Install: libavdevice-ffmpeg56:amd64 (7:2.8.11-0ubuntu0.16.04.1, automatic), ffmp eg:amd64 (7:2.8.11-0ubuntu0.16.04.1), libsdl1.2debian:amd64 (1.2.15+dfsg1-3, aut omatic) End-Date: 2017-09-22 10:43:44 Any ideas? Best Regards ** Affects: chromium-browser (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/1718885 Title: chromium doesn't start in guest session (xubuntu 16.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1718885/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 80220] Re: ability to print several images
** Tags added: xenial ** Tags removed: xenial ** Tags added: trusty ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/80220 Title: ability to print several images To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/80220/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702620] [NEW] package less 481-2.1ubuntu0.2 failed to install/upgrade: package less is already installed and configured
Public bug reported: none ProblemType: Package DistroRelease: Ubuntu 16.04 Package: less 481-2.1ubuntu0.2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Thu Jul 6 09:14:33 2017 DuplicateSignature: package:less:481-2.1ubuntu0.2 Unpacking thunderbird-locale-en-gb (1:52.1.1+build1-0ubuntu0.16.04.1) ... dpkg: error processing package less (--configure): package less is already installed and configured ErrorMessage: package less is already installed and configured InstallationDate: Installed on 2017-05-09 (57 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: dpkg Title: package less 481-2.1ubuntu0.2 failed to install/upgrade: package less is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702620 Title: package less 481-2.1ubuntu0.2 failed to install/upgrade: package less is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1702620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
Upgrade to "Linux ... 4.10.0-26-generic #30-Ubuntu SMP Tue Jun 27 09:30:12 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux" (Ubuntu 17.04 with XFCE under VMware WS Pro 12.5.7 build-5813279) fixed my problems with "jsvc" (starting "tomcat" 8.5.16) and kernel 4.10.0-24.28 ... catching "signal 11" immediately after start. Many thanks to all of You, having helped to solve the problem! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699772 Title: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux- image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/commons-daemon/+bug/1699772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1696741] [NEW] package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 .proc.sys.kernel.moksbstate_disabled: 0 .sys.firmware.efi.efivars.MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/sys/firmware/efi/efivars/MokSBStateRT-605dab50-e046-4300-abb6-3dd810dd8b23' .sys.firmware.efi.efivars.SecureBoot-8be4df61-93ca-11d2-aa0d-00e098032b8c: ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1696741 Title: package shim-signed 1.28~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1696741/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672742] Re: pam session does not work in xrdp
When will the patch hit the world? Upstream has fixed and Fedora is already fixing it. ubuntu sounds a little bit slow in fixing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672742 Title: pam session does not work in xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1672742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672742] Re: pam session does not work in xrdp
Upstream pull request #694 fixes the problem: https://github.com/neutrinolabs/xrdp/pull/694 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672742 Title: pam session does not work in xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1672742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1672742] Re: pam session does not work in xrdp
Am 15.03.2017 um 08:02 schrieb Klaus Steinberger: > Am 15.03.2017 um 00:44 schrieb Seth Arnold: >> Hello Klaus, is this a usability issue or does this also allow someone >> to improperly elevate their privileges? > > One more point: Correct setting of umask (which is definitly a security > thing) > is also dependent on a working session management -> see pam_umask And what I found out by looking through other pam files: It is necessary for a correct selinux context setup (for example look into the pam config for sddm) Sincerly, Klaus -- Rechnerbetriebsgruppe / IT, Fakultät für Physik Klaus Steinberger FAX: +49 89 28914280 Tel: +49 89 28914287 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672742 Title: pam session does not work in xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1672742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1672742] Re: pam session does not work in xrdp
Am 15.03.2017 um 00:44 schrieb Seth Arnold: > Hello Klaus, is this a usability issue or does this also allow someone > to improperly elevate their privileges? One more point: Correct setting of umask (which is definitly a security thing) is also dependent on a working session management -> see pam_umask Sincerly, Klaus -- Rechnerbetriebsgruppe / IT, Fakultät für Physik Klaus Steinberger FAX: +49 89 28914280 Tel: +49 89 28914287 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672742 Title: pam session does not work in xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1672742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1672742] Re: pam session does not work in xrdp
Hi Seth, > Hello Klaus, is this a usability issue or does this also allow someone > to improperly elevate their privileges? it does allow someone to login to machines which she/he has no right to access. E.g. machines reserved for a group, or machines with special hardware which should not be publicly available. Sincerly, Klaus -- Rechnerbetriebsgruppe / IT, Fakultät für Physik Klaus Steinberger FAX: +49 89 28914280 Tel: +49 89 28914287 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672742 Title: pam session does not work in xrdp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1672742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665653] Re: lsb_release -d should show a hint if it uses HWE or not
In contrast to #5 and not knowing any better interface, I expect 'lsb_release' to tell you if system uses HWE or not. This can triggered by installiation of packet 'linux-image-generic- hwe.16.04' or 'linux-image-lowlatency-hwe.16.04'. These packets should - either replace paket 'base-files' with an version for '...-hwe', maybe named 'base-files-hwe', which contains a file '/etc/lsb_release' with the string ' (HWE)' after the old description - or run a script on installiation thich edits the file '/etc/lsb_release'. ** Tags added: precice trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665653 Title: lsb_release -d should show a hint if it uses HWE or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1665653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1665653] Re: lsb_release -d should show a hint if it uses HWE or not
HWE = hardware enablement stack GA = ??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1665653 Title: lsb_release -d should show a hint if it uses HWE or not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1665653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 699802] Re: error:: no video mode activated
confirm #99 for 16.04: Linux xxx 4.4.0-57-generic #78-Ubuntu SMP Fri Dec 9 23:50:32 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux nvidia-304, 304.132, 4.4.0-57-generic, x86_64: installed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/699802 Title: error:: no video mode activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/699802/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date
As a temporary work-around on my ubuntu machine, I added the following line to /lib/systemd/system/NetworkManager.service in the [Service] section: ExecStartPre=-/bin/sh -c 'rm -f /var/lib/NetworkManager/dhclient6-*.lease' Now I get DHCPv6 leases again, even if my machine was powered off for some time. This probably doesn't work for suspend/resume, but is better than nothing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533631 Title: dhclient killed when DHCPv6 lease is out-of date To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1533631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1533631] Re: dhclient killed when DHCPv6 lease is out-of date
Same problem on xubuntu 16.10 with: network-manager 1.2.4-0ubuntu1 isc-dhcp-client 4.3.3-5ubuntu15 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1533631 Title: dhclient killed when DHCPv6 lease is out-of date To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1533631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638541] Re: Kcolorchooser doesn't save a new customer defined color
** Description changed: Kubuntu 16.10 KDE Plasma Version 5.7.5 KDE Frameworks 5.26.0 Qt 5.6.1 (kompiliert gegen 5.6.1) Package: kcolorchooser Version: 4:16.04.3-0ubuntu1 Priority: extra Section: universe/graphics Origin: Ubuntu How to reproduce: Open kcolorchooser Define a new color f.e. #990066 Add to customer defined colors - Close kcolorchooser + Close kcolorchooser -> ok Re open kcolorchooser No customer defined colors saved at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638541 Title: Kcolorchooser doesn't save a new customer defined color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kcolorchooser/+bug/1638541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638541] [NEW] Kcolorchooser doesn't save a new customer defined color
Public bug reported: Kubuntu 16.10 KDE Plasma Version 5.7.5 KDE Frameworks 5.26.0 Qt 5.6.1 (kompiliert gegen 5.6.1) Package: kcolorchooser Version: 4:16.04.3-0ubuntu1 Priority: extra Section: universe/graphics Origin: Ubuntu How to reproduce: Open kcolorchooser Define a new color f.e. #990066 Add to customer defined colors Close kcolorchooser Re open kcolorchooser No customer defined colors saved at all. ** Affects: kcolorchooser (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Kcolorchooser don't save a new customer defined color + Kcolorchooser doesn't save a new customer defined color -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638541 Title: Kcolorchooser doesn't save a new customer defined color To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kcolorchooser/+bug/1638541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1425349] Re: STACK_OP_RAISE_ABOVE: window not in stack
** Bug watch added: Red Hat Bugzilla #1280194 https://bugzilla.redhat.com/show_bug.cgi?id=1280194 ** Also affects: mutter (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1280194 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1425349 Title: STACK_OP_RAISE_ABOVE: window not in stack To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1425349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598332] [NEW] fuzzer itself crashed signal 11
Public bug reported: tried to fuzz radare2 with trinity ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: LXDE Date: Fri Jul 1 20:57:40 2016 DistroRelease: Ubuntu 15.10 ExecutablePath: /usr/bin/trinity ExecutableTimestamp: 1390065470 ProcCmdline: trinity --victims /usr/local/bin/radare2 -d /bin/ls ProcCwd: /home/klaus/radare2/radare2-regressions/bins see attached ** Affects: trinity (Ubuntu) Importance: Undecided Status: New ** Tags: bug fuzzer in trinity -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598332 Title: fuzzer itself crashed signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trinity/+bug/1598332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598332] Re: fuzzer itself crashed signal 11
backup ** Attachment added: "_usr_bin_trinity.1000.crash" https://bugs.launchpad.net/ubuntu/+source/trinity/+bug/1598332/+attachment/4693933/+files/_usr_bin_trinity.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598332 Title: fuzzer itself crashed signal 11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trinity/+bug/1598332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1597728] Re: when starting ubuntu 14.04 I firrstly gets this message: the diskdrive for /tmp is not ready or present, there I chose S for skip. secondly i get the message; Errors were found w
"mount failed for selinuxfs on sys/fs/selinuxfs" it says 2016-06-30 17:24 GMT+02:00 Klaus Cort Jensen <klausc...@gmail.com>: > When starting there shortly is (I cant reach to read it all) a text > saying: mount failed at selinuxfs on sys/fx or somethinng like that > > 2016-06-30 13:40 GMT+02:00 Apport retracing service < > 1597...@bugs.launchpad.net>: > >> ** Tags removed: need-duplicate-check >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1597728 >> >> Title: >> when starting ubuntu 14.04 I firrstly gets this message: the diskdrive >> for /tmp is not ready or present, there I chose S for skip. secondly >> i get the message; Errors were found while checking the disk drive for >> /. -u Upon I for ignore, the system starts ok - however always with a >> warning about "systemprogram problem detected" - However otherwise >> everything seem to function allright. I run the 14.04 on an elderly >> MacBook, which might be the real problem >> >> Status in initramfs-tools package in Ubuntu: >> New >> >> Bug description: >> when starting ubuntu 14.04 I firrstly gets this message: the diskdrive >> for /tmp is not ready or present, there I chose S for skip. secondly >> i get the message; Errors were found while checking the disk drive for >> /. -u Upon I for ignore, the system starts ok - however always with a >> warning about "systemprogram problem detected" - However otherwise >> everything seem to function allright. I run the 14.04 on an elderly >> MacBook, which might be the real problem. >> >> ProblemType: Package >> DistroRelease: Ubuntu 14.04 >> Package: linux-image-3.13.0-88-generic 3.13.0-88.135 >> ProcVersionSignature: Ubuntu 3.13.0-91.138-generic 3.13.11-ckt39 >> Uname: Linux 3.13.0-91-generic i686 >> ApportVersion: 2.14.1-0ubuntu3.21 >> Architecture: i386 >> AudioDevicesInUse: >>USERPID ACCESS COMMAND >>/dev/snd/controlC0: klaus 2975 F pulseaudio >> CRDA: >>country AW: >> (2402 - 2482 @ 40), (N/A, 20) >> (5170 - 5250 @ 40), (N/A, 20) >> (5250 - 5330 @ 40), (N/A, 20), DFS >> (5490 - 5710 @ 40), (N/A, 27), DFS >> Date: Tue Jun 28 18:43:30 2016 >> DuplicateSignature: >> package:linux-image-3.13.0-88-generic:3.13.0-88.135:run-parts: >> /etc/kernel/postinst.d/initramfs-tools exited with return code 127 >> ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited >> with return code 127 >> HibernationDevice: RESUME=UUID=148d1d28-f127-462b-80b7-6d188a09b18b >> InstallationDate: Installed on 2016-03-15 (107 days ago) >> InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 >> (20130820.1) >> MachineType: Apple Inc. MacBook2,1 >> ProcFB: 0 inteldrmfb >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-91-generic >> root=/dev/sda2 ro quiet splash vt.handoff=7 >> PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No >> PulseAudio daemon running, or not running as session daemon. >> RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.9 >> SourcePackage: initramfs-tools >> Title: package linux-image-3.13.0-88-generic 3.13.0-88.135 failed to >> install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited >> with return code 127 >> UpgradeStatus: Upgraded to trusty on 2016-03-15 (106 days ago) >> dmi.bios.date: 06/27/07 >> dmi.bios.vendor: Apple Inc. >> dmi.bios.version: MB21.88Z.00A5.B07.0706270922 >> dmi.board.asset.tag: Base Board Asset Tag >> dmi.board.name: Mac-F4208CAA >> dmi.board.vendor: Apple Inc. >> dmi.board.version: PVT >> dmi.chassis.asset.tag: Asset Tag >> dmi.chassis.type: 10 >> dmi.chassis.vendor: Apple Inc. >> dmi.chassis.version: Mac-F4208CAA >> dmi.modalias: >> dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: >> dmi.product.name: MacBook2,1 >> dmi.product.version: 1.0 >> dmi.sys.vendor: Apple Inc. >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597728/+subscriptions >> > > > > -- > > > *Venligste hilsener* > > *Journalist* > > > *Klaus Cort Jensen* > > *Nørrebrogade 108
[Bug 1597728] Re: when starting ubuntu 14.04 I firrstly gets this message: the diskdrive for /tmp is not ready or present, there I chose S for skip. secondly i get the message; Errors were found while
When starting there shortly is (I cant reach to read it all) a text saying: mount failed at selinuxfs on sys/fx or somethinng like that -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597728 Title: when starting ubuntu 14.04 I firrstly gets this message: the diskdrive for /tmp is not ready or present, there I chose S for skip. secondly i get the message; Errors were found while checking the disk drive for /. -u Upon I for ignore, the system starts ok - however always with a warning about "systemprogram problem detected" - However otherwise everything seem to function allright. I run the 14.04 on an elderly MacBook, which might be the real problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1597728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
