[Touch-packages] [Bug 2056696] Re: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors
I can confirm that refresh snapd to edge channel resolved for me too rev 21649 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056696 Title: All Snaps are denied the ability to use DBus for notifications and apptray indicators in KDE-based flavors Status in snapd: In Progress Status in apparmor package in Ubuntu: Confirmed Bug description: OS: Kubuntu Noble 24.04 Alpha (two-day old install) snapd version: 2.61.2 Affected Snaps: firefox, thunderbird, element-desktop Steps to reproduce: # For Firefox: 1. Open the Firefox Snap. 2. Open https://www.bennish.net/web-notifications.html. 3. Click "Authorize" and allow the website to send notifications. 4. Click "Show". Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up in the upper-right corner of the display, improperly themed and obviously generated by Firefox as a fallback. # For Thunderbird: 1. Open the Thunderbird Snap. 2. Ensure you are connected to an email account. 3. Unfocus the Thunderbird window. 4. Wait for an email to come through. Expected result: When the email comes through, a notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: The notification shows up improperly themed and obviously generated by Thunderbird as a fallback. # For Element: 1. Open the Element Snap. Expected result: An apptray indicator should appear in the system tray with the Element logo. Actual result: No such indicator appears. 2. Log in, ask someone to ping you, then unfocus the window and wait for the ping to come through. Expected result: A notification should be displayed by Plasma, similar to other notifications the system displays. Actual result: No notification appears at all. Additional information: Based on the output of snappy-debug, this appears to be AppArmor related, at least for element-desktop (but presumably for the others too). Of note are some of the following log entries: ``` = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/DBus" interface="org.freedesktop.DBus" member="ListActivatableNames" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="isEnabled" mask="send" name="org.kde.kwalletd5" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=1762 peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/modules/kwalletd5" interface="org.kde.KWallet" member="close" mask="send" name="org.kde.kwalletd5" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=1762 peer_label="unconfined" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/StatusNotifierItem" interface="org.freedesktop.DBus.Properties" member="GetAll" name=":1.45" mask="receive" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=2394 peer_label="plasmashell" DBus access = AppArmor = Time: 2024-03-10T13:4 Log: apparmor="DENIED" operation="dbus_signal" bus="session" path="/StatusNotifierItem" interface="org.kde.StatusNotifierItem" member="NewToolTip" mask="send" name="org.freedesktop.DBus" pid=2950 label="snap.element-desktop.element-desktop" peer_pid=2394 peer_label="plasmashell" DBus access ``` Booting with `apparmor=0` set on the kernel command line fixes the issue with Element (apptray indicator appears, notifications show up). Obviously this is not a solution, but it does isolate AppArmor as being at least partially at fault. This issue seems to be somewhat similar to https://forum.snapcraft.io/t/dbus-related-apparmor-denials/37422, however it seems as if Element is trying to hit the right paths and interfaces and is still being denied (based on looking at the info in https://github.com/snapcore/snapd/blob/master/interfaces/builtin/desktop_legacy.go and comparing the paths and interfaces there with the paths and interfaces shown by snappy-debug. I talked about this issue with Erich Eickmeyer and he mentioned that it occurred after a Plasma update. This doesn't make a great deal of sense to me, and I suspect possibly some other component of the affected systems happened to get updated at the same time (perhaps the snapd Snap), but it's definitely worth mentioning. An example of one of Thunderbird's fallback notifications is attached
[Touch-packages] [Bug 2058093] [NEW] NetworkManager crashed with SIGABRT in g_assertion_message_expr()
Public bug reported: unexpected crashed ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 15 16:40:02 2024 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2023-07-08 (252 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) IpRoute: default via 192.168.0.1 dev wlp0s20f3 proto dhcp src 192.168.0.227 metric 600 10.99.203.0/24 dev mpqemubr0 proto kernel scope link src 10.99.203.1 linkdown 10.236.76.0/24 dev lxdbr0 proto kernel scope link src 10.236.76.1 linkdown 192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.227 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SignalName: SIGABRT SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled separator: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace noble ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2058093 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: New Bug description: unexpected crashed ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Mar 15 16:40:02 2024 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2023-07-08 (252 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) IpRoute: default via 192.168.0.1 dev wlp0s20f3 proto dhcp src 192.168.0.227 metric 600 10.99.203.0/24 dev mpqemubr0 proto kernel scope link src 10.99.203.1 linkdown 10.236.76.0/24 dev lxdbr0 proto kernel scope link src 10.236.76.1 linkdown 192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.227 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SignalName: SIGABRT SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.45.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2058093/+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 2056430] [NEW] apport-gtk crashed with SIGTRAP in g_log_writer_default()
Public bug reported: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: apport-gtk 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 00:00:57 2024 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-07-08 (243 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) InterpreterPath: /usr/bin/python3.12 JournalErrors: -- No entries -- PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A Signal: 5 SignalName: SIGTRAP SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with SIGTRAP in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin nordvpn plugdev sudo users separator: ** Affects: apport (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash noble third-party-packages wayland-session ** Information type changed from Private to Public -- 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/2056430 Title: apport-gtk crashed with SIGTRAP in g_log_writer_default() Status in apport package in Ubuntu: Invalid Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: apport-gtk 2.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 7 00:00:57 2024 ExecutablePath: /usr/share/apport/apport-gtk InstallationDate: Installed on 2023-07-08 (243 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) InterpreterPath: /usr/bin/python3.12 JournalErrors: -- No entries -- PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk Python3Details: /usr/bin/python3.12, Python 3.12.2, python3-minimal, 3.12.1-0ubuntu2 PythonDetails: N/A Signal: 5 SignalName: SIGTRAP SourcePackage: apport StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: apport-gtk crashed with SIGTRAP in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin nordvpn plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2056430/+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 2012295] [NEW] ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke()
Public bug reported: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/2012295 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ibus 1.5.28-2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:39 2023 Disassembly: => 0x7f4f395714b0: Cannot access memory at address 0x7f4f395714b0 ExecutablePath: /usr/libexec/ibus-extension-gtk3 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: -- No entries -- ProcCmdline: /usr/libexec/ibus-extension-gtk3 SegvAnalysis: Segfault happened at: 0x7f4f395714b0:Cannot access memory at address 0x7f4f395714b0 PC (0x7f4f395714b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-extension-gtk3 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/2012295/+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 2012293] [NEW] package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1
Public bug reported: unexpected crashed when login to x11 session ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 7 23:00:26 2023 DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2012293 Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 Status in mesa package in Ubuntu: New Bug description: unexpected crashed when login to x11 session ProblemType: Package DistroRelease: Ubuntu 23.04 Package: libgl1-mesa-dri 22.3.6-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Mar 7 23:00:26 2023 DistroCodename: lunar DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.21ubuntu1 apt 2.6.0 SourcePackage: mesa Title: package libgl1-mesa-dri 22.3.6-1ubuntu2 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/dri/i915_dri.so', which is also in package libgl1-amber-dri:amd64 21.3.7-0ubuntu1 UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2012293/+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 2012294] [NEW] evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke()
Public bug reported: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: ** Affects: evolution-data-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash lunar need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/2012294 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() Status in evolution-data-server package in Ubuntu: New Bug description: crashed when login to x11 session ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: evolution-data-server 3.47.3-1 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 00:27:25 2023 Disassembly: => 0x7f7332a444b0: Cannot access memory at address 0x7f7332a444b0 ExecutablePath: /usr/libexec/evolution-data-server/evolution-alarm-notify InstallationDate: Installed on 2020-06-25 (997 days ago) InstallationMedia: JournalErrors: Mar 21 00:27:22 hostname gnome-control-c[178036]: No gedit is installed here. Colors won't be updated. Please fix your installation. Mar 21 00:27:25 hostname kernel: show_signal_msg: 1 callbacks suppressed ProcCmdline: /usr/libexec/evolution-data-server/evolution-alarm-notify SegvAnalysis: Segfault happened at: 0x7f7332a444b0:Cannot access memory at address 0x7f7332a444b0 PC (0x7f7332a444b0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: evolution-alarm-notify crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to lunar on 2022-09-30 (170 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/2012294/+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 1991008] [NEW] goa-daemon crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1990123 *** https://bugs.launchpad.net/bugs/1990123 Public bug reported: crashed after login to desktop ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7 Uname: Linux 5.19.0-17-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Wed Sep 28 01:34:46 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2020-06-25 (823 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1664300076', '--until=@1664300096'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (155 days ago) UserGroups: nordvpn sudo separator: ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1991008 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() Status in gnome-online-accounts package in Ubuntu: New Bug description: crashed after login to desktop ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: gnome-online-accounts 3.46.0-1 ProcVersionSignature: Ubuntu 5.19.0-17.17-generic 5.19.7 Uname: Linux 5.19.0-17-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Wed Sep 28 01:34:46 2022 ExecutablePath: /usr/libexec/goa-daemon InstallationDate: Installed on 2020-06-25 (823 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1664300076', '--until=@1664300096'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/goa-daemon Signal: 6 SourcePackage: gnome-online-accounts StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/librest-1.0.so.0 rest_proxy_call_sync () from /lib/x86_64-linux-gnu/librest-1.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 Title: goa-daemon crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (155 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1991008/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
clear all or related to network manager only? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1990002] [NEW] NetworkManager crashed with SIGABRT in g_assertion_message_expr()
*** This bug is a duplicate of bug 1988644 *** https://bugs.launchpad.net/bugs/1988644 Public bug reported: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Sep 13 22:54:12 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 600 169.254.0.0/16 dev nordlynx scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic ** Information type changed from Private to Public ** This bug has been marked a duplicate of bug 1988644 NetworkManager crashed with SIGABRT in g_assertion_message_expr() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1990002 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: New Bug description: sudden crashed ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-16.16-generic 5.19.7 Uname: Linux 5.19.0-16-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Tue Sep 13 22:54:12 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (812 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 600 169.254.0.0/16 dev nordlynx scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (144 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990002/+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 1989003] [NEW] package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: i need to re-run the upgrade then it success updating the package ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-16-generic 5.19.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fenris72787 F wireplumber /dev/snd/seq:fenris72784 F pipewire CasperMD5CheckResult: unknown Date: Wed Sep 7 22:15:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-06-25 (803 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to kinetic on 2022-04-25 (134 days ago) dmi.bios.date: 07/12/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd07/12/2022:br1.18:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1989003 Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: i need to re-run the upgrade then it success updating the package ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-16-generic 5.19.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fenris72787 F wireplumber /dev/snd/seq:fenris72784 F pipewire CasperMD5CheckResult: unknown Date: Wed Sep 7 22:15:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-06-25 (803 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to kinetic on 2022-04-25 (134 days ago) dmi.bios.date: 07/12/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd07/12/2022:br1.18:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989003/+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 1989002] [NEW] package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: i need to re-run the upgrade then it success updating the package ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-16-generic 5.19.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fenris72787 F wireplumber /dev/snd/seq:fenris72784 F pipewire CasperMD5CheckResult: unknown Date: Wed Sep 7 22:15:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-06-25 (803 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to kinetic on 2022-04-25 (134 days ago) dmi.bios.date: 07/12/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd07/12/2022:br1.18:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1989002 Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: i need to re-run the upgrade then it success updating the package ProblemType: Package DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-16-generic 5.19.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fenris72787 F wireplumber /dev/snd/seq:fenris72784 F pipewire CasperMD5CheckResult: unknown Date: Wed Sep 7 22:15:16 2022 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2020-06-25 (803 days ago) InstallationMedia: MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=5fd773bd-0c82-4656-8916-834a924ee33e ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-5.19.0-16-generic 5.19.0-16.16 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to kinetic on 2022-04-25 (134 days ago) dmi.bios.date: 07/12/2022 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.0 dmi.board.name: 0V2CCD dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.0:bd07/12/2022:br1.18:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0V2CCD:rvrA04:cvnDellInc.:ct31:cvr:sku08B0: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1989002/+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 1988644] Re: NetworkManager crashed with SIGABRT in g_assertion_message_expr()
as for now, it happened every time when i toggle 'dark mode' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: Incomplete Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1988643] [NEW] ibus-x11 crashed with SIGSEGV in g_closure_invoke()
Public bug reported: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 02:00:33 2022 Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/ibus-x11 RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: nordvpn sudo separator: ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic wayland-session ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1988643 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() Status in ibus package in Ubuntu: New Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: ibus 1.5.27-2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Sep 4 02:00:33 2022 Disassembly: => 0x7f4e338e34f0: Cannot access memory at address 0x7f4e338e34f0 ExecutablePath: /usr/libexec/ibus-x11 InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: JournalErrors: Error: command ['journalctl', '--priority=warning', '--since=@1662228023', '--until=@1662228043'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/libexec/ibus-x11 RebootRequiredPkgs: Error: path contained symlinks. SegvAnalysis: Segfault happened at: 0x7f4e338e34f0:Cannot access memory at address 0x7f4e338e34f0 PC (0x7f4e338e34f0) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: nordvpn sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1988643/+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 1988644] [NEW] NetworkManager crashed with SIGABRT in g_assertion_message_expr()
Public bug reported: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash kinetic need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1988644 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() Status in network-manager package in Ubuntu: New Bug description: occurred when toggle darkmode ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: network-manager 1.39.90-1ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashCounter: 1 Date: Fri Sep 2 15:34:33 2022 ExecutablePath: /usr/sbin/NetworkManager InstallationDate: Installed on 2020-06-25 (799 days ago) InstallationMedia: IpRoute: default via 192.168.50.1 dev wlp0s20f3 proto dhcp src 192.168.50.165 metric 20600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.50.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.50.165 metric 600 JournalErrors: -- No entries -- NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon RebootRequiredPkgs: Error: path contained symlinks. Signal: 6 SourcePackage: network-manager StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message_expr() UpgradeStatus: Upgraded to kinetic on 2022-04-25 (131 days ago) UserGroups: N/A nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.39.90 connected started full enabled enabled enabled missing enabled separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1988644/+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 1885388] [NEW] E: Failed to fetch store Hash Sum mismatch
Public bug reported: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- 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/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+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 1885388] Re: E: Failed to fetch store Hash Sum mismatch
$ uname -a; cat /etc/issue.net Linux XPS 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu Groovy Gorilla (development branch) -- 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/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+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 1885388] Re: E: Failed to fetch store Hash Sum mismatch
tried to remove /var/lib/apt/lists/* and redo the apt update ... but still getting the same Hash Sum mismatch -- 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/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+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 1885388] Re: E: Failed to fetch store Hash Sum mismatch
$ apt policy apt apt: Installed: 2.1.1 Candidate: 2.1.1 Version table: *** 2.1.1 100 100 /var/lib/dpkg/status -- 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/1885388 Title: E: Failed to fetch store Hash Sum mismatch Status in apt package in Ubuntu: New Bug description: E: Failed to fetch store:/var/lib/apt/lists/partial/my.archive.ubuntu.com_ubuntu_dists_groovy_main_binary-i386_Packages.xz Hash Sum mismatch Hashes of expected file: - Filesize:4196112 [weak] - SHA256:b415304a07d683f5841a2cd9cfbf44bc5b2afbe5a2f56e221d0d5c695da2da56 - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] Hashes of received file: - SHA256:3344338d5ab376c7db5c6f99bf8092931e75cc8fb1948a48e3eca78a30e666ea - SHA1:bc5afb5a7b0ee854629c13a7cf2a42059c57fbd3 [weak] - MD5Sum:387420e47971a78270c1b2052e35d3db [weak] - Filesize:4196112 [weak] Last modification reported: Sat, 27 Jun 2020 15:30:17 + Release file created at: Sat, 27 Jun 2020 15:29:16 + E: Some index files failed to download. They have been ignored, or old ones used instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1885388/+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 1786574] Re: remove i2c-i801 from blacklist
i'm having the issue again, i run the evtest and the output as attached ** Attachment added: "input.txt" https://bugs.launchpad.net/hwe-next/+bug/1786574/+attachment/5296792/+files/input.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: In Progress Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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
Re: [Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
Hi @Aaron & @Kai-Heng, I've installed the package and reboot + tried suspend 1 time. So far so good. Will let you know if this problem still occur in the future. Thanks ! On May 10 2019, at 11:35 pm, Kai-Heng Feng wrote: > Khairul, > > Does the touchpad work after boot, and after suspend? > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1786574 > > Title: > remove i2c-i801 from blacklist > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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
Re: [Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
Hi Aaron, Thanks for your prompt replied. I can't find the file synaptics.c to patch , mind to advise me how to patch ? On May 9 2019, at 10:21 pm, AaronMa wrote: > Hi, Khairul, > Could you try the attached patch? > > you can apply this patch in latest kernel. > And give it a try? no kernel parameter needed. > > If it works, I will upstream it. > Thanks in advance. > ** Patch added: > "0002-Input-synaptics-remove-X240-from-the-topbuttonpad-li.patch" > https://bugs.launchpad.net/hwe-next/+bug/1786574/+attachment/5262688/+files/0002-Input-synaptics-remove-X240-from-the-topbuttonpad-li.patch > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1786574 > > Title: > remove i2c-i801 from blacklist > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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
Re: [Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
Im still having this issue when booting from hibernate :( On Thu, May 9, 2019, 16:56 Yuan-Chen Cheng wrote: > ** Tags added: hwe oem-priority > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1786574 > > Title: > remove i2c-i801 from blacklist > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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
Re: [Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
@AaronMa, after recent updates and new kernel 5.0.0-13-generic , I can't reproduce the issue again. On Apr 17 2019, at 12:25 pm, AaronMa wrote: > @Khairul > > Please try passing "psmouse.synaptics_intertouch=0" in kernel parameter. > If it works, I will send a patch to mainline kernel. > Thanks, > Aaron > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1786574 > > Title: > remove i2c-i801 from blacklist > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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
Re: [Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
Nope, I need to re-modprobe the psmouse again to make my touchpad work again On Apr 16 2019, at 12:39 pm, Anthony Wong wrote: > @fenris > Adding back i2c_i801 to blacklist can make the touchpad work again? Is this > what you mean? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1786574 > > Title: > remove i2c-i801 from blacklist > > To manage notifications about this bug go to: > https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1786574] Re: remove i2c-i801 from blacklist
@aaronMa, i2c_i801 doesn't in blacklist, but touchpad still not working after suspend. My laptop model is Thinkpad X240 .. previously works okay in disco-alpha here is my dmesg : http://paste.ubuntu.com/p/kVrkSqxhYn/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: In Progress Status in OEM Priority Project: New Status in kmod package in Ubuntu: Fix Released Status in kmod source package in Xenial: In Progress Status in kmod source package in Bionic: In Progress Status in kmod source package in Cosmic: In Progress Bug description: SRU justification [Impact] Many modern notebooks need i2c-i801 kernel module to function, but it is blacklisted by /etc/modprobe/blacklist.conf, which gives a very poor user experience. [Test case] 1. Install Ubuntu 2. Check touchpad works or not 3. Install the fixed kmod package 4. Confirm touchpad works [Regression Potential] i2c-i801 was blacklisted due to bug 16602. The user complains an HP Compaq nc6000 notebook cannot suspend without blacklisting i2c-i801. While this is a way to workaround the suspend issue, the proper fix should be in linux kernel. Since nc6000 was a machine sold in 2004, it is too difficult to find someone to verify if it will regress due to this SRU. The rationale to blacklist it is: https://bugs.launchpad.net/ubuntu/+source/hotplug/+bug/16602/comments/5, however it is no longer valid nowadays on modern computers. Besides, there look like to be a quirk in linux kernel that fixes it: https://github.com/torvalds/linux/blame/master/drivers/pci/quirks.c#L1434 [Other Info] rationale of i2c_i801 driver blacklist: https://answers.launchpad.net/ubuntu/+source/kmod/+question/269329 --- Original bug report: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+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 1714396] Re: click-to-tap not working after sleep mode
anyone can help to verify this bugs? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1714396 Title: click-to-tap not working after sleep mode Status in ubuntu-meta package in Ubuntu: New Bug description: I've login after coming back from sleep mode then notice click-to-tap not working/functioning ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.398 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 09:43:07 2017 InstallationDate: Installed on 2017-05-04 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1714396/+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 1714396] [NEW] click-to-tap not working after sleep mode
Public bug reported: I've login after coming back from sleep mode then notice click-to-tap not working/functioning ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.398 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 09:43:07 2017 InstallationDate: Installed on 2017-05-04 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1714396 Title: click-to-tap not working after sleep mode Status in ubuntu-meta package in Ubuntu: New Bug description: I've login after coming back from sleep mode then notice click-to-tap not working/functioning ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-desktop 1.398 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 1 09:43:07 2017 InstallationDate: Installed on 2017-05-04 (119 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1714396/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
thanks @kzapalowicz however in Zesty ver. 1:10.0-1ubuntu2. Please advise. -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety
yeah, we are more than happy to test the fixes. Can't wait for the PPA, hope it will land in Zesty as well .. Kind Regards, ejat @ fenris -- 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/1438510 Title: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety Status in PulseAudio: Confirmed Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Bug description: Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1666135] [NEW] signon-ui crashed with SIGSEGV in QWindow::setModality()
Public bug reported: crashed upon login ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: signon-ui-x11 0.17+17.04.20161109-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Sun Feb 19 10:48:46 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2016-03-06 (351 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) ProcCmdline: /usr/bin/signon-ui SegvAnalysis: Segfault happened at: 0x7fa834804da0 <_ZN7QWindow11setModalityEN2Qt14WindowModalityE>: mov0x8(%rdi),%rax PC (0x7fa834804da0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo ** Affects: signon-ui (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace zesty ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1666135 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() Status in signon-ui package in Ubuntu: New Bug description: crashed upon login ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: signon-ui-x11 0.17+17.04.20161109-0ubuntu1 ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5 Uname: Linux 4.9.0-15-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity:Unity7 Date: Sun Feb 19 10:48:46 2017 ExecutablePath: /usr/bin/signon-ui InstallationDate: Installed on 2016-03-06 (351 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) ProcCmdline: /usr/bin/signon-ui SegvAnalysis: Segfault happened at: 0x7fa834804da0 <_ZN7QWindow11setModalityEN2Qt14WindowModalityE>: mov0x8(%rdi),%rax PC (0x7fa834804da0) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: signon-ui StacktraceTop: QWindow::setModality(Qt::WindowModality) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 ?? () ?? () ?? () QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: signon-ui crashed with SIGSEGV in QWindow::setModality() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt libvirtd lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1666135/+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 1630338] [NEW] Bluetooth Handsfree Broken Icon in Sound System Setting
Public bug reported: Please find the attached screenshot ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Handsfree Broken Icon in Sound System Setting" https://bugs.launchpad.net/bugs/1630338/+attachment/4754436/+files/Handsfree-broken-icon.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1630338 Title: Bluetooth Handsfree Broken Icon in Sound System Setting Status in ubuntu-themes package in Ubuntu: New Bug description: Please find the attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1630338/+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 1609707] Re: lxc in Power8 System
stgraber, i've tried to upgrade to xenial then it wont boot. after get feedback from vendor, its only support 14.04 & 15.10. http://tyan.com/tech/openpower/TYAN_openpower_OS_Supporting_Lists.html feedback from Softlayer: Hello, Unfortunately we do not know the time frame in which 16.04 LTS will be available for these machines our internal hardware solutions group has been working on this but no ETA on when this will be complete. Thank You, Michael A. Server Build Technician Softlayer, an IBM Company -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1609707 Title: lxc in Power8 System Status in lxc package in Ubuntu: Invalid Bug description: fenris@bigsoftware:~$ uname -a Linux bigsoftware 3.19.0-28.31-openpower1-generic #openpower1 SMP Wed Sep 9 10:34:29 AEST 2015 ppc64le ppc64le ppc64le GNU/Linux fenris@bigsoftware:~$ lxc No command 'lxc' found, did you mean: Command 'lc' from package 'mono-devel' (main) Command 'lpc' from package 'lprng' (universe) Command 'lpc' from package 'cups-bsd' (main) Command 'lpc' from package 'lpr' (universe) lxc: command not found fenris@bigsoftware:~$ dpkg -l | grep lxc ii liblxc1 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (library) ii lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools ii lxc-templates 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (templates) ii python3-lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (Python 3.x bindings) fenris@bigsoftware:~$ cat /etc/issue Ubuntu 14.04.5 LTS \n \l To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1609707/+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 1609707] Re: lxc in Power8 System
add-apt-repository ppa:ubuntu-lxc/lxd-stable install lxd fenris@bigsoftware:~$ lxc Usage: lxc [subcommand] [options] Available commands: config - Manage configuration. copy - Copy containers within or in between lxd instances. delete - Delete containers or container snapshots. exec - Execute the specified command in a container. file - Manage files on a container. help - Presents details on how to use LXD. image - Manipulate container images. info - List information on LXD servers and containers. launch - Launch a container from a particular image. list - Lists the available resources. move - Move containers within or in between lxd instances. profile- Manage configuration profiles. publish- Publish containers as images. remote - Manage remote LXD servers. restart- Changes state of one or more containers to restart. restore- Set the current state of a resource back to a snapshot. snapshot - Create a read-only snapshot of a container. start - Changes state of one or more containers to start. stop - Changes state of one or more containers to stop. version- Prints the version number of this client tool. Options: --all Print less common commands. --debugPrint debug information. --verbose Print verbose information. Environment: LXD_CONF Path to an alternate client configuration directory. LXD_DIRPath to an alternate server directory. ** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1609707 Title: lxc in Power8 System Status in lxc package in Ubuntu: Invalid Bug description: fenris@bigsoftware:~$ uname -a Linux bigsoftware 3.19.0-28.31-openpower1-generic #openpower1 SMP Wed Sep 9 10:34:29 AEST 2015 ppc64le ppc64le ppc64le GNU/Linux fenris@bigsoftware:~$ lxc No command 'lxc' found, did you mean: Command 'lc' from package 'mono-devel' (main) Command 'lpc' from package 'lprng' (universe) Command 'lpc' from package 'cups-bsd' (main) Command 'lpc' from package 'lpr' (universe) lxc: command not found fenris@bigsoftware:~$ dpkg -l | grep lxc ii liblxc1 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (library) ii lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools ii lxc-templates 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (templates) ii python3-lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (Python 3.x bindings) fenris@bigsoftware:~$ cat /etc/issue Ubuntu 14.04.5 LTS \n \l To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1609707/+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 1609707] [NEW] lxc in Power8 System
Public bug reported: fenris@bigsoftware:~$ uname -a Linux bigsoftware 3.19.0-28.31-openpower1-generic #openpower1 SMP Wed Sep 9 10:34:29 AEST 2015 ppc64le ppc64le ppc64le GNU/Linux fenris@bigsoftware:~$ lxc No command 'lxc' found, did you mean: Command 'lc' from package 'mono-devel' (main) Command 'lpc' from package 'lprng' (universe) Command 'lpc' from package 'cups-bsd' (main) Command 'lpc' from package 'lpr' (universe) lxc: command not found fenris@bigsoftware:~$ dpkg -l | grep lxc ii liblxc1 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (library) ii lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools ii lxc-templates 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (templates) ii python3-lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (Python 3.x bindings) fenris@bigsoftware:~$ cat /etc/issue Ubuntu 14.04.5 LTS \n \l ** Affects: lxc (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1609707 Title: lxc in Power8 System Status in lxc package in Ubuntu: Invalid Bug description: fenris@bigsoftware:~$ uname -a Linux bigsoftware 3.19.0-28.31-openpower1-generic #openpower1 SMP Wed Sep 9 10:34:29 AEST 2015 ppc64le ppc64le ppc64le GNU/Linux fenris@bigsoftware:~$ lxc No command 'lxc' found, did you mean: Command 'lc' from package 'mono-devel' (main) Command 'lpc' from package 'lprng' (universe) Command 'lpc' from package 'cups-bsd' (main) Command 'lpc' from package 'lpr' (universe) lxc: command not found fenris@bigsoftware:~$ dpkg -l | grep lxc ii liblxc1 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (library) ii lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools ii lxc-templates 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (templates) ii python3-lxc 1.0.8-0ubuntu0.3 ppc64el Linux Containers userspace tools (Python 3.x bindings) fenris@bigsoftware:~$ cat /etc/issue Ubuntu 14.04.5 LTS \n \l To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1609707/+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 1570359] [NEW] pcscd crashed with SIGSEGV in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__()
Public bug reported: crashed when login ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pcscd 1.8.14-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 4 17:29:56 2016 Disassembly: => 0x7f7da881b64c: Cannot access memory at address 0x7f7da881b64c ExecutablePath: /usr/sbin/pcscd InstallationDate: Installed on 2016-03-06 (39 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) ProcCmdline: /usr/sbin/pcscd --foreground --auto-exit SegvAnalysis: Segfault happened at: 0x7f7da881b64c: Cannot access memory at address 0x7f7da881b64c PC (0x7f7da881b64c) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing unknown VMA Signal: 11 SourcePackage: pcsc-lite StacktraceTop: ?? () __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__ () from /lib/x86_64-linux-gnu/libc.so.6 ?? () Title: pcscd crashed with SIGSEGV in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace xenial ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1570359 Title: pcscd crashed with SIGSEGV in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__() Status in pcsc-lite package in Ubuntu: New Bug description: crashed when login ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pcscd 1.8.14-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Mon Apr 4 17:29:56 2016 Disassembly: => 0x7f7da881b64c: Cannot access memory at address 0x7f7da881b64c ExecutablePath: /usr/sbin/pcscd InstallationDate: Installed on 2016-03-06 (39 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) ProcCmdline: /usr/sbin/pcscd --foreground --auto-exit SegvAnalysis: Segfault happened at: 0x7f7da881b64c:Cannot access memory at address 0x7f7da881b64c PC (0x7f7da881b64c) not located in a known VMA region (needed executable region)! Stack memory exhausted (SP below stack segment) SegvReason: executing unknown VMA Signal: 11 SourcePackage: pcsc-lite StacktraceTop: ?? () __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__ () from /lib/x86_64-linux-gnu/libc.so.6 ?? () Title: pcscd crashed with SIGSEGV in __elf_set___libc_thread_subfreeres_element___rpc_thread_destroy__() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1570359/+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 1451728] Re: [master] kde-config-telepathy-accounts package install error
its still broke in Xenial /var/cache/apt/archives/kde-config-telepathy- accounts_4%3a15.12.1-1ubuntu1_amd64.deb need to fenris@x240:~⟫ sudo dpkg -i --force-overwrite /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.1-1ubuntu1_amd64.deb (Reading database ... 279743 files and directories currently installed.) Preparing to unpack .../kde-config-telepathy-accounts_4%3a15.12.1-1ubuntu1_amd64.deb ... Unpacking kde-config-telepathy-accounts (4:15.12.1-1ubuntu1) over (4:15.12.1-1ubuntu1) ... Setting up kde-config-telepathy-accounts (4:15.12.1-1ubuntu1) ... Processing triggers for libc-bin (2.21-0ubuntu6) ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libaccounts-glib in Ubuntu. https://bugs.launchpad.net/bugs/1451728 Title: [master] kde-config-telepathy-accounts package install error Status in Kubuntu PPA: Confirmed Status in meta-telepathy: Fix Released Status in kaccounts-providers package in Ubuntu: Triaged Status in ktp-accounts-kcm package in Ubuntu: Triaged Status in libaccounts-glib package in Ubuntu: In Progress Status in kaccounts-providers source package in Wily: Triaged Status in ktp-accounts-kcm source package in Wily: Triaged Bug description: Installing from Kubuntu 15.04 backports: Unpacking kde-config-telepathy-accounts (15.04.0-0ubuntu1~ubuntu15.04~ppa1) over (0.9.0-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_15.04.0-0ubuntu1~ubuntu15.04~ppa1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/facebook-im.service', which is also in package account-plugin-facebook 0.12+15.04.20150415.1-0ubuntu1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) To manage notifications about this bug go to: https://bugs.launchpad.net/kubuntu-ppa/+bug/1451728/+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 1487569] Re: a lot of packages need to be remove when execute apt-get dist-upgrade
adding ppa:kubuntu-ppa/staging-kdeapplications based on feedback from #kubuntu-devel -- 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/1487569 Title: a lot of packages need to be remove when execute apt-get dist-upgrade Status in apt package in Ubuntu: New Bug description: as spoken with cjwatson in #ubuntu-devel , please find the debug output as below: http://paste.ubuntu.com/12142592/ http://paste.ubuntu.com/12142634/ tarball for /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+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
Re: [Touch-packages] [Bug 1487569] Re: a lot of packages need to be remove when execute apt-get dist-upgrade
http://paste.ubuntu.com/12152420/ On Sun, Aug 23, 2015 at 12:54 AM, Khairul Aizat Kamarudzzaman fen...@ubuntu.com.my wrote: adding ppa:kubuntu-ppa/staging-kdeapplications based on feedback from #kubuntu-devel -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1487569 Title: a lot of packages need to be remove when execute apt-get dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+subscriptions -- 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/1487569 Title: a lot of packages need to be remove when execute apt-get dist-upgrade Status in apt package in Ubuntu: New Bug description: as spoken with cjwatson in #ubuntu-devel , please find the debug output as below: http://paste.ubuntu.com/12142592/ http://paste.ubuntu.com/12142634/ tarball for /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+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 1487569] Re: a lot of files to be removed when execute apt-get dist-upgrade
** Attachment added: /var/lib/apt https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+attachment/4450423/+files/var-lib-apt.tar.gz -- 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/1487569 Title: a lot of files to be removed when execute apt-get dist-upgrade Status in apt package in Ubuntu: New Bug description: as spoken with cjwatson in #ubuntu-devel , please find the debug output as below: http://paste.ubuntu.com/12142592/ http://paste.ubuntu.com/12142634/ tarball for /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+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 1487569] Re: a lot of packages need to be removed when execute apt-get dist-upgrade
$ uname -a; cat /etc/issue Linux macbuntu 4.1.0-3-generic #3-Ubuntu SMP Tue Jul 28 12:22:42 UTC 2015 i686 i686 i686 GNU/Linux Ubuntu Wily Werewolf (development branch) \n \l ** Summary changed: - a lot of files to be removed when execute apt-get dist-upgrade + a lot of packages need to be removed when execute apt-get dist-upgrade ** Summary changed: - a lot of packages need to be removed when execute apt-get dist-upgrade + a lot of packages need to be remove when execute apt-get dist-upgrade -- 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/1487569 Title: a lot of packages need to be remove when execute apt-get dist-upgrade Status in apt package in Ubuntu: New Bug description: as spoken with cjwatson in #ubuntu-devel , please find the debug output as below: http://paste.ubuntu.com/12142592/ http://paste.ubuntu.com/12142634/ tarball for /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+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 1487569] [NEW] a lot of files to be removed when execute apt-get dist-upgrade
Public bug reported: as spoken with cjwatson in #ubuntu-devel , please find the debug output as below: http://paste.ubuntu.com/12142592/ http://paste.ubuntu.com/12142634/ tarball for /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as attached. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Attachment added: /var/lib/dpkg https://bugs.launchpad.net/bugs/1487569/+attachment/4450422/+files/var-lib-dpkg.tar.gz -- 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/1487569 Title: a lot of files to be removed when execute apt-get dist-upgrade Status in apt package in Ubuntu: New Bug description: as spoken with cjwatson in #ubuntu-devel , please find the debug output as below: http://paste.ubuntu.com/12142592/ http://paste.ubuntu.com/12142634/ tarball for /var/lib/apt/, /var/cache/apt/, and /var/lib/dpkg/ as attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1487569/+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 1464753] Re: package software-properties-kde 0.96.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Setting up software-properties-kde (0.96.7) ... File /usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py, line 732 text = %s\n\nsmall%s/small) % primary, msg ^ SyntaxError: invalid syntax dpkg: error processing package software-properties-kde (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: software-properties-kde E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1464753 Title: package software-properties-kde 0.96.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in software-properties package in Ubuntu: New Bug description: ubuntuGNOME Wily with KDE Desktop also installed. dpkg: error processing package software-properties-kde (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: software-properties-kde I'll try to configure after reboot ProblemType: Package DistroRelease: Ubuntu 15.10 Package: software-properties-kde 0.96.7 Uname: Linux 4.1.0-040100rc7-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 Date: Fri Jun 12 15:10:02 2015 DuplicateSignature: package:software-properties-kde:0.96.7:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-03-28 (75 days ago) InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.10ubuntu1 SourcePackage: software-properties Title: package software-properties-kde 0.96.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1464753/+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
