[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
When trying to solve the dependence with libcurl3 there is a problem with the removal of official Ubuntu packages... igor@mcmcc-GL553VE:~$ LANG=C sudo apt-get install libcurl3 [sudo] password for igor: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libboost-context1.65.1 python-cffi python-pycparser python3-cffi python3-ply python3-pycparser Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libcurl4-gnutls-dev opera-stable slack-desktop virtualbox-5.2 The following packages will be REMOVED: cmake cmake-curses-gui cmake-qt-gui curl djvulibre-bin kde-config-whoopsie kicad libafflib0v5 libcurl4 libcurl4-openssl-dev libtsk13 pdf2djvu sleuthkit transmission-remote-gtk uget whoopsie The following NEW packages will be installed: libcurl3 libcurl4-gnutls-dev The following packages will be upgraded: opera-stable slack-desktop virtualbox-5.2 3 upgraded, 2 newly installed, 16 to remove and 68 not upgraded. Need to get 182 MB of archives. After this operation, 79.4 MB disk space will be freed. Do you want to continue? [Y/n] How to be? Are you offering to stay without them? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Invalid Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1427638] Re: Extra package box does not expand with its window, rendering its contents unreadable
This problem is not present under Ubuntu Mate, I experienced it on Unity. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1427638 Title: Extra package box does not expand with its window, rendering its contents unreadable Status in gdebi package in Ubuntu: Triaged Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 14.10 with lubuntu-desktop 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center 0.9.5.4 3) What you expected to happen Look at attached screenshot: Window containing focused string "libjpeg62:i386" should be resizable/adjustable to display more than 1 string (automatically? manually?) 4) What happened instead It's not resizable automatically nor I'm able to resize it to display more than 1 string To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1427638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
The libcurl4 package was not showing up for me in Ubuntu Package Search and a few minutes ago it appeared! What I can suggest is a workaround that applies to users of Ubuntu Bionic Beaver that is still in beta. Download the files libcurl3_7.58.0-2ubuntu2_amd64.deb and libcurl4_7.58.0-2ubuntu2_amd64.deb. Unpack the contents of each one at a time into a folder and modify the control file in the DEBIAN folder by removing the constraint in the conflict and replace fields. Repackage the files and install them with dpkg with the --force-all option as they modify some common files. Take a hold on these packages with apt-mark and dpkg selections. I gave the following commands to hold: sudo apt-mark hold libcurl3 libcurl4 echo "libcurl3 hold" | sudo dpkg --set-selections echo "libcurl4 hold" | sudo dpkg --set-selections Recalling that this is a workaround only applicable to version 18.04 since these versions of libcurl3 and 4 only exist in it and version 18.04 is still in development. Remembering that this workaround is to allow the installation and operation not only of the applications mentioned, but also curl and uget but that side effects not yet observed can manifest themselves. Use at your own risk! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Invalid Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I manually edited file /var/lib/dpkg/status, it replaced libсurl3 (>= 7.16.2) to libcurl4 (>= 7.16.2) and libcurl3 to libcurl4, in those places where there is no version checking. Almost all the packages that require libcurl3 work without problems, except for the virtualbox, for it we had to take libcurl.so.4 from the libcurl3 package and put it in the /usr/lib/virtualbox directory... This workaround makes it possible updates all the packages except those for which the changes have been made with the libcurl3 dependencies. It's better than marking packages as hold... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Invalid Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754836] [NEW] Failed to activate service
Public bug reported: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "xsession-errors.txt" https://bugs.launchpad.net/bugs/1754836/+attachment/5074973/+files/xsession-errors.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1754836 Title: Failed to activate service Status in bluez package in Ubuntu: New Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725150] Re: apport-gtk crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from ensure_surface_for_gicon() from gtk_icon_helper_load_surface() from gtk
*** This bug is a duplicate of bug 1627564 *** https://bugs.launchpad.net/bugs/1627564 ** This bug has been marked a duplicate of bug 1627564 crash due to assertion in ensure_surface_for_gicon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1725150 Title: apport-gtk crashed with SIGABRT in g_assertion_message() from g_assertion_message_expr() from ensure_surface_for_gicon() from gtk_icon_helper_load_surface() from gtk_icon_helper_ensure_surface() Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.7-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/89ba75aaa8b360ea7a348d4f4f7d24875f1f6180 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1725150/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754836] Re: Failed to activate service
live session xsession-errors ** Attachment added: "xsession-errors" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+attachment/5074986/+files/xsession-errors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1754836 Title: Failed to activate service Status in bluez package in Ubuntu: New Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1754836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754843] [NEW] gdk-pixbuf version in artful > version in bionic
Public bug reported: gdk-pixbuf in artful is 2.36.11-1ubuntu0.1 which is greater than 2.36.11-1 in bionic ** Affects: gdk-pixbuf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1754843 Title: gdk-pixbuf version in artful > version in bionic Status in gdk-pixbuf package in Ubuntu: New Bug description: gdk-pixbuf in artful is 2.36.11-1ubuntu0.1 which is greater than 2.36.11-1 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1754843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580686] [NEW] scp-dbus-service.py crashed with signal 5 in _XReply()
You have been subscribed to a public bug: Printed 3 copys of one document with setting 2 pages on 1 sheet. Job printed normally but crash report appeared afterwards. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CupsErrorLog: E [11/May/2016:18:27:44 +0200] [cups-deviced] PID 13760 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Wed May 11 18:32:16 2016 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2016-04-30 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.5 Lpstat: device for FS-1010: usb://Kyocera/FS-1010?serial=XAL4584303 MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 PpdFiles: FS-1010: Kyocera Mita FS-1010 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash vt.handoff=7 Signal: 5 SourcePackage: system-config-printer StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gtk_tooltip_trigger_tooltip_query () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: scp-dbus-service.py crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare sudo video dmi.bios.date: 03/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B150-HD3P-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: gtk+3.0 (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-crash xenial -- scp-dbus-service.py crashed with signal 5 in _XReply() https://bugs.launchpad.net/bugs/1580686 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1580686] Re: scp-dbus-service.py crashed with signal 5 in _XReply()
** Package changed: system-config-printer (Ubuntu) => gtk+3.0 (Ubuntu) ** Summary changed: - scp-dbus-service.py crashed with signal 5 in _XReply() + crash in XTranslateCoordinates from gdk_window_x11_get_root_coords -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1580686 Title: crash in XTranslateCoordinates from gdk_window_x11_get_root_coords Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Printed 3 copys of one document with setting 2 pages on 1 sheet. Job printed normally but crash report appeared afterwards. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: system-config-printer-gnome 1.5.7+20160212-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CupsErrorLog: E [11/May/2016:18:27:44 +0200] [cups-deviced] PID 13760 (gutenprint52+usb) stopped with status 1! CurrentDesktop: XFCE Date: Wed May 11 18:32:16 2016 ExecutablePath: /usr/share/system-config-printer/scp-dbus-service.py InstallationDate: Installed on 2016-04-30 (11 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterpreterPath: /usr/bin/python3.5 Lpstat: device for FS-1010: usb://Kyocera/FS-1010?serial=XAL4584303 MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. PackageArchitecture: all Papersize: a4 PpdFiles: FS-1010: Kyocera Mita FS-1010 ProcCmdline: /usr/bin/python3 /usr/share/system-config-printer/scp-dbus-service.py ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic root=UUID=6d707d68-42fe-492a-8d56-5bd131334069 ro quiet splash vt.handoff=7 Signal: 5 SourcePackage: system-config-printer StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XTranslateCoordinates () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gtk_tooltip_trigger_tooltip_query () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: scp-dbus-service.py crashed with signal 5 in _XReply() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare sudo video dmi.bios.date: 03/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B150-HD3P-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd03/07/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1580686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617552] Re: mate-notification-daemon crashed with SIGABRT in __assert_fail_base()
*** This bug is a duplicate of bug 1598142 *** https://bugs.launchpad.net/bugs/1598142 ** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** This bug has been marked a duplicate of bug 1598142 mate-notification-daemon assert failure: mate-notification-daemon: ../../../../src/cairo.c:305: cairo_destroy: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed. ** This bug is no longer a duplicate of bug 1598142 mate-notification-daemon assert failure: mate-notification-daemon: ../../../../src/cairo.c:305: cairo_destroy: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed. ** Package changed: ubuntu => mate-notification-daemon (Ubuntu) ** This bug has been marked a duplicate of bug 1598142 mate-notification-daemon assert failure: mate-notification-daemon: ../../../../src/cairo.c:305: cairo_destroy: Assertion `CAIRO_REFERENCE_COUNT_HAS_REFERENCE (&cr->ref_count)' failed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1617552 Title: mate-notification-daemon crashed with SIGABRT in __assert_fail_base() Status in mate-notification-daemon package in Ubuntu: New Bug description: Just popped out of nowhere. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: mate-notification-daemon 1.14.1-1build1 ProcVersionSignature: Ubuntu 4.4.0-9134.53-powerpc64-smp 4.4.15 Uname: Linux 4.4.0-9134-powerpc64-smp ppc64 ApportVersion: 2.20.3-0ubuntu7 Architecture: powerpc CurrentDesktop: MATE Date: Sat Aug 27 13:10:34 2016 ExecutablePath: /usr/lib/mate-notification-daemon/mate-notification-daemon InstallationDate: Installed on 2016-03-26 (153 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta powerpc (20160326) ProcCmdline: /usr/lib/mate-notification-daemon/mate-notification-daemon ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=de_AT:de LANG=de_AT.UTF-8 Signal: 6 SourcePackage: mate-notification-daemon StacktraceTop: raise () from /lib/powerpc-linux-gnu/libc.so.6 abort () from /lib/powerpc-linux-gnu/libc.so.6 ?? () from /lib/powerpc-linux-gnu/libc.so.6 __assert_fail () from /lib/powerpc-linux-gnu/libc.so.6 cairo_destroy () from /usr/lib/powerpc-linux-gnu/libcairo.so.2 Title: mate-notification-daemon crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1617552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547561] Re: Unable to use Scilab with default Ambiance theme because of low contrast in the menu
18.04 LTS with all updates, bug exists. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1547561 Title: Unable to use Scilab with default Ambiance theme because of low contrast in the menu Status in scilab package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu with all default settings (Ambiance theme) 2. Install Scilab 3. Launch Scilab 4. Try to use Scilab menu on the top of its window 5. This menu has low contrast (see screenshot from 14.04). Temporary solution: switch theme to light (Radiance) theme. Affected Ubuntu versions: 12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10, 17.04, 17.10, 18.04 LTS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: scilab 5.5.0-2 ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12 Uname: Linux 3.19.0-49-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 CurrentDesktop: Unity Date: Fri Feb 19 18:31:09 2016 InstallationDate: Installed on 2015-12-12 (68 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) PackageArchitecture: all SourcePackage: scilab UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1547561/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754849] [NEW] libindicator fails to build against glib 2.55.x
Public bug reported: GNOME 3.28 is going to be release shortly (next week) and will be based on GLIB 2.56.0 With the latest available rc, libindicator fails to build with this error: [ 86s] CC libindicator3_la-indicator-object-enum-types.lo [ 86s] ../../libindicator/indicator-ng.c: In function 'indicator_ng_init': [ 86s] ../../libindicator/indicator-ng.c:690:21: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] [ 86s]self->entry.label = g_object_ref_sink (gtk_label_new (NULL)); [ 86s] ^ [ 86s] ../../libindicator/indicator-ng.c:691:21: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] [ 86s]self->entry.image = g_object_ref_sink (gtk_image_new ()); [ 86s] ^ [ 86s] ../../libindicator/indicator-ng.c:693:20: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] [ 86s]self->entry.menu = g_object_ref_sink (gtk_menu_new ()); [ 86s] ^ [ 87s] cc1: all warnings being treated as errors ** Affects: libindicator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libindicator in Ubuntu. https://bugs.launchpad.net/bugs/1754849 Title: libindicator fails to build against glib 2.55.x Status in libindicator package in Ubuntu: New Bug description: GNOME 3.28 is going to be release shortly (next week) and will be based on GLIB 2.56.0 With the latest available rc, libindicator fails to build with this error: [ 86s] CC libindicator3_la-indicator-object-enum-types.lo [ 86s] ../../libindicator/indicator-ng.c: In function 'indicator_ng_init': [ 86s] ../../libindicator/indicator-ng.c:690:21: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] [ 86s]self->entry.label = g_object_ref_sink (gtk_label_new (NULL)); [ 86s] ^ [ 86s] ../../libindicator/indicator-ng.c:691:21: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] [ 86s]self->entry.image = g_object_ref_sink (gtk_image_new ()); [ 86s] ^ [ 86s] ../../libindicator/indicator-ng.c:693:20: error: assignment from incompatible pointer type [-Werror=incompatible-pointer-types] [ 86s]self->entry.menu = g_object_ref_sink (gtk_menu_new ()); [ 86s] ^ [ 87s] cc1: all warnings being treated as errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libindicator/+bug/1754849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754851] [NEW] Broken Packages
Public bug reported: Failure to update Libreoffice! Difficulty solving the problem ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CurrentDesktop: X-Cinnamon Date: Sat Mar 10 11:10:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-27 (133 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 rosa third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1754851 Title: Broken Packages Status in xorg package in Ubuntu: New Bug description: Failure to update Libreoffice! Difficulty solving the problem ... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: i386 CurrentDesktop: X-Cinnamon Date: Sat Mar 10 11:10:24 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-27 (133 days ago) InstallationMedia: Linux Mint 17.1 "Rebecca" - Release i386 20141126 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1281846] Re: Temporary black screen after login
This happens to me too (still) : both VGA and DVI-D (cannot test HDMI). This happens at both log-in and log-out. DistroRelease: Ubuntu 16.04 Architecture: amd64 Date: Sat Mar 10 2018 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1281846 Title: Temporary black screen after login Status in lightdm package in Ubuntu: Confirmed Bug description: I turn on my laptop, wait lightdm appears, and do login to my user. Sometimes i got a black screen, only cursor appears in the screen. I can open a terminal with Ctrl+Alt+t, and run firefox using terminal, for example. And it is possible to change tty. Then, after 30 seconds, or more, like 1 minute, my desktop appears (background, unity launcher, top panel...). I'm having this problem in my asus laptop, that have nvidia optimus (and can confirm with other, a sony laptop with only intel graphics card). ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: lightdm 1.8.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-17.31-generic 3.11.10.3 Uname: Linux 3.11.0-17-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Wed Feb 19 00:52:59 2014 InstallationDate: Installed on 2013-12-13 (67 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1281846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style
** Summary changed: - mate-panel crashed with SIGSEGV in g_slist_remove_all() + crash in g_slist_remove_all from gtk_rc_clear_realized_style -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1555331 Title: crash in g_slist_remove_all from gtk_rc_clear_realized_style Status in gtk+2.0 package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Won't Fix Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 9 22:49:55 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-02-25 (12 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x7f4fa6439b1c :cmp %rbp,(%rdi) PC (0x7f4fa6439b1c) ok source "%rbp" ok destination "(%rdi)" (0x160016) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_slist_remove_all() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1555331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753140] Re: X-Session killed / forced log-out after suspend
*** This bug is a duplicate of bug 1754866 *** https://bugs.launchpad.net/bugs/1754866 ** This bug has been marked a duplicate of private bug 1754866 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1753140 Title: X-Session killed / forced log-out after suspend Status in systemd package in Ubuntu: New Bug description: X-sessions on my system are killed or automatically logged out when I suspend from resume. Steps to reproduce: gnome-screensaver-command --lock & systemctl suspend -i Wait for system to suspend. Disconnect, power, external monitor and usb devices. Resume by pressing the power button. Be greeted by a new log-in screen. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.2 Uname: Linux 4.15.0-041500rc6-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 3 18:34:21 2018 InstallationDate: Installed on 2015-11-05 (849 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Notebook W230SS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc6-generic root=/dev/sda3 ro uveau.modeset=0 acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax acpi_enforce_resources=lax SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2018-01-16 (46 days ago) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2017-11-16T19:29:56.550129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753140] Re: X-Session killed / forced log-out after suspend
*** This bug is a duplicate of bug 1557346 *** https://bugs.launchpad.net/bugs/1557346 ** This bug is no longer a duplicate of bug 1754866 Xorg crashed with SIGABRT ** This bug has been marked a duplicate of bug 1557346 Xorg crashed with SIGABRT in OsAbort() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1753140 Title: X-Session killed / forced log-out after suspend Status in systemd package in Ubuntu: New Bug description: X-sessions on my system are killed or automatically logged out when I suspend from resume. Steps to reproduce: gnome-screensaver-command --lock & systemctl suspend -i Wait for system to suspend. Disconnect, power, external monitor and usb devices. Resume by pressing the power button. Be greeted by a new log-in screen. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12.2 Uname: Linux 4.15.0-041500rc6-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Mar 3 18:34:21 2018 InstallationDate: Installed on 2015-11-05 (849 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: Notebook W230SS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-041500rc6-generic root=/dev/sda3 ro uveau.modeset=0 acpi_enforce_resources=lax nosplash uveau.modeset=0 acpi_enforce_resources=lax acpi_enforce_resources=lax SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2018-01-16 (46 days ago) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook modified.conffile..etc.systemd.resolved.conf: [modified] mtime.conffile..etc.systemd.resolved.conf: 2017-11-16T19:29:56.550129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1753140/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions
** Changed in: e2fsprogs (Ubuntu) Status: Invalid => Triaged ** Changed in: e2fsprogs (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Same here. I'm running a 14.04.5 distribution and the problem has appeared after the last dist-upgrade. I'm using the 'proposed' repository for Trusty, and a few packages have been updated recently. I suspect it was caused by the following update: https://www.ubuntuupdates.org/packages/latest_logs?commit=Filter&dist=trusty systemd 03-08 22:07 UTC Release: trusty Repo: universe Level: proposed New version: 204-5ubuntu20.27 Packages in group: python-systemd systemd (204-5ubuntu20.27) trusty; urgency=medium * logind: fix session not added to gc and other memleaks (LP: #1750013) - Added cgmanager as dependency, needed to clean up old cgroups -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest
** Changed in: cups Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1750514 Title: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest Status in CUPS: Fix Released Status in cups package in Ubuntu: Confirmed Status in cups source package in Bionic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups. This problem was most recently seen with package version 2.2.6-5, the problem page at https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1750514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming
I'm re-assigning the status and importance based on user reports in IRC and elsewhere. See also the related "Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997 ** Changed in: e2fsprogs (Ubuntu) Status: In Progress => Triaged ** Changed in: e2fsprogs (Ubuntu) Importance: Wishlist => Medium ** Changed in: e2fsprogs (Ubuntu) Assignee: Daniel Mehrmann (daniel-mehrmann) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming Status in e2fsprogs package in Ubuntu: Triaged Bug description: In the Trusty release notes "Metadata checksumming" is listed as one of the tech highlights of kernel 3.13. https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS However, the userland tools do not support this kernel feature. To the best of my knowledge this will be supported in 1.43, and won't be backported to 1.42. IMHO this is very misleading. It's like a car salesperson sold you a sports car with an V8 engine. After you drove it home, you opened the hood and realized only 6 cylinders are working because 2 of the spark plugs were not included, and you have to buy aftermarket ones. BTW, I've been following the development of e2fsprogs for over a year. 1.43 release has been in limbo for God knows how long :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions
An issue for 18.04 too, reported in IRC. There is a related bug "Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754877] Re: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1552577, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1754877/+attachment/5075282/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754877/+attachment/5075285/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754877/+attachment/5075288/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754877/+attachment/5075289/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754877/+attachment/5075290/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754877/+attachment/5075291/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754877/+attachment/5075292/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754877 Title: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying Status in apport package in Ubuntu: New Bug description: It happens time to time, when I try to magnify a scanned text-picture in XZGV, suddenly the whole graphical session terminates, I see the monitor in framebuffer character mode, and then I can log in for an other graphical session. Usually I reboot just after this login, and after this reboot I get the crash report possibility, ... this time three in parallel, but only the "apport-gtk crashed with SIGSEGV" out of these was successful to submit a crash report. This is the reason why the summary is a bit unsure: "either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying". I am not sure whether there is any problem with apport-gtk, because it might happen, that only the reboot disturbed it (I make the reboots before any crash report opportunity window shows up). I think the real problem is, that magnifying a larger picture in XZGV can kill the graphical session, regadless what other jobs wanted to remain alive in it. (this is 18.04 development branch, and xzgv 0.9.1-4, everything (evrypackage) are fresh up to date) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 10 19:30:33 2018 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1518540671 InstallationDate: Installed on 2017-07-13 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 JournalErrors: -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 19:35:01 CET. -- Mar 10 19:32:21 pc56 spice-vdagent[1670]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 10 19:32:21 pc56 pulseaudio[1703]: [pulseaudio] pid.c: Daemon already running. Mar 10 19:32:46 pc56 pulseaudio[1499]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/prohlep Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7f43f443e5a9:mov(%rbx),%rdi PC (0x7f43f443e5a9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-
[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Continuing my previous comment: after the update I got both 'cgmanager' and 'systemd-logind' daemons eating 70% of processor time each (in a multi-core cpu). Tried to reinstall and reconfigure all recently updated packages, with no result. The visible effect is a long delay when logging (either on terminal or graphics environment). I also got problems with the NetworkManager, which started to show an 'insufficient privileges' when selecting a wireless network. A stopgap measure to access wifi was killing the user-level 'nm-applet' process and starting it again as root. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Solved the issue temporarily for me: 1. Had to manually download and install older packages: sudo dpkg -i libpam-systemd_204-5ubuntu20.25_amd64.deb libsystemd- daemon0_204-5ubuntu20.25_amd64.deb systemd- services_204-5ubuntu20.25_amd64.deb 2. Put those versions on hold: sudo apt-mark hold systemd-services libsystemd-daemon0 libpam-systemd 3. Removed completely 'cgmanager': sudo apt-get purge cgmanager 4. Restarted -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754887] Re: apport-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1552577, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1754887/+attachment/5075405/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754887/+attachment/5075408/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754887/+attachment/5075411/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754887/+attachment/5075412/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754887/+attachment/5075413/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754887/+attachment/5075414/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754887/+attachment/5075415/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1552577 apport-gtk crashed with SIGSEGV in _gtk_style_provider_private_get_settings(provider=0x0) [gtkstyleproviderprivate.c:123] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754887 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: This is a fork of the compound "Bug 1754877", see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754877 This fork will be devoted to the "apport-gtk crashed with SIGSEGV" part of the compound bug 1754877, and the other fork parallel to this will contain to the original XZGV + Xorg issue. Due to the original issue (see bug 1754877) I usually reboot before any bug report possibility shows up, or even I do not login before the reboot. After reboot, the bug report possibility shows up earlier, than my firefox is started. Due to the original compound bug, I always get at least two bug report possibilities in parallel. When I try to answer the first immediately, and when this process arrives to that point, where the apport program tries to open the bugs.lunchpad.net for me, then I can see the ICON of firefox for a short second only in the left icon bar, and then it disapperas, and I get NO firefox at all. Then, when I open the firefox, and AFTER THIS OPENING I handle the other, second apport window waiting for me already since the beginnings, then it already can simply open a tab in the running firefox for me to continue the bug report there. My feeling is, that "apport-gtk crashed with SIGSEGV" belongs to the unsuccesful firefox opening, since the first bug report usually disappears. Whenever I try to reproduce the other "XZGV + Xorg issue", and the firefox is NOT opened IN ADVANCE,then I have an unsuccessful firefox opening experience with apport program: that report trial dies out, disappears. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 10 19:58:35 2018 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1518540671 InstallationDate: Installed on 2017-07-13 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 JournalErrors: -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 20:13:45 CET. -- Mar 10 19:59:48 pc56 spice-vdagent[1675]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 10 19:59:48 pc56 pulseaudio[1723]: [pulseaudio] pid.c: Daemon already running. Mar 10 20:00:13 pc56 pulseaudio[1521]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/prohlep Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-m
[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming
Ubuntu 18.04 may well enable (under review) 64bit,metadata_csum by default, thereby creating ext4 filesystems that are not compatible with e2fsck on Ubuntu-16.04 LTS (or 14.04)? This creates all sorts of problems for compatibility/portability of filesystems, for e.g.:- * dual-booting 18.04 and older LTS versions * "ext4 portable disks" do not work. * (notice also Ken's hwe-edge/lvm issue above too). I strongly support that Xenial gets a backport of e2fsprogs-1.43 (as requested) so that this compatibility-annoyance is ameliorated, at least. Debian have already done this, created a "jessie-backports" e2fsprogs=1.43.3-1~bpo8+1 Hopefully tytso can advise us on the best version of e2fsprogs to backport (18.04 currently has 1.43.9-2). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming Status in e2fsprogs package in Ubuntu: Triaged Bug description: In the Trusty release notes "Metadata checksumming" is listed as one of the tech highlights of kernel 3.13. https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS However, the userland tools do not support this kernel feature. To the best of my knowledge this will be supported in 1.43, and won't be backported to 1.42. IMHO this is very misleading. It's like a car salesperson sold you a sports car with an V8 engine. After you drove it home, you opened the hood and realized only 6 cylinders are working because 2 of the spark plugs were not included, and you have to buy aftermarket ones. BTW, I've been following the development of e2fsprogs for over a year. 1.43 release has been in limbo for God knows how long :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions
Canonical please read Theodore Tso's Comment #4 above, and consider for Ubuntu 18.04 LTS! This "64bit,metadata_csum" creates compatibility-issues even with 16.04 LTS, and does not seem to provide a huge benefit [>16TB fs support, slightly stronger metadata checksumming]. This creates all sorts of problems for compatibility/portability of filesystems, e.g.:- * dual-booting 18.04, even previous LTS version cannot fsck the filesystem. * "ext4 portable disks" created by 18.04 similarly same problem. * Also consider how wide is the 64bit,metadata_csum support anyway, users may want disks to work with many distros/drivers? Canonical's commercial-supporters may have views herein?. -- the linked bugreport also mentions another issue with hwe-edge and LVM. Also note, turning off the 64bit,metadata_csum when required is a total PAIN, needing filesystem offline, fsck and tune2fs in careful concert. In my view, the 16.04 LTS mke2fs.conf [ ext4{} stanza with "auto_64-bit_support = 1" and NO "64bit,metadata_csum" in "features" ] should be seriously-considered for 18.04 "LTS" (even if 18.10 onwards follow Debian). As tytso says, this 'change' has been "Decision-by-Default" due to importing a Debian upstream package, I would like Canonical to make an 'informed and considered decision' about this please!. Hope that helps! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754895] [NEW] package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: do-release-upgrade trusty -> xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: init (not installed) ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39 Uname: Linux 3.13.0-139-generic x86_64 NonfreeKernelModules: ksplice_95uod8hg_vmlinux_new ksplice_95uod8hg ksplice_ddpjisv1 ksplice_rka920bz ksplice_1riczoim_vmlinux_new ksplice_1riczoim ksplice_crp1ph1u_kvm_intel_new ksplice_crp1ph1u ksplice_tqw2mpfu ksplice_cw77iggc ksplice_atmd9p4a ksplice_4o4hn2b7 ksplice_f1t11xc0_vmlinux_new ksplice_f1t11xc0 ksplice_cszgun87_vmlinux_new ksplice_cszgun87 ksplice_29s6va6l_vmlinux_new ksplice_29s6va6l ksplice_tf44m8uy ksplice_epc9kw49 ksplice_3qz20j8p ksplice_jtw954mg_vmlinux_new ksplice_jtw954mg ksplice_ek4cdsiq ksplice_fx6q5odc_vmlinux_new ksplice_fx6q5odc ksplice_muwbgmk6_vmlinux_new ksplice_muwbgmk6 ksplice_sy1l5bb4 ksplice_qpv02ghx_vmlinux_new ksplice_qpv02ghx ksplice_j5rqibmu ksplice_ku5v8znq_vmlinux_new ksplice_ku5v8znq ksplice_k7b1nygi_vmlinux_new ksplice_k7b1nygi ksplice_7a64zsdm_vmlinux_new ksplice_7a64zsdm ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Sat Mar 10 15:09:36 2018 DuplicateSignature: package:init:(not installed):dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: init-system-helpers Title: package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-03-10 (0 days ago) ** Affects: init-system-helpers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1754895 Title: package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in init-system-helpers package in Ubuntu: New Bug description: do-release-upgrade trusty -> xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: init (not installed) ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39 Uname: Linux 3.13.0-139-generic x86_64 NonfreeKernelModules: ksplice_95uod8hg_vmlinux_new ksplice_95uod8hg ksplice_ddpjisv1 ksplice_rka920bz ksplice_1riczoim_vmlinux_new ksplice_1riczoim ksplice_crp1ph1u_kvm_intel_new ksplice_crp1ph1u ksplice_tqw2mpfu ksplice_cw77iggc ksplice_atmd9p4a ksplice_4o4hn2b7 ksplice_f1t11xc0_vmlinux_new ksplice_f1t11xc0 ksplice_cszgun87_vmlinux_new ksplice_cszgun87 ksplice_29s6va6l_vmlinux_new ksplice_29s6va6l ksplice_tf44m8uy ksplice_epc9kw49 ksplice_3qz20j8p ksplice_jtw954mg_vmlinux_new ksplice_jtw954mg ksplice_ek4cdsiq ksplice_fx6q5odc_vmlinux_new ksplice_fx6q5odc ksplice_muwbgmk6_vmlinux_new ksplice_muwbgmk6 ksplice_sy1l5bb4 ksplice_qpv02ghx_vmlinux_new ksplice_qpv02ghx ksplice_j5rqibmu ksplice_ku5v8znq_vmlinux_new ksplice_ku5v8znq ksplice_k7b1nygi_vmlinux_new ksplice_k7b1nygi ksplice_7a64zsdm_vmlinux_new ksplice_7a64zsdm ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Sat Mar 10 15:09:36 2018 DuplicateSignature: package:init:(not installed):dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: init-system-helpers Title: package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-03-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1754895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754895] Re: package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1754895 Title: package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in init-system-helpers package in Ubuntu: New Bug description: do-release-upgrade trusty -> xenial ProblemType: Package DistroRelease: Ubuntu 16.04 Package: init (not installed) ProcVersionSignature: Ubuntu 3.13.0-139.188-generic 3.13.11-ckt39 Uname: Linux 3.13.0-139-generic x86_64 NonfreeKernelModules: ksplice_95uod8hg_vmlinux_new ksplice_95uod8hg ksplice_ddpjisv1 ksplice_rka920bz ksplice_1riczoim_vmlinux_new ksplice_1riczoim ksplice_crp1ph1u_kvm_intel_new ksplice_crp1ph1u ksplice_tqw2mpfu ksplice_cw77iggc ksplice_atmd9p4a ksplice_4o4hn2b7 ksplice_f1t11xc0_vmlinux_new ksplice_f1t11xc0 ksplice_cszgun87_vmlinux_new ksplice_cszgun87 ksplice_29s6va6l_vmlinux_new ksplice_29s6va6l ksplice_tf44m8uy ksplice_epc9kw49 ksplice_3qz20j8p ksplice_jtw954mg_vmlinux_new ksplice_jtw954mg ksplice_ek4cdsiq ksplice_fx6q5odc_vmlinux_new ksplice_fx6q5odc ksplice_muwbgmk6_vmlinux_new ksplice_muwbgmk6 ksplice_sy1l5bb4 ksplice_qpv02ghx_vmlinux_new ksplice_qpv02ghx ksplice_j5rqibmu ksplice_ku5v8znq_vmlinux_new ksplice_ku5v8znq ksplice_k7b1nygi_vmlinux_new ksplice_k7b1nygi ksplice_7a64zsdm_vmlinux_new ksplice_7a64zsdm ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 Date: Sat Mar 10 15:09:36 2018 DuplicateSignature: package:init:(not installed):dependency problems - leaving triggers unprocessed ErrorMessage: dependency problems - leaving triggers unprocessed RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: init-system-helpers Title: package init (not installed) failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2018-03-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1754895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670898] [NEW] crash after spi_cache_foreach from impl_GetItems
You have been subscribed to a public bug: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with package version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/f507ea21d5337991672738917ae190e6e86f76e2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. ** Affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New ** Tags: xenial -- crash after spi_cache_foreach from impl_GetItems https://bugs.launchpad.net/bugs/1670898 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670898] Re: crash after spi_cache_foreach from impl_GetItems
** Summary changed: - /usr/bin/mate-settings-daemon:11:g_type_check_instance_is_fundamentally_a:g_object_ref:g_hash_table_foreach:spi_cache_foreach:impl_GetItems + crash after spi_cache_foreach from impl_GetItems ** Package changed: mate-settings-daemon (Ubuntu) => at-spi2-atk (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1670898 Title: crash after spi_cache_foreach from impl_GetItems Status in at-spi2-atk package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding mate-settings-daemon. This problem was most recently seen with package version 1.12.1-2build1, the problem page at https://errors.ubuntu.com/problem/f507ea21d5337991672738917ae190e6e86f76e2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1670898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754472] Re: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there
That's not what I meant. The test is valid, and on s390x, one consistently fails to run fsckd right. I have already included a few overrides in bionic, where it is valid for fsckd to enter error state, as long as it does not block boot. what release are you seeing this? what you are saying here, is that fsck support on boot is broken on s390x, and that we do not care about it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754472 Title: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there Status in systemd package in Ubuntu: New Bug description: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754887] Re: apport-gtk crashed with SIGSEGV
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 "Comment here only if you think the duplicate status is wrong.", OK I do it. Because that bug is "Crash displayed after logging in.". And this bug is: apport-gtk crash IF no running firefox, and the apport wants to brig me to bugs.lunchpad.net to continue and finish the bug report. The resulting end is the same: "apport-gtk crashed with SIGSEGV", but the situation, context and reason is really different, hence it seems to be a different problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754887 Title: apport-gtk crashed with SIGSEGV Status in apport package in Ubuntu: New Bug description: This is a fork of the compound "Bug 1754877", see https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754877 This fork will be devoted to the "apport-gtk crashed with SIGSEGV" part of the compound bug 1754877, and the other fork parallel to this will contain to the original XZGV + Xorg issue. Due to the original issue (see bug 1754877) I usually reboot before any bug report possibility shows up, or even I do not login before the reboot. After reboot, the bug report possibility shows up earlier, than my firefox is started. Due to the original compound bug, I always get at least two bug report possibilities in parallel. When I try to answer the first immediately, and when this process arrives to that point, where the apport program tries to open the bugs.lunchpad.net for me, then I can see the ICON of firefox for a short second only in the left icon bar, and then it disapperas, and I get NO firefox at all. Then, when I open the firefox, and AFTER THIS OPENING I handle the other, second apport window waiting for me already since the beginnings, then it already can simply open a tab in the running firefox for me to continue the bug report there. My feeling is, that "apport-gtk crashed with SIGSEGV" belongs to the unsuccesful firefox opening, since the first bug report usually disappears. Whenever I try to reproduce the other "XZGV + Xorg issue", and the firefox is NOT opened IN ADVANCE,then I have an unsuccessful firefox opening experience with apport program: that report trial dies out, disappears. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 10 19:58:35 2018 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1518540671 InstallationDate: Installed on 2017-07-13 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 JournalErrors: -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 20:13:45 CET. -- Mar 10 19:59:48 pc56 spice-vdagent[1675]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 10 19:59:48 pc56 pulseaudio[1723]: [pulseaudio] pid.c: Daemon already running. Mar 10 20:00:13 pc56 pulseaudio[1521]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/prohlep Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7f19de99b5a9:mov(%rbx),%rdi PC (0x7f19de99b5a9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-09 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754887/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727825] Re: networkd DHCP immediately drops lease ( on igbx cards )
** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1727825 Title: networkd DHCP immediately drops lease ( on igbx cards ) Status in systemd package in Ubuntu: Invalid Bug description: On new install of 17.10 systemd-networkd loops with: Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service... Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed Oct 23 16:45:24 san-jose systemd[1]: Started Network Service. Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 10.30.3.94/24 via 12 Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The name org.freedesktop Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 10.30.3.94/24 via 12 Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The name org.freedesktop Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost that is the correct interface and address. If I manually run 'dhclient nep129s0f0' the lease sticks and 'journalctl -fu systemd-networkd' shows: Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 10.30.3.94/24 via 12 Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The name org.freedesktop Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured I have verified this is reproducible on other systems with ixgbe based add in cards. igb (1G) cards seem to behave properly as do a random assortment of onboard devices and virtio devices inside VMs. Based on a pseudo random selection of my available gear it does seem hardware specific but this is our only flavor of 10G nic (and we have kindof a lot of them). Since isc-dhcp-client can bring up the interface on the commandline I don't *think* it's a driver issue. root@host:~# lsb_release -rd;uname -r ; dpkg -l nplan systemd Description: Ubuntu 17.10 Release: 17.10 4.13.0-16-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii nplan 0.30 amd64 YAML network configuration abstraction fo ii systemd 234-2ubuntu12 amd64 system and service manager my current workaround: root@host:~# cat /etc/rc.local #!/bin/sh dhclient enp129s0f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754877] Re: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying
*** This bug is a duplicate of bug 1552577 *** https://bugs.launchpad.net/bugs/1552577 Half of this bug is the duplicate of https://bugs.launchpad.net/bugs/1754885 and NOT of https://bugs.launchpad.net/bugs/1552577 SINCE in 1552577 and 1754885 the situations what caus the problems are different, only the resulting signal is the same. The other half of this bug is the duplicate of https://bugs.launchpad.net/bugs/1754887 During the creation of this error report it was not clear, which report of the three parallel reports remained alive. But later experiments made me clear the situation, and therefore later I allowed the apport- gtk produce the SEPARATE much more precise reports 1754885 and 1754887. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754877 Title: either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying Status in apport package in Ubuntu: New Bug description: It happens time to time, when I try to magnify a scanned text-picture in XZGV, suddenly the whole graphical session terminates, I see the monitor in framebuffer character mode, and then I can log in for an other graphical session. Usually I reboot just after this login, and after this reboot I get the crash report possibility, ... this time three in parallel, but only the "apport-gtk crashed with SIGSEGV" out of these was successful to submit a crash report. This is the reason why the summary is a bit unsure: "either apport-gtk crashed with SIGSEGV or x-server crashed because of xzgv magnifying". I am not sure whether there is any problem with apport-gtk, because it might happen, that only the reboot disturbed it (I make the reboots before any crash report opportunity window shows up). I think the real problem is, that magnifying a larger picture in XZGV can kill the graphical session, regadless what other jobs wanted to remain alive in it. (this is 18.04 development branch, and xzgv 0.9.1-4, everything (evrypackage) are fresh up to date) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport-gtk 2.20.8-0ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sat Mar 10 19:30:33 2018 ExecutablePath: /usr/share/apport/apport-gtk ExecutableTimestamp: 1518540671 InstallationDate: Installed on 2017-07-13 (240 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterpreterPath: /usr/bin/python3.6 JournalErrors: -- Logs begin at Fri 2018-03-09 12:38:41 CET, end at Sat 2018-03-10 19:35:01 CET. -- Mar 10 19:32:21 pc56 spice-vdagent[1670]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 Mar 10 19:32:21 pc56 pulseaudio[1703]: [pulseaudio] pid.c: Daemon already running. Mar 10 19:32:46 pc56 pulseaudio[1499]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk ProcCwd: /home/prohlep Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 SegvAnalysis: Segfault happened at: 0x7f43f443e5a9:mov(%rbx),%rdi PC (0x7f43f443e5a9) ok source "(%rbx)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: apport StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: apport-gtk crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-03-09 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1754877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions
It should be noted that I recently released e2fsprogs 1.44.0 (currently in Debian Unstable, should hopefully hit Debian Testing in three more days) which turns on Metadata Checksums for everyone. https://packages.debian.org/sid/e2fsprogs Pulling in 1.44.0 into 18.04 LTS would be nice since it supports two new features, largedir and ea_inode, (neither turned on by default yet, but the second in particular is very useful for Samba servers since it was written specifically to efficiently support Windows ACL's and Security ID's better than any other file system by supporting xattr dedupe.) http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.44.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750174] Re: FFe: Update gnome-control-center to 3.27.90
** Also affects: humanity-icon-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1750174 Title: FFe: Update gnome-control-center to 3.27.90 Status in gnome-control-center package in Ubuntu: Triaged Status in humanity-icon-theme package in Ubuntu: New Bug description: FFe Justification - This upgrade was ready a little bit late because we wanted to fix some regressions identified in testing the new version instead of rushing it in. News https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/NEWS To Do - 1. The app icon was renamed from 'preferences-system' to 'gnome- control-center'. We'll want to update humanity-icon-theme and the Ubuntu Budgie default themes. But there is a naming issue with gnome- icon-theme so let's hold off on changing icon themes until that gets resolved: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/3 2. You can't maximize the Settings app (button is there, but doesn't work). Maybe only affects when run in a VM? Done 1. Rebase 70_allow_sound_above_100.patch (This patch has been somewhat upstreamed. However, the upstream feature is incomplete without the gnome-settings-daemon patches that haven't been accepted upstream yet. Also, the upstream gsettings schema for this feature has a different name than the Ubuntu schema. Didier's plan was to keep using the Ubuntu schema name until the gnome-settings-daemon patches were accepted. After that, we'll need a way to migrate the gsettings schema.) -> rebasing is done, keeping the same gsettings key than in artful. 2. Background panel redesign (didn't land for 3.28 so never mind) 3. The default 'faces' (user avatars) were changed and there was an upgrade issue. Other Info -- I believe this can be updated independently of gnome-settings-daemon or gnome-shell/mutter. Packages are available in the GNOME3 Staging PPA for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1750174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming
I recently released e2fsprogs 1.44.0 (currently in Debian Unstable, should hopefully hit Debian Testing in three more days) which turns on Metadata Checksums for everyone. https://packages.debian.org/sid/e2fsprogs Pulling in 1.44.0 supports two new features, largedir and ea_inode, (neither turned on by default yet, but the second in particular is very useful for Samba servers since it was written specifically to efficiently support Windows ACL's and Security ID's better than any other file system by supporting xattr dedupe.) http://e2fsprogs.sourceforge.net/e2fsprogs-release.html#1.44.0 In general e2fsprogs has a very conservative release process, and there have been a *large* number of bug fixes since e2fsprogs 1.42.13. (Including some that can cause horrible file system corruption and data loss if you do off-line resize2fs operations (resizing the file system while the file system is not mounted) under some circumstances. So if you are using distribution with that has e2fsprogs 1.42.13, on the misguided assumption that staying on an ancient version of e2fsprogs is "safer" --- that is simply not true. One caveat: in 1.44.0 I started relying on dpkg build profiles in debian/rules. This means e2fsprogs 1.44.0 no longer builds out of the box for Debian 7 (wheezy, aka Debian old-old-stable) and Ubuntu Trusty (14.04 LTS) and older releases. It should be possible to backport e2fsprogs 1.44.0 to 14.04 LTS, but at the very least 14.04 LTS should go to 1.43.9 to fix a huge number of bugs. But for 16.04, e2fsprogs 1.44.0 should just drop right in. And with 14.04 LTS and older, e2fsprogs 1.43.9 should Just Work. It wouldn't be that hard to make e2fsprogs 1.44.0 work on 14.04 LTS, but it won't be turn-key. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming Status in e2fsprogs package in Ubuntu: Triaged Bug description: In the Trusty release notes "Metadata checksumming" is listed as one of the tech highlights of kernel 3.13. https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS However, the userland tools do not support this kernel feature. To the best of my knowledge this will be supported in 1.43, and won't be backported to 1.42. IMHO this is very misleading. It's like a car salesperson sold you a sports car with an V8 engine. After you drove it home, you opened the hood and realized only 6 cylinders are working because 2 of the spark plugs were not included, and you have to buy aftermarket ones. BTW, I've been following the development of e2fsprogs for over a year. 1.43 release has been in limbo for God knows how long :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions
I'll try to get core dev's attention this week; it'd require a Feature Freeze Exception (FFE) now to get v1.44.0 into 18.04 but as an LTS it would be better to have it from the start - and decide on the default installer/mkfs flags now rather than have users suffer later. >From that we could possibly release it to 16.04 xenial-backports. Not sure about 14.04 trusty though. The latest kernel for 14.04 is v4.4 (the GA 16.04 kernel). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750174] Re: FFe: Update gnome-control-center to 3.27.90
** Tags removed: block-proposed ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1750174 Title: FFe: Update gnome-control-center to 3.27.90 Status in gnome-control-center package in Ubuntu: Triaged Status in humanity-icon-theme package in Ubuntu: New Bug description: FFe Justification - This upgrade was ready a little bit late because we wanted to fix some regressions identified in testing the new version instead of rushing it in. News https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/NEWS To Do - 1. The app icon was renamed from 'preferences-system' to 'gnome- control-center'. We'll want to update humanity-icon-theme and the Ubuntu Budgie default themes. But there is a naming issue with gnome- icon-theme so let's hold off on changing icon themes until that gets resolved: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/3 2. You can't maximize the Settings app (button is there, but doesn't work). Maybe only affects when run in a VM? Done 1. Rebase 70_allow_sound_above_100.patch (This patch has been somewhat upstreamed. However, the upstream feature is incomplete without the gnome-settings-daemon patches that haven't been accepted upstream yet. Also, the upstream gsettings schema for this feature has a different name than the Ubuntu schema. Didier's plan was to keep using the Ubuntu schema name until the gnome-settings-daemon patches were accepted. After that, we'll need a way to migrate the gsettings schema.) -> rebasing is done, keeping the same gsettings key than in artful. 2. Background panel redesign (didn't land for 3.28 so never mind) 3. The default 'faces' (user avatars) were changed and there was an upgrade issue. Other Info -- I believe this can be updated independently of gnome-settings-daemon or gnome-shell/mutter. Packages are available in the GNOME3 Staging PPA for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1750174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs
** Summary changed: - Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions + Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750174] Re: FFe: Update gnome-control-center to 3.27.90
This bug was fixed in the package humanity-icon-theme - 0.6.15 --- humanity-icon-theme (0.6.15) bionic; urgency=medium * Add symlinks to handle gnome-control-center 3.28's new icon name (LP: #1750174) * Build-Depend on scour instead of python3-scour -- Jeremy Bicha Sat, 10 Mar 2018 18:12:18 -0500 ** Changed in: humanity-icon-theme (Ubuntu) Status: New => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to humanity-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1750174 Title: FFe: Update gnome-control-center to 3.27.90 Status in gnome-control-center package in Ubuntu: Fix Released Status in humanity-icon-theme package in Ubuntu: Fix Released Bug description: FFe Justification - This upgrade was ready a little bit late because we wanted to fix some regressions identified in testing the new version instead of rushing it in. News https://gitlab.gnome.org/GNOME/gnome-control-center/blob/master/NEWS To Do - 1. The app icon was renamed from 'preferences-system' to 'gnome- control-center'. We'll want to update humanity-icon-theme and the Ubuntu Budgie default themes. But there is a naming issue with gnome- icon-theme so let's hold off on changing icon themes until that gets resolved: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/3 2. You can't maximize the Settings app (button is there, but doesn't work). Maybe only affects when run in a VM? Done 1. Rebase 70_allow_sound_above_100.patch (This patch has been somewhat upstreamed. However, the upstream feature is incomplete without the gnome-settings-daemon patches that haven't been accepted upstream yet. Also, the upstream gsettings schema for this feature has a different name than the Ubuntu schema. Didier's plan was to keep using the Ubuntu schema name until the gnome-settings-daemon patches were accepted. After that, we'll need a way to migrate the gsettings schema.) -> rebasing is done, keeping the same gsettings key than in artful. 2. Background panel redesign (didn't land for 3.28 so never mind) 3. The default 'faces' (user avatars) were changed and there was an upgrade issue. Other Info -- I believe this can be updated independently of gnome-settings-daemon or gnome-shell/mutter. Packages are available in the GNOME3 Staging PPA for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1750174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750174] Re: FFe: Update gnome-control-center to 3.27.90
This bug was fixed in the package gnome-control-center - 1:3.27.92-1ubuntu1 --- gnome-control-center (1:3.27.92-1ubuntu1) bionic; urgency=medium [ Jeremy Bicha ] * Sync with Debian. (LP: #1750174, LP: #1752928, LP: #1691867) Remaining changes: + debian/control.in: - Depend on fonts-ubuntu, language-selector-gnome, and whoopsie-preferences - Depend on instead of Recommend network-manager-gnome and system-config-printer-common - Recommend ibus, unity-control-center-faces, & ubuntu-system-service - Suggest instead of Recommend realmd and rygel - Build-Depend on libwhoopsie-preferences-dev + Split gnome-control-center-faces to a separate package so that it can be used by unity-control-center + Install apport hook + debian/gnome-control-center-data.install: - Don't install gnome-control-center.pkla since we use policykit-desktop-privileges instead - Install additional assets used by unity-control-center * debian/ubuntu-logo-icon.png, debian/source/include-binaries, debian/gnome-control-center-data.install: Include an Ubuntu logo * debian/gnome-control-center-data.links: - Link audio-speaker-center* to audio-speaker-mono* so that an icon is shown in the test speaker panel. (LP: #1704002) + debian/rules: Enable whoospie integration + debian/patches: - 08_lowercase_user_names.patch: Disallow upper-case letters in user names for compliance with adduser - 52_region_language.patch: Adapt region panel to use Ubuntu style regions - 64_restore_terminal_keyboard_shortcut.patch Bring back terminal shortcut - 70_allow_sound_above_100.patch: Allow setting volume above 100% in the Ubuntu session - 71_ubuntu_dock_settings.patch Add Dock panel for Ubuntu session - 99_add_lock-on-suspend.patch Add option to lock on suspend - ubuntu-gnome-version.patch: Add Ubuntu branding to Details panel - ubuntu-region-packagekit.patch fix detection of installed language packs - ubuntu-region-langpack-install.patch: check for missing language packs when loading region panel to pull in packs that arent included with the installer - ubuntu-language-support.patch Add Language Support button to Region & Language panel to work around (LP: #1631750) - ubuntu-printer-support.patch Add Advanced Printer Settings button to work around missing printer sharing feature (LP: #1718083) - ubuntu-legacy-notifications.patch Ubuntu ships compatibility names for .desktop that got renamed upstream, those use NoDisplay but the panel doesn't respect that key, skip known buggy entries for file-roller and nautilus (LP: #1716267) - connectivity-switch.patch Add Connectivity Checking switch to Privacy panel - privacy-panel-whoopsie.patch Support Ubuntu's whoopsie service in the Privacy panel - ubuntu-white-lists.patch Ensure lists have white background when used with Ambiance & Radiance * Update connectivity-switch.patch with latest version proposed to GNOME * Drop patches applied in new release: - gnome-desktop327.patch - monospace-wifihotspot-password.patch - search-provider-locale.patch [ Didier Roche ] * Rebased 70_allow_sound_above_100.patch * Dep on latest gsettings-desktop-schemas for binary gnome-control-center (1:3.27.92-1) unstable; urgency=medium * New upstream release candidate * Build with meson * Build-Depend on policykit-1 for itstool rules * Build-Depend on networkmanager-dev * Bump minimum gnome-desktop3 and gsettings-desktop-schemas * Bump debhelper compat to 11 * Bump Standards-Version to 4.1.3 gnome-control-center (1:3.26.2-1) unstable; urgency=medium * New upstream release * Recommend gnome-user-docs instead of transitional package gnome-user-guide * Drop debian/patches/fix-about-desktop.patch, merged upstream * Switch to dh_missing and abort on uninstalled files gnome-control-center (1:3.26.1-2) unstable; urgency=medium * Release to unstable * Add fix-about-desktop.patch: - Fix launching About panel (LP: #1721802) * Bump Standards-Version to 4.1.1 gnome-control-center (1:3.26.1-1) experimental; urgency=medium * Team upload * New upstream release gnome-control-center (1:3.26.0-1) experimental; urgency=medium * Team upload * debian/watch: Go back to checking for stable versions only * New upstream stable release gnome-control-center (1:3.25.92.1-1) experimental; urgency=medium * Team upload * debian/watch: Check for development versions too * New upstream release - Increase build and runtime dependencies as per configure.ac * Add Suggests: gnome-software | gnome-packagekit, for Updates button in overview panel -- Jeremy Bicha Sat, 10 Mar 2018 15:
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs
E2fsprogs 1.44.0 now depends on dpkg build-profiles, which means that getting it backported to 14.04 LTS would require adjusting debian/control and debian/rules a bit. For 14.04 LTS, I'd urge consideration of going to e2fsprogs 1.43.9. This will get you most of the latest bug fixes, including some that could cause massive file system corruption and data loss (relative to e2fsprogs 1.42.x) in the right (wrong) circumstances. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
Regarding my comment #43: The solution suggested in #46 doesn't work. While it does force 1920x1080, even after login, the nvidia driver is not working. lspci -v does show "Kernel driver in use: nvidia" for the card, but nvidia-settings behaves as if the driver is not loaded and glxinfo shows llvmpipe as the OpenGL renderer. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I have the same problem with Kopano packeges and php 7.0. In fact I even don't know why there is a conflict and a problem to solve this. libсurl3 should install /usr/lib/x86_64-linux-gnu/libcurl.so.3 and libcurl4 /usr/lib/x86_64-linux-gnu/libcurl.so.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Invalid Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf
Just had the idea to unload "glx" and see if I can Disable Composite without crashing Xorg / startx / xinit. It works! Here's my xorg.conf: Section "Module" Disable "glx" EndSection Section "Extensions" Option "Composite" "0" EndSection I'll put my resulting Xorg.0.log as an attachment. However logically this prevents me from getting DRI (which I need), while glxinfo saying: "LIBGL_DEBUG=verbose glxinfo name of display: :0 Error: couldn't find RGB GLX visual or fbconfig" Interesting though that Xorg no longer crashes with Composite being disabled when I disable the glx module at the same time. ** Summary changed: - [bionic] startx / xinit crashes with Composite Disabled in xorg.conf + [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf ** Attachment added: "Xorg.0.log.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5075590/+files/Xorg.0.log.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1754296 Title: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf Status in xorg package in Ubuntu: New Bug description: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite extension prevents tearing in (some) games and sometimes is an additional performance boost. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bionic). I tested with the mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and bionic. Xserver will crash with "Option "Composite" "0/False/Disable" When I comment out the specific line in the Extensions section (that means *enabling* Composite) it works again with this xorg.conf. I can also do other stuff like disabling DRI3 or AIGLX. No crashes in these cases. My xorg.conf: Section "Device" Identifier "Intel GMA45" ##just a trivial name as Identifier Driver "intel" EndSection Section "Extensions" Option "Composite" "0" EndSection It has a backtrace and caughts signal 6. My Xorg.0.log: [ 35.779] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 35.781] X Protocol Version 11, Revision 0 [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64 [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash [ 35.787] Build Date: 22 February 2018 08:04:42PM [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 35.789] Current version of pixman: 0.34.0 [ 35.792] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: Wed Mar 7 22:43:35 2018 [ 35.801] (==) Using config file: "/etc/X11/xorg.conf" [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 35.803] (==) No Layout section. Using the first Screen section. [ 35.803] (==) No screen section available. Using defaults. [ 35.803] (**) |-->Screen "Default Screen Section" (0) [ 35.803] (**) | |-->Monitor "" [ 35.804] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset" [ 35.804] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 35.804] (==) Automatically adding devices [ 35.804] (==) Automatically enabling devices [ 35.804] (==) Automatically adding GPU devices [ 35.804] (==) Automatically binding GPU devices [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 35.809] Entry deleted from font path. [ 35.822] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules" [ 35.822] (**) Extension "Composite" is disabled [ 35.822] (II) The server relies on udev to provide the list of input devi
[Touch-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf
Maybe this is i915/i965 intel driver related. If someone with an in intel IGP could reproduce this. I have xserver-xorg-video-intel installed by the way. With not mentioning "intel" explicitly as the driver in xorg.conf doesn't it automatically uses modesetting or glamorgl? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1754296 Title: [bionic] startx / xinit crashes with GLX backtrace if Composite Disabled in xorg.conf Status in xorg package in Ubuntu: New Bug description: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite extension prevents tearing in (some) games and sometimes is an additional performance boost. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bionic). I tested with the mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and bionic. Xserver will crash with "Option "Composite" "0/False/Disable" When I comment out the specific line in the Extensions section (that means *enabling* Composite) it works again with this xorg.conf. I can also do other stuff like disabling DRI3 or AIGLX. No crashes in these cases. My xorg.conf: Section "Device" Identifier "Intel GMA45" ##just a trivial name as Identifier Driver "intel" EndSection Section "Extensions" Option "Composite" "0" EndSection It has a backtrace and caughts signal 6. My Xorg.0.log: [ 35.779] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 35.781] X Protocol Version 11, Revision 0 [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64 [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash [ 35.787] Build Date: 22 February 2018 08:04:42PM [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 35.789] Current version of pixman: 0.34.0 [ 35.792] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: Wed Mar 7 22:43:35 2018 [ 35.801] (==) Using config file: "/etc/X11/xorg.conf" [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 35.803] (==) No Layout section. Using the first Screen section. [ 35.803] (==) No screen section available. Using defaults. [ 35.803] (**) |-->Screen "Default Screen Section" (0) [ 35.803] (**) | |-->Monitor "" [ 35.804] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset" [ 35.804] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 35.804] (==) Automatically adding devices [ 35.804] (==) Automatically enabling devices [ 35.804] (==) Automatically adding GPU devices [ 35.804] (==) Automatically binding GPU devices [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 35.809] Entry deleted from font path. [ 35.822] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules" [ 35.822] (**) Extension "Composite" is disabled [ 35.822] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 35.822] (II) Loader magic: 0x55cfd2964020 [ 35.822] (II) Module ABI versions: [ 35.822] X.Org ANSI C Emulation: 0.4 [ 35.822] X.Org Video Driver: 23.0 [ 35.822] X.Org XInput driver : 24.1 [ 35.822] X.Org Server Extension : 10.0 [ 35.824] (++) using VT number 1 [ 35.827] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0) [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 0xd0
[Touch-packages] [Bug 1754921] Re: systemd-journald crashed with SIGABRT in fsync()
*** This bug is a duplicate of bug 1750855 *** https://bugs.launchpad.net/bugs/1750855 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1750855, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1754921/+attachment/5075591/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754921/+attachment/5075594/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754921/+attachment/5075600/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754921/+attachment/5075602/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754921/+attachment/5075603/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754921/+attachment/5075604/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754921/+attachment/5075605/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1750855 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754921 Title: systemd-journald crashed with SIGABRT in fsync() Status in systemd package in Ubuntu: New Bug description: Just after booting. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Mar 10 19:47:42 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-03-08 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307) JournalErrors: -- Logs begin at Sat 2018-03-10 11:26:25 EET, end at Sun 2018-03-11 08:02:14 EET. -- мар 11 07:30:38 hostname systemd-udevd[409]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0xc022d, key code 103): Invalid argument мар 11 07:30:38 hostname systemd-udevd[409]: Error calling EVIOCSKEYCODE on device node '/dev/input/event4' (scan code 0xc022e, key code 108): Invalid argument мар 11 07:30:44 hostname spice-vdagent[2673]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0 мар 11 07:31:08 hostname pulseaudio[2555]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) MachineType: Intel Thurley ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=ru_UA.UTF-8 LANGUAGE=ru_UA:ru PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=76ae456f-1793-40e3-ac19-2829d2667881 ro quiet splash vt.handoff=1 Signal: 6 SourcePackage: systemd StacktraceTop: fsync (fd=27) at ../sysdeps/unix/sysv/linux/fsync.c:27 ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so ?? () from /lib/systemd/libsystemd-shared-237.so journal_file_append_entry () from /lib/systemd/libsystemd-shared-237.so SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-journald crashed with SIGABRT in fsync() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/13/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: X58 dmi.board.vendor: Mainboard dmi.board.version: V3.10 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Intel dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/13/2017:svnIntel:pnThurley:pvrToBeFilledByO.E.M.:rvnMainboard:rnX58:rvrV3.10:cvnIntel:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: High-End Desktop dmi.product.name: Thurley dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Int
[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming
Given your other comment (which I think may have been posted to the wrong thread):- [E2fsprogs 1.44.0 now depends on dpkg build-profiles, which means that getting it backported to 14.04 LTS would require adjusting debian/control and debian/rules a bit. For 14.04 LTS, I'd urge consideration of going to e2fsprogs 1.43.9. This will get you most of the latest bug fixes, including some that could cause massive file system corruption and data loss (relative to e2fsprogs 1.42.x) in the right (wrong) circumstances.] --are you saying that 1.39.9/1.44.0 ought to not only go to trusty-backports and xenial-backports, but also then into 'updates' to be 'pushed to all users' -- that needs some fiddly SRU process ? I note Debian haven't pushed such an update back to jessie/wheezy either. I (suspect) Canonical will require significant 'evidence'/'bug-reports' for backports to become 'updates' in this circumstance... HOPEFULLY 1.44.0 into bionic will be easier. Hope that helps, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming Status in e2fsprogs package in Ubuntu: Triaged Bug description: In the Trusty release notes "Metadata checksumming" is listed as one of the tech highlights of kernel 3.13. https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS However, the userland tools do not support this kernel feature. To the best of my knowledge this will be supported in 1.43, and won't be backported to 1.42. IMHO this is very misleading. It's like a car salesperson sold you a sports car with an V8 engine. After you drove it home, you opened the hood and realized only 6 cylinders are working because 2 of the spark plugs were not included, and you have to buy aftermarket ones. BTW, I've been following the development of e2fsprogs for over a year. 1.43 release has been in limbo for God knows how long :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
I don't understand the conflict between libcurl3 and libcurl4 too, why can't they coexist? Still wondering how to handle that while keeping opera. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Invalid Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs
Can we pay-attention, to this thread (now) being about considering the feature-flags 'used by default' in mke2fs.conf, in consideration to 18.04 -- [linked bug for e2fsprogs]. We know massive 'compatibility'/portability benefit of formatting the same as previous-LTS by default, as the required e2fsprogs was only introduced 16.10, and the needed kernel was only in 16.04 (and 14.04 -HWE-kernel-update.). NB: Looks like there is a similar issue with GRUB2 which affects dual-booters, grub2 2.02beta3 may be needed to support 64bit FS. If so, again Xenial isn't compatible to detect an 18.04 in multi-boot-menu. I'd like tytso to comment on the downsides of formatting without 64bit,metadata_csum, more specifically. From what I can (see) this only loses a little extra checksumming-integrity (against bad disks, which we've never needed before??), and the 64bit feature appears only to be needed to strengthen these checksums or support >16TB disks (bearing in mind auto_64bit_support can still be used). NB: Is this correct, -OR- is there likely going to be future annoyances with 'other' ext4 features-to-come which will ALSO expect 64bit formatting?. My suggestion is, this hasn't been sorted-out enough in the ubuntu- world, and 64bit,metadata_csum should be disabled-by-default for 18.04 and backporting grub/e2fsprogs/etc where relevant should happen as well [see other thread, possibly another may be created for grub2]. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp