[Touch-packages] [Bug 1812683] Re: rhythmbox crashes when trying to play music
This might be a dupe of bug #1801436 as it only happens with the alternative-toolbar plugin that was enabled by default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1812683 Title: rhythmbox crashes when trying to play music Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault. 0x77183384 in gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x77183384 in gtk_tree_view_get_column () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x76ecd5fa in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x76ece792 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x76ecf445 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7718d1fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x710bedae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #6 0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #7 0x76be3ced in g_cclosure_marshal_generic_va () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7700f7fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7700c78e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x7700dcdb in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0x7701099e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #19 0x76fde1e1 in gtk_event_controller_handle_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #20 0x7719d85b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x77b46642 in () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #22 0x7705815b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #23 0x76be310d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x76bf605e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x76bfe0af in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x7719fb04 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #28 0x770551ce in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #29 0x770572a8 in gtk_main_do_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x75323765 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #31 0x75353f82 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #32 0x76909387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x769095c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7690964c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x737e7e3d in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #36 0x77aa0b09 in rb_application_run () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #37 0x4d57 in main () ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 16:14:12 2019 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1812683/+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 1783499] Re: systemd: Failed to send signal
Please let the hardware vendor know. This is highly likely a platform bug. AFAICT, systemd has done its part, so the bug is either in the kernel (less likely) or in the BIOS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1812683] Re: rhythmbox crashes when trying to play music
(gdb) bt #0 0x77183384 in gtk_tree_view_get_column (tree_view=tree_view@entry=0x55e847f0 [GtkTreeView], n=n@entry=16) at ../../../../gtk/gtktreeview.c:12343 #1 0x76ecf5da in _gtk_tree_view_accessible_add_state (treeview=0x55e847f0 [GtkTreeView], tree=tree@entry=0x55f801c0, node=node@entry=0x56aca100, state=state@entry=GTK_CELL_RENDERER_SELECTED) at ../../../../gtk/a11y/gtktreeviewaccessible.c:1993 #2 0x771727f9 in gtk_tree_selection_real_select_node (selection=selection@entry=0x55e24610 [GtkTreeSelection], tree=tree@entry=0x55f801c0, node=node@entry=0x56aca100, select=select@entry=1) at ../../../../gtk/gtktreeselection.c:1632 #3 0x77173146 in _gtk_tree_selection_internal_select_node (selection=0x55e24610 [GtkTreeSelection], node=0x56aca100, tree=0x55f801c0, path=0x55c58500, mode=, override_browse_mode=0) at ../../../../gtk/gtktreeselection.c:1585 #4 0x771861c8 in gtk_tree_view_real_set_cursor (tree_view=tree_view@entry=0x55e847f0 [GtkTreeView], path=path@entry=0x55c58500, flags=flags@entry=(CLEAR_AND_SELECT | CLAMP_NODE)) at ../../../../gtk/gtktreeview.c:13306 #5 0x7718d4e9 in gtk_tree_view_multipress_gesture_pressed (gesture=0x55e7d430 [GtkGestureMultiPress], n_press=1, x=, y=, tree_view=0x55e847f0 [GtkTreeView]) at ../../../../gtk/gtktreeview.c:3379 #6 0x710bedae in ffi_call_unix64 () ---Type to continue, or q to quit--- .so.6 #7 0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #8 0x76be3ced in g_cclosure_marshal_generic_va (closure=0x55e939f0, return_value=0x0, instance=, args_list=, marshal_data=, n_params=3, param_types=0x559f4940) at ../../../../gobject/gclosure.c:1604 #9 0x76be3346 in _g_closure_invoke_va (closure=0x55e939f0, return_value=0x0, instance=0x55e7d430, args=0x7fffcd70, n_params=3, param_types=0x559f4940) at ../../../../gobject/gclosure.c:867 #10 0x76bfe9ff in g_signal_emit_valist (instance=0x55e7d430, signal_id=, detail=, var_args=var_args@entry=0x7fffcd70) at ../../../../gobject/gsignal.c:3300 #11 0x76bff12f in g_signal_emit (instance=instance@entry=0x55e7d430, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447 #12 0x7700f7fc in gtk_gesture_multi_press_begin (gesture=0x55e7d430 [GtkGestureMultiPress], sequence=) at ../../../../gtk/gtkgesturemultipress.c:241 #13 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv (closure=0x55ab92d0, return_value=, instance=, args=, marshal_data=, n_params=, param_types=0x559aa9c0) at ../../../../gobject/gmarshal.c:1950 #14 0x76be3346 in _g_closure_invoke_va (closure=0x55ab92d0, return_value=0x0, instance=0x55e7d430, args=0x7fffd130, n_params=1, param_types=0x559aa9c0) at ../../../../gobject/gclosure.c:867 #15 0x76bfe9ff in g_signal_emit_valist (instance=0x55e7d430, signal_id=, detail=, var_args=var_args@entry=0x7fffd130) at ../../../../gobject/gsignal.c:3300 #16 0x76bff12f in g_signal_emit (instance=instance@entry=0x55e7d430, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447 #17 0x7700c78e in _gtk_gesture_set_recognized (sequence=0x0, recognized=1, gesture=0x55e7d430 [GtkGestureMultiPress]) at ../../../../gtk/gtkgesture.c:343 #18 0x7700c78e in _gtk_gesture_check_recognized (gesture=gesture@entry=0x55e7d430 [GtkGestureMultiPress], sequence=sequence@entry=0x0) at ../../../../gtk/gtkgesture.c:389 #19 0x7700dcdb in gtk_gesture_handle_event (controller=0x55e7d430 [GtkGestureMultiPress], event=0x5739f660) at ../../../../gtk/gtkgesture.c:747 #20 0x7701099e in gtk_gesture_single_handle_event (controller=0x55e7d430 [GtkGestureMultiPress], event=0x5739f660) at ../../../../gtk/gtkgesturesingle.c:222 #21 0x76fde1e1 in gtk_event_controller_handle_event (controller=0x55e7d430 [GtkGestureMultiPress], event=event@entry=0x5739f660) at ../../../../gtk/gtkeventcontroller.c:230 #22 0x7719d85b in _gtk_widget_run_controllers (widget=0x55e847f0 [GtkTreeView], event=0x5739f660, phase=GTK_PHASE_BUBBLE) at ../../../../gtk/gtkwidget.c:7379 #23 0x77b46642 in rb_tree_dnd_button_press_event_cb (widget=widget@entry=0x55e847f0 [GtkTreeView], event=0x5739f660, data=) at rb-tree-dnd.c:924 #28 0x76bff12f in (instance=instance@entry=0x55e847f0, signal_id=, detail=detail@entry=0) at ../../../../gobject/gsignal.c:3447 #24 0x7705815b in _gtk_marshal_BOOLEAN__BOXED (closure=0x55e952f0, return_value=0x7fffd500, n_param_values=, param_values=0x7fffd560, invocation_hint=, marshal_data=) at ../../../../gtk/gtkmarshalers.c:83 #25 0x76be310d in g_closure_invoke (closure=0x55e952f0, return_value=0x7fffd500,
[Touch-packages] [Bug 1685796] Re: systemctl -H user@host hangs after execution
This bug is affecting me in 2019, it looks like it was fixed in 2016: https://github.com/systemd/systemd/issues/3543#ref-commit-6590ca9 Is there a chance of getting this fix in 16.04? Is there anything I can do to help? ** Bug watch added: github.com/systemd/systemd/issues #3543 https://github.com/systemd/systemd/issues/3543 -- 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/1685796 Title: systemctl -H user@host hangs after execution Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.2 (x86_64) systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016 If I execute: systemctl -H root@127.0.0.1 restart networking The command is executed correctly but it hangs forever. If I run it localy: systemctl restart networking It is also executed correctly, but it does not hang at the end if the command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685796/+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 1373598] Re: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com
** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com Status in apt package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. "apt-get update" failed, and later "apt-get dist upgrade" It started with this when doing a normal "apt-get update" W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+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 1783499] Re: systemd: Failed to send signal
reboot=pci does not help, it get stuck after 19 hours (reboot once at 5 min). Attached is the debug log. On ILO we get the same as I sent in my first post - see capture from the arhive. We'll update systemd to 237 and test it. ** Attachment added: "shutdown-log-reboot-pci.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5231295/+files/shutdown-log-reboot-pci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1763628] Re: autopkgtests are failing on valgrind
autopkgtests pass now in cosmic and in disco (well once my 1.4.3-4 upload autosyncs in a few hours). Do you think it's worth doing a bionic SRU if we can identify what fixed the autopkgtests in newer versions? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1763628 Title: autopkgtests are failing on valgrind Status in colord package in Ubuntu: New Bug description: This happens now autopkgtest [07:42:07]: test make-check: ---] autopkgtest [07:42:08]: test make-check: - - - - - - - - - - results - - - - - - - - - - make-check FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368 autopkgtest [07:42:08]: test make-check: - - - - - - - - - - stderr - - - - - - - - - - ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368 ==9257==at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9257==by 0x18EF2D: xmalloc (in /bin/bash) ==9257==by 0x18898A: set_default_locale (in /bin/bash) ==9257==by 0x137E66: main (in /bin/bash) ==9257== ==9505== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368 ==9505==at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==9505==by 0x18EF2D: xmalloc (in /bin/bash) ==9505==by 0x18898A: set_default_locale (in /bin/bash) ==9505==by 0x137E66: main (in /bin/bash) ==9505== autopkgtest [07:42:08]: summary make-check FAIL stderr: ==9257== 8 bytes in 1 blocks are definitely lost in loss record 67 of 368 From http://autopkgtest.ubuntu.com/packages/c/colord/bionic/amd64 it looks like it's cause by the new glib2.0, but I just tried on my machine without that package and it still happened. Could you have a look please? Looks like it might not actually be colord's fault here, but maybe we want to reconsider running under valgrind at least for the autopktests? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1763628/+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 1799287] Re: usbmud service will not load on boot
[Expired for usbmuxd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: usbmuxd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to usbmuxd in Ubuntu. https://bugs.launchpad.net/bugs/1799287 Title: usbmud service will not load on boot Status in usbmuxd package in Ubuntu: Expired Bug description: I use usbmux for my iphone so I can access my photos via shotwell and move files around. I have to start the service manually via systemd. When I try to enable I get the following. hhernandez@hhernandez-Precision-M4800:~$ sudo systemctl enable usbmuxd [sudo] password for hhernandez: The unit files have no installation config (WantedBy, RequiredBy, Also, Alias settings in the [Install] section, and DefaultInstance for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). 4) In case of template units, the unit is meant to be enabled with some instance name specified. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: usbmuxd 1.1.0-2build1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Mon Oct 22 13:04:24 2018 SourcePackage: usbmuxd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usbmuxd/+bug/1799287/+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 1812271] Re: Ubuntu 18.04.1, "Bad packet length nnnn."
** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812271/+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 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Tags added: sts -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd package in Ubuntu: In Progress Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812760/+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 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Merge proposal linked: https://code.launchpad.net/~daxtens/ubuntu/+source/systemd/+git/systemd/+merge/362057 -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd package in Ubuntu: In Progress Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812760/+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 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Merge proposal linked: https://code.launchpad.net/~daxtens/ubuntu/+source/systemd/+git/systemd/+merge/362056 -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd package in Ubuntu: In Progress Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812760/+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 1201128] Re: missing icons for .directory files
This bug was fixed in the package gnome-menus - 3.31.4-2ubuntu1 --- gnome-menus (3.31.4-2ubuntu1) disco; urgency=medium * Sync with Debian. Remaining changes: - debian/gnome-menus.postinst, debian/gnome-menus.prerm, debian/gnome-menus.dirs: + Remove since we don't use the Debian GNOME menu blacklist - debian/gnome-menus.triggers: Drop "gmenucache". - Add 09_app_install_entry.patch: + Add Ubuntu Software / GNOME Software to the traditional apps menu - Add 70_ubuntu-directories.patch + Add Ubuntu-specific directories back to POTFILES.in - Add ubuntu_gcc_translations.patch: + Make the unity-control-center categories translatable (lp: #1515911) - Add 80_file_monitor_delayed.patch: + Fix app menus not updating correctly after app install or removal gnome-menus (3.31.4-2) unstable; urgency=medium * Follow upstream and stop using intltool for our update-po rule * Run debian/rules update-po * Add translate-Debian-directories.patch from Ubuntu * Run dh_auto_test gnome-menus (3.31.4-1) unstable; urgency=medium * New upstream release - Drop the Sundry menu * Drop obsolete Build-Depends on intltool * Refresh patches * Drop 12_alacarte.path: obsolete with new release gnome-menus (3.31.3-1) unstable; urgency=medium * New upstream release: - Includes updates for renamed .desktop files * Bump debhelper compat to 11 * Update Vcs fields for migration to https://salsa.debian.org/ * Add -Wl,-O1 to our LDFLAGS * Bump Standards-Version to 4.3.0 * debian/desktop-files/: - Update some of the directory icon names (LP: #1201128) * Drop patches applied in new release: - 03_kde-legacydirs.patch - 30_xdg_syntax.patch - 31_nl_translation.patch * Refresh patches -- Jeremy Bicha Mon, 21 Jan 2019 20:19:06 -0500 ** Changed in: gnome-menus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1201128 Title: missing icons for .directory files Status in gnome-icon-theme package in Ubuntu: Confirmed Status in gnome-menus package in Ubuntu: Fix Released Bug description: Directory files have been shipped with incorrect Icon= fields. For example, ActionGames.directory contains Icon=weather-storm. This should instead read Icon=applications-action (1) which is included in many icon sets (2), leaving this kind of substitution to the theme author using symlinks. Including references to these substitutions directly in the .directory files is an inappropriate and unecessary kludge which breaks themes, including the default one. I've only checked the Games .directory files so far, since that is what I was doing when I encountered the bug, but they all exhibit this problem. I'm using Ubuntu 13.04, but it's the kind of thing that could have been sitting undone for a while. It's probably worth checking whether this bug exists upstream or whether it's been introduced by the Ubuntu team. Upon further checking, Bug #421294 is a particular case of this bug, where the line reads Icon=system-run rather than Icon=applications- puzzles. From this report and Bug #421695 it seems likely that this bug was introduced in Karmic. (1) or similar - I'm not entirely sure on whether this will shake out as applications-action or applications-games-action; Gnome currently goes one way and KDE the other but, either way, symlinks are cheap and it can be sorted out through freedesktop. (2) Ubuntu's own Humanity icon set includes icons of this form, but they are not used because of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-icon-theme/+bug/1201128/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
Kai-Heng Feng, What's the status of the kernel fix in bionic? As to verify UI fixes we should get everything in. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/362055 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Committed Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Confirmed Status in gnome-control-center source package in Bionic: New Status in gnome-shell source package in Bionic: New Status in linux source package in Bionic: New Status in upower source package in Bionic: New Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1812760] [NEW] networkd: [Route] PreferredSource not working in *.network files
Public bug reported: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Daniel Axtens (daxtens) Status: In Progress ** Changed in: systemd (Ubuntu) Status: Confirmed => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Daniel Axtens (daxtens) -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd package in Ubuntu: In Progress Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the
[Touch-packages] [Bug 1812744] Re: resolved uses only per-link dns servers
** Attachment added: "Screenshot from 2019-01-21 23-11-46.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+attachment/5231234/+files/Screenshot%20from%202019-01-21%2023-11-46.png -- 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/1812744 Title: resolved uses only per-link dns servers Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812744] Re: resolved uses only per-link dns servers
turns of DNS automatic => turn off automatic DNS -- 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/1812744 Title: resolved uses only per-link dns servers Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812744] Re: resolved uses only per-link dns servers
That is intentionally done by NM to prevent leaking DNS queries. Which is privacy sensitive (ie. do _not_ use "public" dns, to query VPN encrypted hostnames). If you do not want to use router configured DNS servers, you can specify per-connection DNS server overrides in network-manager, which is imho what you should be doing. Ie. wipe the resolved.conf settings of DNS=, go into system settings into each of your connections (ie. the wlan & ethernet one) and in ipv4/ipv6 tabs, turns of DNS automatic, and specify manual DNS servers there. Then NM will push those to resolved (note you will need to reconnect). It's best to use per-connection DNS servers, and specifically per connection DNS overrides and configure that all in NM. Do not override / provide fallbacks in resolved.conf. It is poor taste. ** Changed in: network-manager (Ubuntu) Status: New => Invalid ** 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/1812744 Title: resolved uses only per-link dns servers Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1373598] Re: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches with de.archive.ubuntu.com Status in apt package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. "apt-get update" failed, and later "apt-get dist upgrade" It started with this when doing a normal "apt-get update" W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Sep 24 21:57:55 2014 InstallationDate: Installed on 2013-05-09 (503 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to trusty on 2014-05-04 (142 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373598/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
I've just been bitten by this bug while upgrading our business PXE/preseed installations from Xenial to Bionic. We use an internal private repository for company specific packages. I'm unable to get the apt key installed with the preseed, so nothing works. I'm going to attempt the workaround mentioned above. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1807262] Re: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp
Reviewed: https://review.openstack.org/623564 Committed: https://git.openstack.org/cgit/openstack/sqlalchemy-migrate/commit/?id=231a4d2ae9f8496cfc8eea2e6bb8186a0dd602f9 Submitter: Zuul Branch:master commit 231a4d2ae9f8496cfc8eea2e6bb8186a0dd602f9 Author: Corey Bryant Date: Fri Dec 7 13:49:20 2018 -0500 Use legacy_alter_table ON in sqlite recreate_table Use "PRAGMA legacy_alter_table = ON" with sqlite >= 3.26 when using "ALTER TABLE RENAME TO migration_tmp" to maintain legacy behavior. As of sqlite version 3.26, when a table is renamed using "ALTER TABLE RENAME TO", REFERENCES clauses that refer to the table will be updated. To maintain legacy (3.24 and earlier) behavior, "PRAGMA legacy_alter_table" can be set to true and "PRAGMA foreign_keys" can be set to false. [1] [1] https://www.sqlite.org/src/info/ae9638e9c0ad0c36 Thanks to "László Böszörményi (GCS)" for providing the code for this patch, which has since been slightly modified. Change-Id: I539988ab2ad6df6c8f423ecec15364ad8fcc7267 Closes-Bug: 1807262 ** Changed in: sqlalchemy-migrate Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: Fix Released Status in cinder package in Ubuntu: Fix Released Status in migrate package in Ubuntu: Fix Released Status in nova package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+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 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]
This bug was fixed in the package valgrind - 1:3.14.0-2ubuntu4 --- valgrind (1:3.14.0-2ubuntu4) disco; urgency=medium * s390x Fix vector facility bit. valgrind (1:3.14.0-2ubuntu3) disco; urgency=medium * Cherrypick s390x/z13 fixes from valgrind master (3.15) LP: #1799696 valgrind (1:3.14.0-2ubuntu2) disco; urgency=medium * debian/patches/usrmerge_support.patch: make valgrind aware of usrmerge; if we can't find the debug files under the full objpath (including /usr), also try the alternative path by stripping out /usr. (LP: #1808508) valgrind (1:3.14.0-2ubuntu1) disco; urgency=medium * Merge with Debian; remaining changes: - Lower over-inflated valgrind-dbg Recommends to Suggests instead. - Don't strip vgpreload* on ARM; this results in unusable stack traces without valgrind-dbg. - Configure with --enable-only64bit on AArch64. - Enable parallel builds. valgrind (1:3.14.0-2) unstable; urgency=medium * Fix path in dh_shlibdeps argument on non-x86 arches (Closes: #913822) valgrind (1:3.14.0-1) unstable; urgency=medium * New upstream release (Closes: #913208) + Fix assertion `cfsi_fits` failing in simple C program (Closes: #909797) * Drop patches backported from upstream * Refresh patches * Bump Standards-Version to 4.2.1 (no changes needed) * Bump debhelper compat level to 11 * Update install paths * Use pkg-config to detect MPI to fix cross-build. Thanks to Helmut Grohne for the patch (Closes: #902297) -- Dimitri John Ledkov Mon, 21 Jan 2019 17:13:06 + ** Changed in: valgrind (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.] Status in base-files package in Ubuntu: Won't Fix Status in valgrind package in Ubuntu: Fix Released Bug description: $ valgrind /bin/ls ==25995== Memcheck, a memory error detector ==25995== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==25995== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info ==25995== Command: /bin/ls ==25995== valgrind: Fatal error at startup: a function redirection valgrind: which is mandatory for this platform-tool combination valgrind: cannot be set up. Details of the redirection are: valgrind: valgrind: A must-be-redirected function valgrind: whose name matches the pattern: strlen valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing valgrind: symbols from the object with soname: ld-linux-x86-64.so.2 valgrind: valgrind: Possible fixes: (1, short term): install glibc's debuginfo valgrind: package on this machine. (2, longer term): ask the packagers valgrind: for your Linux distribution to please in future ship a non- valgrind: stripped ld.so (or whatever the dynamic linker .so is called) valgrind: that exports the above-named function using the standard valgrind: calling conventions for this platform. The package you need valgrind: to install for fix (1) is called valgrind: valgrind:On Debian, Ubuntu: libc6-dbg valgrind:On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: valgrind 1:3.14.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Fri Dec 14 17:06:03 2018 InstallationDate: Installed on 2018-12-04 (10 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: valgrind UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Description changed: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. - While we understand it's not a "bug' and only a reference/example... + While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. - * ./doc/sources.list.5.xml | grep -i verbatim + * ./doc/sources.list.5.xml --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: In Progress Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: In Progress Bug
[Touch-packages] [Bug 1812744] Re: resolved uses only per-link dns servers
This is caused by network-manager pushing ~. as the search domain. This effectively makes resolved ignore the DNS servers I configured. I could fix this by adding Domains=~. to resolved.conf, but I don't know, this does not feel right - network-manager essentially breaks a resolved feature. ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1812744 Title: resolved uses only per-link dns servers Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1812744/+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 1812744] Re: resolved uses only per-link dns servers
bionic looks ok: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("1.1.1.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("1.1.1.1")}, 16) = 0 connect(17, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("10.33.102.1")}, 16) = 0 -- 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/1812744 Title: resolved uses only per-link dns servers Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+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 1812744] Re: resolved uses only per-link dns servers
https://paste.ubuntu.com/p/gxnC326J7b/ -- 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/1812744 Title: resolved uses only per-link dns servers Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+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 1325525] Re: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d
I can confirm that the issue is still present in 18.04: - 53-monospace-lcd-filter.conf is not linked into conf.d (not sure if it is a bug by itself) - when the file is linked into conf.d, the warning about broken config appears (this is definitely a bug) ** Changed in: fontconfig (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1325525 Title: Missing 53-monospace-lcd-filter.conf from /etc/fonts/conf.d Status in fontconfig package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu-trusty, and noticed that in Thunderbird the fonts are rendered incorrectly. It seemed that the problem is with sub-pixel rendering. After much googling and finding nothing I've started to compare the /etc/fonts/conf.d dir on my Precise machin with the trusty one. I noticed that on trusty the 53-monospace-lcd-filter.conf file is missing from the conf.d dir, but is available in the conf.avail. After I created the symlink and rebooted, my thunderbird font rendering became normal again. But now if I start from something from the terminal it says: "Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in isn't supported and may not work as expected" So the 1st question, why did you leave out the monospace-lcd- filter.conf from the fontconfig conf.d, and the second is why didn't you update it so it won't complaing about the multiple test tags. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Mon Jun 2 12:43:15 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-27-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:308c] MachineType: LENOVO 3492C4G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-27-generic root=UUID=a1bd4186-b465-4605-845f-12c9de2dc180 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2012 dmi.bios.vendor: LENOVO dmi.bios.version: F1KT44AUS dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrF1KT44AUS:bd12/21/2012:svnLENOVO:pn3492C4G:pvrThinkCentreEdge72:rvnLENOVO:rn:rvrNODPK:cvnLENOVO:ct3:cvr: dmi.product.name: 3492C4G dmi.product.version: ThinkCentre Edge72 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Mon Jun 2 12:37:17 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputLITEON Technology USB Multimedia Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16498 vendor DEL xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1325525/+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 1812683] Re: rhythmbox crashes when trying to play music
Could you install the dbgsym (https://wiki.ubuntu.com/Debug%20Symbol%20Packages) for glib, gtk and rhythmbox and get a debug backtrace? ** Changed in: gstreamer1.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1812683 Title: rhythmbox crashes when trying to play music Status in gstreamer1.0 package in Ubuntu: Incomplete Bug description: Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault. 0x77183384 in gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x77183384 in gtk_tree_view_get_column () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x76ecd5fa in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x76ece792 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x76ecf445 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7718d1fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x710bedae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #6 0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #7 0x76be3ced in g_cclosure_marshal_generic_va () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7700f7fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7700c78e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x7700dcdb in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0x7701099e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #19 0x76fde1e1 in gtk_event_controller_handle_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #20 0x7719d85b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x77b46642 in () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #22 0x7705815b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #23 0x76be310d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x76bf605e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x76bfe0af in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x7719fb04 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #28 0x770551ce in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #29 0x770572a8 in gtk_main_do_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x75323765 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #31 0x75353f82 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #32 0x76909387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x769095c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7690964c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x737e7e3d in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #36 0x77aa0b09 in rb_application_run () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #37 0x4d57 in main () ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 16:14:12 2019 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1812683/+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 1812744] Re: resolved uses only per-link dns servers
Can you please show your resolved config? E.g.: $ resolvectl --no-pager status | pastebinit -- 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/1812744 Title: resolved uses only per-link dns servers Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+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 1526956] Re: klibc does not support rfc3442; needed for netboot
This bug was fixed in the package klibc - 2.0.5-2 --- klibc (2.0.5-2) unstable; urgency=medium * Drop redundant patch "Include the multiarch include directory in klcc's path" * Drop "Fix klibc Debian specific build trouble" and introduce links in debian/rules * Fix up debug symbol support: - Use -Ttext-segment to link shared library on all arches (Closes: #919855) - Drop "kbuild: Enable build IDs" - Kbuild: Add option to install unstripped binaries - Kbuild: Enable full debug information - Set CONFIG_DEBUG_INFO instead of overriding STRIP -- Ben Hutchings Sun, 20 Jan 2019 22:49:25 + ** Changed in: klibc (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1526956 Title: klibc does not support rfc3442; needed for netboot Status in klibc package in Ubuntu: Fix Released Status in klibc package in Debian: Fix Released Bug description: klibc does not support classless static routes. If classes routing is used for a netboot device (NFS, iscsi) these devices will fail to boot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1526956/+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 1812744] Re: resolved uses only per-link dns servers
This is probably an upstream bug, but I'm not sure, so I went here first. -- 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/1812744 Title: resolved uses only per-link dns servers Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+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 1692494] Re: klibc does not support reboot arguments
This bug was fixed in the package klibc - 2.0.5-2 --- klibc (2.0.5-2) unstable; urgency=medium * Drop redundant patch "Include the multiarch include directory in klcc's path" * Drop "Fix klibc Debian specific build trouble" and introduce links in debian/rules * Fix up debug symbol support: - Use -Ttext-segment to link shared library on all arches (Closes: #919855) - Drop "kbuild: Enable build IDs" - Kbuild: Add option to install unstripped binaries - Kbuild: Enable full debug information - Set CONFIG_DEBUG_INFO instead of overriding STRIP -- Ben Hutchings Sun, 20 Jan 2019 22:49:25 + ** Changed in: klibc (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1692494 Title: klibc does not support reboot arguments Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Xenial: New Status in klibc package in Debian: Confirmed Bug description: ... so we cannot do things like "reboot recovery" in devices that follow the Android partitions conventions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1692494/+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 1812750] [NEW] Python stack trace when running `ubuntu-bug nautilus` in disco
Public bug reported: ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook symb['add_info'](report, ui) TypeError: add_info() takes 1 positional argument but 2 were given During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 210, in _run_hook symb['add_info'](report) File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in add_info report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages)) TypeError: '<' not supported between instances of 'NoneType' and 'str' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apport 2.20.10-0ubuntu19 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CrashReports: 640:0:119:606530:2019-01-21 14:49:01.440511009 -0500:2019-01-21 14:49:01.136510154 -0500:/var/crash/_opt_penguindome_client_client-cron.py.0.crash 640:0:119:2444106:2019-01-21 14:54:50.761487081 -0500:2019-01-21 14:54:48.449619152 -0500:/var/crash/_usr_lib_packagekit_packagekitd.0.crash 640:1000:119:3237446:2019-01-21 14:54:03.516504591 -0500:2019-01-21 14:54:00.808239070 -0500:/var/crash/_usr_lib_tracker_tracker-extract.1000.crash 640:1000:119:4471123:2019-01-21 15:43:11.507506447 -0500:2019-01-21 15:43:07.863473435 -0500:/var/crash/_usr_bin_nautilus.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 15:55:09 2019 InstallationDate: Installed on 2019-01-02 (19 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages -- 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/1812750 Title: Python stack trace when running `ubuntu-bug nautilus` in disco Status in apport package in Ubuntu: New Bug description: ERROR: hook /usr/share/apport/package-hooks/source_nautilus.py crashed: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 205, in _run_hook symb['add_info'](report, ui) TypeError: add_info() takes 1 positional argument but 2 were given During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/apport/report.py", line 210, in _run_hook symb['add_info'](report) File "/usr/share/apport/package-hooks/source_nautilus.py", line 23, in add_info report["usr_lib_nautilus"] = package_versions(*sorted(plugin_packages)) TypeError: '<' not supported between instances of 'NoneType' and 'str' ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apport 2.20.10-0ubuntu19 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CrashReports: 640:0:119:606530:2019-01-21 14:49:01.440511009 -0500:2019-01-21 14:49:01.136510154 -0500:/var/crash/_opt_penguindome_client_client-cron.py.0.crash 640:0:119:2444106:2019-01-21 14:54:50.761487081 -0500:2019-01-21 14:54:48.449619152 -0500:/var/crash/_usr_lib_packagekit_packagekitd.0.crash 640:1000:119:3237446:2019-01-21 14:54:03.516504591 -0500:2019-01-21 14:54:00.808239070 -0500:/var/crash/_usr_lib_tracker_tracker-extract.1000.crash 640:1000:119:4471123:2019-01-21 15:43:11.507506447 -0500:2019-01-21 15:43:07.863473435 -0500:/var/crash/_usr_bin_nautilus.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 15:55:09 2019 InstallationDate: Installed on 2019-01-02 (19 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to disco on 2019-01-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1812750/+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 1812744] [NEW] resolved uses only per-link dns servers
Public bug reported: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1812744 Title: resolved uses only per-link dns servers Status in systemd package in Ubuntu: New Bug description: I configured multiple DNS servers in the DNS= option. The manual page says: "DNS requests are sent to one of the listed DNS servers in parallel to suitable per-link DNS servers" What I see however, is that each DNS request is sent twice to the same server, e.g.: connect(15, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 connect(16, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("192.168.0.1")}, 16) = 0 If a per-link server is pushed by network-manager, it's always that one. Since my per-link server can lag a lot, that is annoying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812744/+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 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
@jurit you mention armbian which is not an Ubuntu Project supported flavour. You show kernel version strings for x86_64 arch, instead of ARM. You should contact armbian to get better/newer kernel which is compatible with what userspace expects. If possible, I can only support and recommend to get all of your packages from the Ubuntu Project. -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
This bug was fixed in the package apport - 2.20.10-0ubuntu19 --- apport (2.20.10-0ubuntu19) disco; urgency=medium * debian/apport-autoreport.service: Since this calls whoopsie-upload-all which fails if whoopsie isn't running, it should have a relationship with whoopsie.service. (LP: #1787729) -- Brian Murray Wed, 16 Jan 2019 10:23:09 -0800 ** Changed in: apport (Ubuntu) Status: In Progress => Fix Released -- 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/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: Fix Released Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Changed in: apt (Ubuntu Cosmic) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: apt (Ubuntu Bionic) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: apt (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: apt (Ubuntu Bionic) Status: New => In Progress ** Changed in: apt (Ubuntu Cosmic) Status: New => In Progress ** Changed in: apt (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: In Progress Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Bionic: In Progress Status in apt source package in Cosmic: In Progress Status in apt source package in Disco: In Progress Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. *
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Thank you, I have: root@tery:~# uname -m x86_64 root@tery:~# uname -r 4.15.0-43-generic root@tery:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic Are you sure, if I update bionic (LTS) kernel to armbian I can use all future bionic LTS updates? -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Changed in: apt (Ubuntu Disco) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: In Progress Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: In Progress Bug description: [Impact] APT documentation/example/manpages isn't referencing the current release which could be misleading for certain users. --- APT src code: --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Xenial and late in APT points to 'trusty or 'xenial' which generate the doc example & manpage with the wrong release instead of the actual ubuntu-codename. APT in Xenial point to 'trusty'. APT in Bionic and late to 'xenial' It also affect the man page: Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Xenial and late: * Look sources.list(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. While we understand it's not a "bug' and only a reference/example... I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812696/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1018677] Re: scanner doesn't work on bootup
I updated libusb-0.1.so.4 to libusb-dev in ubuntu 18.04 LTS and the error was gone. BTW: i am astonished how such an error can remain so long in the operating system :-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1018677 Title: scanner doesn't work on bootup Status in libusb package in Ubuntu: Confirmed Bug description: When the computer boots up (12.04) with the scanner attached lsusb lists the scanner Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 002: ID 03f0:1705 Hewlett-Packard ScanJet 5590 Bus 002 Device 003: ID 0424:2502 Standard Microsystems Corp. Bus 002 Device 004: ID 0424:2602 Standard Microsystems Corp. USB 2.0 Hub Bus 002 Device 005: ID 0424:2228 Standard Microsystems Corp. 9-in-2 Card Reader Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) On Bus 002 Device 002 crw-rw-r--+ 1 root root 189, 129 Jun 27 21:51 /dev/bus/usb/002/002 But when I run scanimage -L >scanimage -L No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). doesn't work as root either scanimage -L [sudo] password for manojav: No scanners were identified. If you were expecting something different, check that the scanner is plugged in, turned on and detected by the sane-find-scanner tool (if appropriate). Please read the documentation which came with this software (README, FAQ, manpages). the only way to get the scanner working again is to power it off (unplug) and plug it again. this time its recognized by scanimage -L or xsane running as non-root as well root. looks like something has got a hold of the device and not letting it go! its similar to when a scanning app crashes and leaves things is a bad state. only way to clear that is power off the scanner and plug it back-in this has been happening since 11.10, and now also w/ 12.04 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xsane 0.998-3ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jun 27 22:00:50 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: xsane UpgradeStatus: Upgraded to precise on 2012-06-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/1018677/+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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Description changed: [Impact] - From APT src code : + APT documentation/example/manpages isn't referencing the current release + which could be misleading for certain users. --- + APT src code: + --- [GOOD ubuntu-codename] + * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] + * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- - The ubuntu-codename variable for Bionic and late in APT points to Xenial - which generate the doc example with Xenial instead of the actual - codename. And Xenial point to 'trusty'. + The ubuntu-codename variable for Xenial and late in APT points to + 'trusty or 'xenial' which generate the doc example & manpage with the + wrong release instead of the actual ubuntu-codename. - * ./doc/sources.list.5.xml | grep -i verbatim - --- - %aptverbatiment; - --- + APT in Xenial point to 'trusty'. + APT in Bionic and late to 'xenial' - It also seems to affect the man page by mentionning 'xenial'. + It also affect the man page: + Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] - With Bionic and late (or Xenial) : + With Xenial and late: * Look sources.list(5) manpage + Ex: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look apt_preferences(5) manpage - http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html + Ex: http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html * Look /usr/share/doc/apt/examples/sources.list $ lsb_release -cs bionic $ cat /usr/share/doc/apt/examples/sources.list # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu xenial main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted deb http://security.ubuntu.com/ubuntu xenial-security main restricted deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted -- You'll notice they all point to the wrong release. - While we understand it's not a "bug' and only a reference/example... I - think it's for the best interest of all if the examples/manpages - reference the current release. + While we understand it's not a "bug' and only a reference/example... + I think it's for the best interest of all if the examples/manpage reference the current release. [Regression Potential] * None, it only affect documentation/examples and manpages. No behavior change in the APT code. [Other Info] [Original Description] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html -- You received this bug
[Touch-packages] [Bug 1808233] Re: Update gtk to 3.24.4
** Summary changed: - Update gtk to 3.24.3 + Update gtk to 3.24.4 ** Description changed: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS - https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.3 + https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. + + Make sure that GTK switches look OK. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few - regressions in the 3.24.2 release.) + regressions in the 3.24.2 and 3.24.3 releases.) This update changes the ON/OFF switches for GNOME's default Adwaita - theme to use ⏽/⭘. Previously, it was ❙/○ for most languages but ON/OFF - for English (because English has short words that could fit on a - switch). This doesn't affect default Ubuntu 18.10 which uses Yaru which - doesn't use labels on its switches. This is technically a UI change, but - it is useful for compatibility with Flatpak apps that are being built - with the new GTK. This change is small enough that it could be reverted - for Ubuntu 18.10 if necessary. + theme to use ❙/○ for all languages (or ⏽/⭘ if they are supported in a + font you have installed: currently, that's fonts-symbola which we no + longer install by default). Previously, it was ❙/○ for most languages + but ON/OFF for English (because English has short words that could fit + on a switch). This doesn't affect default Ubuntu 18.10 which uses Yaru + which doesn't use labels on its switches. This is technically a UI + change, but it is useful for compatibility with Flatpak apps that are + being built with the new GTK. This change is small enough that it could + be reverted for Ubuntu 18.10 if necessary. Other Info == The commit history shows themeing changes to the GNOME default themes (Adwaita and Adwaita Dark which are bundled inside gtk3). But those changes were reverted for this release to make it easier for distros like us to push the update to our stable release. - The next scheduled gtk3 release (3.24.4 ? in March?) will include those + The next scheduled gtk3 release (3.24.5 ? in March?) will include those changes. See https://blog.gtk.org/2019/01/14/theme-changes-in-gtk-3/ for more details. -- 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/1808233 Title: Update gtk to 3.24.4 Status in gtk+3.0 package in Ubuntu: Fix Committed Status in gtk+3.0 source package in Cosmic: In Progress Bug description: Impact == There is a new release in the stable 3.24 series. This also bundles the emoji fixes from LP: #1807719 and LP: #1807721 and the Xfce flickering fix from LP: #1798861. https://gitlab.gnome.org/GNOME/gtk/blob/gtk-3-24/NEWS https://gitlab.gnome.org/GNOME/gtk/compare/3.24.1...3.24.4 Test Case = Run several apps in the default Ubuntu install and make sure that there are no visible regressions. Make sure that GTK switches look OK. We will also be checking Xfce to validate the fix for LP: #1798861. Regression Potential There is a standing microrelease exception for GNOME point releases. I believe this is the second time in recent history that we've pushed a gtk point release as an SRU. The other example was 3.22.25 for Ubuntu 17.10 (LP: #1728421). We never ended up doing one for Ubuntu 18.04 LTS since it already included 3.22.30, the final 3.22 release. It hasn't been practical to update 18.04's gtk to the 3.24 series (bumped dependencies are one problem). https://wiki.ubuntu.com/StableReleaseUpdates#GNOME By the way, pre-release gtk3 is actually getting a bit more testing than a year ago since more developers and users are using development Flatpak releases of popular GNOME apps. (On the other hand, there were a few regressions in the 3.24.2 and
[Touch-packages] [Bug 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Description changed: + [Impact] + From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- - It also seems to affect the man page by mentionning 'xenial'. + It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html + + + [Test Case] + + With Bionic and late : + + * Look sources.list(5) manpage + http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html + + * Look apt_preferences(5) manpage + http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html + + * Look /usr/share/doc/apt/examples/sources.list + + $ lsb_release -cs + bionic + + $ cat /usr/share/doc/apt/examples/sources.list + + # See sources.list(5) manpage for more information + # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. + deb http://us.archive.ubuntu.com/ubuntu xenial main restricted + deb-src http://us.archive.ubuntu.com/ubuntu xenial main restricted + + deb http://security.ubuntu.com/ubuntu xenial-security main restricted + deb-src http://security.ubuntu.com/ubuntu xenial-security main restricted + + deb http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted + deb-src http://us.archive.ubuntu.com/ubuntu xenial-updates main restricted + -- + + You'll notice they all point to the wrong release. + + While we understand it's not a "bug' and only a reference/example... I + think it's for the best interest of all if the examples/manpages + reference the current release. + + [Regression Potential] + + * None, it only affect documentation/examples and manpages. No behavior + change in the code APT code. + + [Other Info] + + [Original Description] + From APT src code : + + --- + [GOOD ubuntu-codename] + * trusty: + apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: + + [WRONG ubuntu-codename] + * xenial: + apt-1.2.29/doc/apt-verbatim.ent: + + * bionic: + apt-1.6.7/doc/apt-verbatim.ent: + + * disco: + apt-1.8.0~alpha3/doc/apt-verbatim.ent: + --- + + * vendor/ubuntu/sources.list.in + --- + # See sources.list(5) manpage for more information + # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. + deb http://us.archive.ubuntu.com/ubuntu main restricted + deb-src http://us.archive.ubuntu.com/ubuntu main restricted + + deb http://security.ubuntu.com/ubuntu -security main restricted + deb-src http://security.ubuntu.com/ubuntu -security main restricted + + deb http://us.archive.ubuntu.com/ubuntu -updates main restricted + deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted + --- + + The ubuntu-codename variable for Bionic and late in APT points to Xenial + which generate the doc example with Xenial instead of the actual + codename. + + * ./doc/sources.list.5.xml | grep -i verbatim + --- + %aptverbatiment; + --- + + It also seems to affect the man page by mentionning 'xenial'. + Example took from Bionic: + http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html + http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html ** Description changed: [Impact] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src
[Touch-packages] [Bug 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Description changed: From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- - It also seems to affect the man page by mentionning 'xenial' for Bionic: + It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html ** Description changed: From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- - It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: + It also seems to affect the man page by mentionning 'xenial'. + Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: New Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: [Impact] From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html [Test Case] With Bionic and late : * Look sources.list(5) manpage http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html * Look
[Touch-packages] [Bug 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
juliank will include the ubuntu-codename variable change in his next SRU later this week. Thanks Juliank ! ** Tags added: sts ** Changed in: apt (Ubuntu Trusty) Status: New => Invalid ** Description changed: From APT src code : - --- - * trusty: - apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: + --- + [GOOD ubuntu-codename] + * trusty: + apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: - * xenial: - apt-1.2.29/doc/apt-verbatim.ent: + [WRONG ubuntu-codename] + * xenial: + apt-1.2.29/doc/apt-verbatim.ent: - * bionic: - apt-1.6.7/doc/apt-verbatim.ent: + * bionic: + apt-1.6.7/doc/apt-verbatim.ent: - * disco: - apt-1.8.0~alpha3/doc/apt-verbatim.ent: - --- + * disco: + apt-1.8.0~alpha3/doc/apt-verbatim.ent: + --- - * vendor/ubuntu/sources.list.in - --- - # See sources.list(5) manpage for more information - # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. - deb http://us.archive.ubuntu.com/ubuntu main restricted - deb-src http://us.archive.ubuntu.com/ubuntu main restricted + * vendor/ubuntu/sources.list.in + --- + # See sources.list(5) manpage for more information + # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. + deb http://us.archive.ubuntu.com/ubuntu main restricted + deb-src http://us.archive.ubuntu.com/ubuntu main restricted - deb http://security.ubuntu.com/ubuntu -security main restricted - deb-src http://security.ubuntu.com/ubuntu -security main restricted + deb http://security.ubuntu.com/ubuntu -security main restricted + deb-src http://security.ubuntu.com/ubuntu -security main restricted - deb http://us.archive.ubuntu.com/ubuntu -updates main restricted - deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted - --- + deb http://us.archive.ubuntu.com/ubuntu -updates main restricted + deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted + --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. - * ./doc/sources.list.5.xml | grep -i verbatim - --- - %aptverbatiment; - --- + * ./doc/sources.list.5.xml | grep -i verbatim + --- + %aptverbatiment; + --- It also seems to affect the man page by mentionning 'xenial' for Bionic: - http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html + http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: New Status in apt source package in Trusty: Invalid Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: From APT src code : --- [GOOD ubuntu-codename] * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: [WRONG ubuntu-codename] * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial'. Example took from Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812696/+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 1809827] Re: --add-file broken in bionic
Thanks for the bug report and pointing out the commit that fixes it, that seems fixed in the current version so closing the corresponding bug line and uploading a SRU for bionic ** Description changed: same error like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0 - Description of problem: + * Impact tar supplied in bionic has --add-file option broken. - Version-Release number of selected component: - tar-1.29b-2_amd64 - - Reproducible: Always - + * Test case Steps to Reproduce: 1. echo >a.txt 2. echo >b.txt 3. tar cf a.tar a.txt 4. tar rf a.tar --add-file=b.txt Actual results: tar: unhandled positional option 0 + * Regression potential + The changes are around an option which isn't working so no much regression potential there, check that other options still work though + + Is likely fixed by this: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54 ** Changed in: tar (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1809827 Title: --add-file broken in bionic Status in tar package in Ubuntu: Fix Released Status in tar package in Fedora: Unknown Bug description: same error like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0 * Impact tar supplied in bionic has --add-file option broken. * Test case Steps to Reproduce: 1. echo >a.txt 2. echo >b.txt 3. tar cf a.tar a.txt 4. tar rf a.tar --add-file=b.txt Actual results: tar: unhandled positional option 0 * Regression potential The changes are around an option which isn't working so no much regression potential there, check that other options still work though Is likely fixed by this: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1809827/+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 1809827] Re: --add-file broken in bionic
** Changed in: tar (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1809827 Title: --add-file broken in bionic Status in tar package in Ubuntu: Confirmed Status in tar package in Fedora: Unknown Bug description: same error like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0 Description of problem: tar supplied in bionic has --add-file option broken. Version-Release number of selected component: tar-1.29b-2_amd64 Reproducible: Always Steps to Reproduce: 1. echo >a.txt 2. echo >b.txt 3. tar cf a.tar a.txt 4. tar rf a.tar --add-file=b.txt Actual results: tar: unhandled positional option 0 Is likely fixed by this: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1809827/+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 1812696] Re: APT doc and manpage uses wrong ubuntu-codename
** Changed in: apt (Ubuntu Trusty) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Bionic) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Cosmic) Importance: Undecided => Wishlist ** Changed in: apt (Ubuntu Disco) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: New Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: From APT src code : --- * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial' for Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812696/+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 1812696] [NEW] APT doc and manpage uses wrong ubuntu-codename
Public bug reported: >From APT src code : --- * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial' for Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1812696 Title: APT doc and manpage uses wrong ubuntu-codename Status in apt package in Ubuntu: New Status in apt source package in Trusty: New Status in apt source package in Xenial: New Status in apt source package in Bionic: New Status in apt source package in Cosmic: New Status in apt source package in Disco: New Bug description: From APT src code : --- * trusty: apt-1.0.1ubuntu2.18/doc/apt-verbatim.ent: * xenial: apt-1.2.29/doc/apt-verbatim.ent: * bionic: apt-1.6.7/doc/apt-verbatim.ent: * disco: apt-1.8.0~alpha3/doc/apt-verbatim.ent: --- * vendor/ubuntu/sources.list.in --- # See sources.list(5) manpage for more information # Remember that CD-ROMs, DVDs and such are managed through the apt-cdrom tool. deb http://us.archive.ubuntu.com/ubuntu main restricted deb-src http://us.archive.ubuntu.com/ubuntu main restricted deb http://security.ubuntu.com/ubuntu -security main restricted deb-src http://security.ubuntu.com/ubuntu -security main restricted deb http://us.archive.ubuntu.com/ubuntu -updates main restricted deb-src http://us.archive.ubuntu.com/ubuntu -updates main restricted --- The ubuntu-codename variable for Bionic and late in APT points to Xenial which generate the doc example with Xenial instead of the actual codename. * ./doc/sources.list.5.xml | grep -i verbatim --- %aptverbatiment; --- It also seems to affect the man page by mentionning 'xenial' for Bionic: http://manpages.ubuntu.com/manpages/bionic/man5/sources.list.5.html http://manpages.ubuntu.com/manpages/bionic/man5/apt_preferences.5.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812696/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
** Attachment added: "hwinfo.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+attachment/5231145/+files/hwinfo.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: New Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+attachment/5231143/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: New Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
** Attachment added: "pacmd.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+attachment/5231146/+files/pacmd.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: New Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] Re: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: New Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1812693] [NEW] [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers
Public bug reported: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alc1220 amd64 bionic realtek ** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/bugs/1812693/+attachment/5231140/+files/alsa-info.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1812693 Title: [MSI GL63 8RE, Realtek ALC1220] No sound from internal speakers Status in alsa-driver package in Ubuntu: New Bug description: Internal speaker - No sound Headset - OK Bluetooth earbuds - OK Everything is OK on Windows 10. lsb_release -rd Description:KDE neon User Edition 5.14 Release:18.04 ALSA version alsa-base 1.0.25+dfsg-0ubuntu5 /proc/version_signature Ubuntu 4.15.0-43.46-generic 4.15.18 uname -r 4.15.0-43-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1812693/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I encounter the exact same problems of Thales Loiola Raveli on an ASUS 14 UX433FN with Linux Mint 19.1 Cinnamon. When will the patch be added to a Linux Mint-supported kernel version? Please please please, it's hard to have a brand-new but mute PC :/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1812683] [NEW] rhythmbox crashes when trying to play music
Public bug reported: Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault. 0x77183384 in gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x77183384 in gtk_tree_view_get_column () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x76ecd5fa in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x76ece792 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x76ecf445 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7718d1fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x710bedae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #6 0x710be71f in ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #7 0x76be3ced in g_cclosure_marshal_generic_va () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #8 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #9 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #10 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #11 0x7700f7fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #12 0x76be6008 in g_cclosure_marshal_VOID__BOXEDv () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #13 0x76be3346 in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #14 0x76bfe9ff in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #15 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #16 0x7700c78e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #17 0x7700dcdb in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #18 0x7701099e in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #19 0x76fde1e1 in gtk_event_controller_handle_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #20 0x7719d85b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #21 0x77b46642 in () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #22 0x7705815b in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #23 0x76be310d in g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #24 0x76bf605e in () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #25 0x76bfe0af in g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #26 0x76bff12f in g_signal_emit () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #27 0x7719fb04 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #28 0x770551ce in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #29 0x770572a8 in gtk_main_do_event () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #30 0x75323765 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #31 0x75353f82 in () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 #32 0x76909387 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #33 0x769095c0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #34 0x7690964c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x737e7e3d in g_application_run () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #36 0x77aa0b09 in rb_application_run () at /usr/lib/x86_64-linux-gnu/librhythmbox-core.so.10 #37 0x4d57 in main () ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 16:14:12 2019 SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1812683 Title: rhythmbox crashes when trying to play music Status in gstreamer1.0 package in Ubuntu: New Bug description: Thread 1 "rhythmbox" received signal SIGSEGV, Segmentation fault. 0x77183384 in gtk_tree_view_get_column () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (gdb) bt #0 0x77183384 in gtk_tree_view_get_column () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #1 0x76ecd5fa in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #2 0x76ece792 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #3 0x76ecf445 in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #4 0x7718d1fc in () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 #5 0x710bedae in ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 #6 0x710be71f in ffi_call () at
[Touch-packages] [Bug 1812536] Re: logrotate 3.14.0-4ubuntu2 error: /etc/logrotate.conf:7 unknown group 'admn'
Thanks, that was fixed in this update https://bugs.launchpad.net/ubuntu/+source/logrotate/3.14.0-4ubuntu3 ** Changed in: logrotate (Ubuntu) Importance: Undecided => High ** Changed in: logrotate (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1812536 Title: logrotate 3.14.0-4ubuntu2 error: /etc/logrotate.conf:7 unknown group 'admn' Status in logrotate package in Ubuntu: Fix Released Bug description: try to run version on proposed sudo logrotate -f /etc/logrotate.conf [sudo] password for agent: error: /etc/logrotate.conf:7 unknown group 'admn' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1812536/+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 1760106] Re: FFe: Enable configuring resume offset via sysfs
removing, breaks amd64 autopkg tests. Removing packages from disco-proposed: klibc 2.0.4-9ubuntu3 in disco klibc-utils 2.0.4-9ubuntu3 in disco amd64 klibc-utils 2.0.4-9ubuntu3 in disco arm64 klibc-utils 2.0.4-9ubuntu3 in disco armhf klibc-utils 2.0.4-9ubuntu3 in disco ppc64el klibc-utils 2.0.4-9ubuntu3 in disco s390x libklibc 2.0.4-9ubuntu3 in disco amd64 libklibc 2.0.4-9ubuntu3 in disco arm64 libklibc 2.0.4-9ubuntu3 in disco armhf libklibc 2.0.4-9ubuntu3 in disco ppc64el libklibc 2.0.4-9ubuntu3 in disco s390x libklibc-dev 2.0.4-9ubuntu3 in disco amd64 libklibc-dev 2.0.4-9ubuntu3 in disco arm64 libklibc-dev 2.0.4-9ubuntu3 in disco armhf libklibc-dev 2.0.4-9ubuntu3 in disco ppc64el libklibc-dev 2.0.4-9ubuntu3 in disco s390x Comment: see LP: #1760106: remove klibc from proposed, breaking autopkg tests 1 package successfully removed. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... [2.742629] 220 (nuke): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault done. [2.746818] 222 (run-init): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault Target filesystem doesn't have requested /sbin/init. [2.750846] 223 (run-init): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault [2.753957] 224 (run-init): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault [2.757109] 225 (run-init): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault [2.760128] 226 (run-init): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault [2.763174] 227 (run-init): Uhuuh, elf segment at 0020 requested but the memory is mapped already Segmentation fault chvt: can't open console No init found. Try passing init= bootarg. Couldn't get a file descriptor referring to the console BusyBox v1.27.2 (Ubuntu 1:1.27.2-2ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) [6n --- : failure: Timed out on waiting for ssh connection autopkgtest [09:21:38]: ERROR: testbed failure: cannot send to testbed: [Errno 32] Broken pipe -- 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/1760106 Title: FFe: Enable configuring resume offset via sysfs Status in OEM Priority Project: Fix Released Status in klibc package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in klibc source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in klibc source package in Cosmic: New Status in linux source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Cannot hibernate & resume from a swapfile [Test Case] * Create or enlarge swapfile to be big enough for hibernation * Attempt to hibernate and resume [Regression Potential] * Hibernation is not reliable technology in itself, and multiple things may cause failure to resume. Thus it is sufficient to validate this bug after swapfile is attempted for hibernation and the disk offset kernel parameter is modified. Irrespective if actual suspending or resume were successful or not. [Other Info] * Original bug report In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work "out of the box". The patch in the kernel is here: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git/commit/?h=linux-next=355064675f1c997cea017ea64c8f2c216e5425d9 Systemd support for adopting this change is available here: https://github.com/systemd/systemd/pull/8406 As of 3/30/18 it's not yet been merged however. Klibc support for adopting this change is available here: https://www.zytor.com/pipermail/klibc/2018-March/003986.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760106/+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 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
I quite agree with @GeekSmith here. We disabled systemd-resolved on bionic and install ifupdown instead since we install this on server that have a static configuration and we don't want systemd-resolved to modify anything in the resolv.conf file. Only during the initial installation time of the server we use dhclient to get an IP address. The result is that the resolv.conf file is not modified by dhclient despite systemd-resolved being disabled. To work around this issue, we simply deleted the /etc/dhcp/dhclient-enter- hooks.d/resolved file as we don't need it anyway. A cleaner way of course it to actually test in the file if systemd- resolved is used, as @GeekSmith's patch does. -- 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/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration Status in resolvconf package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ...and reboot. You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/interfaces or /etc/network/interfaces.d/* will not provide DNS configuration in /etc/resolv.conf and /run/resolvconf/interfaces/. This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines "make_resolv_conf()" as a valid function for the BOUND case, but /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now, eh?) even though resolved is masked. The file existence check in the beginning of /etc/dhcp/dhclient-enter- hooks.d/resolved should be more thorough, i.e. it should ensure that resolved is enabled, rather than simply look for the existence of /lib/systemd/systemd-resolved. This works for me: -if [ -x /lib/systemd/systemd-resolved ] ; then +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled systemd-resolved ; then Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a similar check, looking for /run/resolvconf/enable-updates as a condition for meddling with DNS settings. If desired, I'll file a separate bug for that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 1644996] Re: logrotate config uses syslog group
This bug was fixed in the package logrotate - 3.14.0-4ubuntu3 --- logrotate (3.14.0-4ubuntu3) disco; urgency=medium * Fix typo in 'adm' group name. logrotate (3.14.0-4ubuntu2) disco; urgency=medium * Use group 'adm' instead of 'syslog' when rotating logs. LP: #1644996. -- Dimitri John Ledkov Mon, 21 Jan 2019 10:11:39 + ** Changed in: logrotate (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
Just clarifying that we don't use the resolvconf package either, but just a plain static /etc/resolv.conf file. -- 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/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration Status in resolvconf package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ...and reboot. You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/interfaces or /etc/network/interfaces.d/* will not provide DNS configuration in /etc/resolv.conf and /run/resolvconf/interfaces/. This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines "make_resolv_conf()" as a valid function for the BOUND case, but /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now, eh?) even though resolved is masked. The file existence check in the beginning of /etc/dhcp/dhclient-enter- hooks.d/resolved should be more thorough, i.e. it should ensure that resolved is enabled, rather than simply look for the existence of /lib/systemd/systemd-resolved. This works for me: -if [ -x /lib/systemd/systemd-resolved ] ; then +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled systemd-resolved ; then Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a similar check, looking for /run/resolvconf/enable-updates as a condition for meddling with DNS settings. If desired, I'll file a separate bug for that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 1759836] Re: systemd-udevd consumes 100% of CPU
I too can confirm that the solution Florian posted (modifying /lib/udev/rules.d/97-hid2hci.rules) works. Dell Latitude E6400, Ubuntu-Mate 18.04LTS with generic kernel (Linux 4.15.0-43-generic), udev/systemd version 237-3ubuntu10.11, bluez version 5.48-0ubuntu3.1 -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd 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. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+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 1812637] [NEW] systemd-resolved stops resolving
Public bug reported: Regularly (= after about 15 mins of use) the systemd-resolved service stops resolving DNS names (any). Configuration: Two domains defined - one internal, one for external services DNS server does not provide DNSSEC services Both domains are in the search path (served by DHCP) Effect: Clients refuse to resolve internal domain servers (short or FQDN) after about 15 mins. Workaround: from the client CLI sudo systemctl restart systemd-resolved.service Background: A Github error (https://github.com/systemd/systemd/issues/6490) describes the cause to be (missing) DNSSEC. I found discussions about "the correct way" DNS works (with only one domain). Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked fine). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.6 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 11:57:32 2019 InstallationDate: Installed on 2018-04-30 (266 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- 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/1812637 Title: systemd-resolved stops resolving Status in systemd package in Ubuntu: New Bug description: Regularly (= after about 15 mins of use) the systemd-resolved service stops resolving DNS names (any). Configuration: Two domains defined - one internal, one for external services DNS server does not provide DNSSEC services Both domains are in the search path (served by DHCP) Effect: Clients refuse to resolve internal domain servers (short or FQDN) after about 15 mins. Workaround: from the client CLI sudo systemctl restart systemd-resolved.service Background: A Github error (https://github.com/systemd/systemd/issues/6490) describes the cause to be (missing) DNSSEC. I found discussions about "the correct way" DNS works (with only one domain). Happens exclusively on Ubuntu clients (Windows, Mac and Fedora worked fine). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10.6 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 21 11:57:32 2019 InstallationDate: Installed on 2018-04-30 (266 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (92 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1
[Touch-packages] [Bug 1765331] Re: ar in ubuntu_ltp test failed with 4.15 KVM
Passed with Bionic kernel 4.15.0-44.47: ar01 14 TPASS: ar updated modified file0 (-u) ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** No longer affects: binutils ** No longer affects: binutils (Ubuntu) ** No longer affects: linux-kvm (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1765331 Title: ar in ubuntu_ltp test failed with 4.15 KVM Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: ar tests in ubuntu_ltp has failed with 4.15.0-1004.4 kvm kernel <<>> tag=ar stime=1523972462 cmdline="export TCdat=$LTPROOT/testcases/bin; ar01" contacts="" analysis=exit <<>> ar01 1 TPASS: ar added new file after another (-a) ar01 2 TPASS: ar moved file correctly (-ma) ar01 3 TPASS: ar added new file before another (-b) ar01 4 TPASS: ar moved file correctly (-mb) ar01 5 TPASS: ar haven't produced output (-c) ar01 6 TPASS: ar haven't produced output (-qc) ar01 7 TPASS: ar deleted files correctly (-d) ar01 8 TPASS: ar deleted nothing (-d with empty list) ar01 9 TPASS: ar added new file before another (-i) ar01 10 TPASS: ar moved file correctly (-mi) ar01 11 TPASS: ar moved file correctly (-m) ar01 12 TPASS: ar printed file content correctly (-p) ar01 13 TPASS: ar appended file correctly (-q) ar: `u' modifier ignored since `D' is the default (see `U') ar01 14 TFAIL: ar haven't updated modified file0 (-u) ar01 14 TPASS: ar haven't updated unmodified file1 (-u) ar01 15 TPASS: ar verbose listing works (-tv) ar01 16 TPASS: ar printed extracted filenames (-xv) ar01 16 TPASS: ar extracted files correctly ar01 17 TPASS: ar printed extracted filename (-xv) ar01 17 TPASS: ar extracted file correctly Summary: passed 19 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 08:24:19 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1765331/+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 1656806] Re: fail to invoke online account creationg from messaging-app
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1656806 Title: fail to invoke online account creationg from messaging-app Status in Online Accounts setup for Ubuntu Touch: In Progress Status in webapps-sprint: In Progress Status in messaging-app package in Ubuntu: Confirmed Bug description: Using online account API from messaging-app to create a new account fail with the message "invalid application file" . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1656806/+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