[Touch-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
The gnome-control-center fix. ** Patch added: "gnome-control-center_3.27.92-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1686081/+attachment/5080005/+files/gnome-control-center_3.27.92-1ubuntu2.debdiff ** No longer affects: ubuntu ** No longer affects: Ubuntu Artful ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
** Changed in: ubuntu Importance: Undecided => Medium ** Changed in: ubuntu Status: New => In Progress ** Changed in: ubuntu Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Importance: Undecided => Medium ** Changed in: ubuntu Status: New => In Progress ** Changed in: ubuntu Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
The mutter fix. ** Patch added: "mutter_3.28.0-1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1686081/+attachment/5080004/+files/mutter_3.28.0-1ubuntu1.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
I'm merging bug 1733032 (which contains fixes) into this one. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu Artful) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: Ubuntu Artful Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work
** Package changed: gtk+3.0 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => In Progress ** Changed in: ubuntu Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: xorg (Ubuntu) Status: Confirmed => Invalid ** Changed in: xorg (Ubuntu Artful) Status: Confirmed => Invalid ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-control-center (Ubuntu) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686081 Title: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work Status in Release Notes for Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: In Progress Status in mutter package in Ubuntu: In Progress Status in xorg package in Ubuntu: Invalid Status in xubuntu-meta package in Ubuntu: Fix Released Status in gnome-control-center source package in Artful: Confirmed Status in mutter source package in Artful: Confirmed Status in xorg source package in Artful: Invalid Status in xubuntu-meta source package in Artful: Fix Released Bug description: I'm splitting this issue off from LP: #1685542 (which made xserver- xorg-input-all no longer recommend xserver-xorg-input-synaptics) for tracking the remaining issues. gnome-control-center only supports libinput. If xserver-xorg-input- synaptics is installed (because it's used by some desktops which haven't been ported to libinput yet), synaptics overrides libinput. That makes gnome-control-center's Mouse & Touchpad settings panel only show basic settings and important configurations don't work. Questions - 1. Which desktops/apps still need -synaptics? - Unity - Xfce? - LXDE? LXQt? All the other major desktops have already been ported (LP: #1417980) 2. Can these apps be ported or removed before 18.04 LTS is released? 3. Can the desktops be ported and how bad is it if they are not ported and -synaptics is no longer available? 4. If -synaptics can't be removed completely from 18.04 LTS, does it make sense to have gnome-control-center Conflicts: xserver-xorg-input- synaptics? 5. Is there any other way we can fix this conflict? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1733032] Re: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed)
*** This bug is a duplicate of bug 1686081 *** https://bugs.launchpad.net/bugs/1686081 ** This bug has been marked a duplicate of bug 1686081 If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work ** This bug is no longer a duplicate of bug 1686081 If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work ** This bug has been marked a duplicate of bug 1686081 If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed) Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: Since upgrading to 17.10, my mouse pointer is repeatedly and frequently getting moved against my will when I am typing on my laptop keyboard (as opposed to external keyboard) because my hand brushes against the touchpad or even just near its surface. Furthermore, I don't want tap-to-click to be enabled. I want to actually have to push down on the mousepad hard enough to click it to generate a mouse button event. I can't figure out how to disable tap- to-click in 17.10 either. I did not have these problems _at all_ in 17.04. I have the touchpad click method set to "Areas" and "Disable While Typing" enabled in gnome-tweak-tool. This does not help. I have these lines in the touchpad section of /usr/share/X11/xorg.conf.d/40-libinput.conf as well: Option "DisableWhileTyping" "true" Option "PalmDetection" "true" Option "Tapping" "false" They don't help either. This is a substantial regression in functionality from 17.04. It appears to be a problem using both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 21:28:05 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (182 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733032/+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 1286840] Re: pulseaudio crashed with signal 7 in elf_machine_rel()
Incomplete. I think this was fixed or never reoccurred after 14.04. I can't find any other reports of it. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1286840 Title: pulseaudio crashed with signal 7 in elf_machine_rel() Status in pulseaudio package in Ubuntu: Incomplete Bug description: me pone error al iniciar y tarda mucho en arrancar ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-14.34-generic 3.13.5 Uname: Linux 3.13.0-14-generic i686 ApportVersion: 2.13.2-0ubuntu5 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sun Mar 2 17:09:29 2014 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-02-20 (9 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20140220.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 7 SourcePackage: pulseaudio StacktraceTop: elf_machine_rel (reloc=0xb765fbd0, skip_ifunc=, reloc_addr_arg=, version=0xb6d1dba8, sym=0xb7658d14, map=0xb770d930) at ../sysdeps/i386/dl-machine.h:337 elf_dynamic_do_Rel (skip_ifunc=, lazy=0, nrelative=, relsize=, reladdr=, map=) at do-rel.h:137 _dl_relocate_object (scope=0xb770dae8, reloc_mode=1, consider_profiling=0) at dl-reloc.c:264 dl_main (phdr=, phnum=, user_entry=0xbf80a95c, auxv=0xbf80aa40) at rtld.c:2204 _dl_sysdep_start (start_argptr=start_argptr@entry=0xbf80a9f0, dl_main=dl_main@entry=0xb7710650 ) at ../elf/dl-sysdep.c:249 Title: pulseaudio crashed with signal 7 in elf_machine_rel() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/20/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R1120Y4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR1120Y4:bd08/20/2009:svnSonyCorporation:pnVGN-NW21EF_S:pvrC602NXNT:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-NW21EF_S dmi.product.version: C602NXNT dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1286840/+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 1493481] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch
Fix released (zero crash reports after 15.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- 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/1493481 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from avctp_confirm_cb:server_cb from g_main_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/1c7ce0e3d4d00429fd1a154776e90a7b6a1a3ca5 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493481/+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 1290542] Re: pulseaudio crashed with SIGSEGV in prepare_next_write_item()
Incomplete. I think this was fixed or never reoccurred after 14.04. I can't find any other reports of it. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1290542 Title: pulseaudio crashed with SIGSEGV in prepare_next_write_item() Status in pulseaudio package in Ubuntu: Incomplete Bug description: crashed while watching video via hdmi display port and hdmi displayport audio ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-16.36-generic 3.13.5 Uname: Linux 3.13.0-16-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 2416 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 10 21:27:32 2014 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-03-07 (3 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140301) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so pa_mainloop_dispatch () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 main () Title: pulseaudio crashed with SIGSEGV in pa_mainloop_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1290542/+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 1273805] Re: pulseaudio crashed with SIGABRT in pa_rtsp_setparameter()
Incomplete. I think this was fixed or never reoccurred after 14.04. I can't find any other reports of it. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1273805 Title: pulseaudio crashed with SIGABRT in pa_rtsp_setparameter() Status in pulseaudio package in Ubuntu: Incomplete Bug description: Happened in background while trying to play YouTube video ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erik 15615 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 28 19:46:56 2014 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2011-09-14 (867 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANGUAGE=de_DE XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_rtsp_setparameter () from /usr/lib/pulse-4.0/modules/librtp.so pa_raop_client_set_volume () from /usr/lib/pulse-4.0/modules/libraop.so pa_sink_set_mute () from /usr/lib/libpulsecore-4.0.so ?? () from /usr/lib/pulse-4.0/modules/libprotocol-native.so pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-4.0.so Title: pulseaudio crashed with SIGABRT in pa_rtsp_setparameter() UpgradeStatus: Upgraded to trusty on 2013-12-09 (50 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 06/19/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0HN341 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd06/19/2013:svnDellInc.:pnLatitudeD830:pvr:rvnDellInc.:rn0HN341:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Latitude D830 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1273805/+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 1493528] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch
Fix released (zero crash reports after 15.04) -- 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/1493528 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/b2077378adbdb76716399672a8b463aeffbfea17 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493528/+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 1493528] Re: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch
Fix released (zero crash reports after 15.04) ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- 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/1493528 Title: bluetoothd crashed with SIGSEGV in state_changed from avctp_set_state from session_cb from g_main_dispatch:g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with version 4.101-0ubuntu25.1~overlay2, the problem page at https://errors.ubuntu.com/problem/b2077378adbdb76716399672a8b463aeffbfea17 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1493528/+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 1690060] Re: pulseaudio crashed with SIGABRT in memcpy() from memblock_make_local() from pa_memblock_unref_fixed() from mmap_read() from thread_func()
Fix released (zero crash reports after 17.04) ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1690060 Title: pulseaudio crashed with SIGABRT in memcpy() from memblock_make_local() from pa_memblock_unref_fixed() from mmap_read() from thread_func() Status in pulseaudio package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding pulseaudio. This problem was most recently seen with package version 1:9.0-2ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/963a8640e82ef6b116ef4a527b326054260506c0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1690060/+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 981149] Re: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile() from command_set_card
Fix released (zero crashes reported after 14.04) ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/981149 Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile() from command_set_card_profile() Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/19109234540b458347c4e4fafa9d895523ba2431 --- When I switch between my headphones and/or my Logitech lap desk N700 speakers the sound will crash. I usually have to restart my laptop to get everything to work again. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: pulseaudio 1:1.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu2 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 6394 F pulseaudio /dev/snd/controlC0: mark 6394 F pulseaudio /dev/snd/pcmC0D0p: mark 6394 F...m pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfc50 irq 49' Mixer name : 'Realtek ALC268' Components : 'HDA:10ec0268,1179ff02,0013 HDA:11c11040,11790001,00100200' Controls : 16 Simple ctrls : 9 Card1.Amixer.info: Card hw:1 'N700'/'Logitech Logitech Speaker Lapdesk N700 at usb-:00:1d.0-2, full speed' Mixer name : 'USB Mixer' Components : 'USB046d:0a1a' Controls : 2 Simple ctrls : 1 Date: Fri Apr 13 16:28:44 2012 ExecutablePath: /usr/bin/pulseaudio InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: pulseaudio StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 pa_sink_input_finish_move () from /usr/lib/libpulsecore-1.1.so pa_sink_move_all_finish () from /usr/lib/libpulsecore-1.1.so ?? () from /usr/lib/pulse-1.1/modules/module-alsa-card.so Title: pulseaudio crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 08/28/2008 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.60 dmi.board.name: ISKAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.60:bd08/28/2008:svnTOSHIBA:pn*:pvr*:rvnTOSHIBA:rnISKAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: * dmi.product.version: * dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/981149/+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 1299219] Re: pulseaudio crashed with SIGILL in pa_alsa_ucm_mapping_context_free()
Incomplete. I think this was fixed or never reoccurred after 14.04. I can't find any other reports of it. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1299219 Title: pulseaudio crashed with SIGILL in pa_alsa_ucm_mapping_context_free() Status in pulseaudio package in Ubuntu: Incomplete Bug description: seen when just logging in for the first time after a reboot ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6 Uname: Linux 3.13.0-19-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D1c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Mar 28 21:02:15 2014 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-02-22 (34 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140220.1) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) LANGUAGE=en_GB:en XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed to kill PulseAudio daemon. Signal: 4 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_mapping_context_free () from /usr/lib/pulse-4.0/modules/libalsa-util.so ?? () from /usr/lib/pulse-4.0/modules/libalsa-util.so pa_alsa_profile_set_drop_unsupported () from /usr/lib/pulse-4.0/modules/libalsa-util.so pa_alsa_profile_set_probe () from /usr/lib/pulse-4.0/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-4.0/modules/module-alsa-card.so Title: pulseaudio crashed with SIGILL in pa_alsa_ucm_mapping_context_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1299219/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
@Maarten: Maybe spotify will install and work from its flatpak? It's the second flatpak app listed here: https://www.omgubuntu.co.uk/2017/07/7 -flatpak-apps-can-install-right-now-flathub -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755973] Re: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdca in Ubuntu. https://bugs.launchpad.net/bugs/1755973 Title: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libdca package in Ubuntu: New Bug description: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration I have reinstalled it but getting same error every time I tried to install any package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdca0:i386 0.0.5-7build1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Thu Mar 15 09:14:55 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu10 DpkgHistoryLog: Start-Date: 2018-03-15 09:14:39 Commandline: apt-get install ansible Requested-By: ashish (1000) Install: python-markupsafe:i386 (0.23-2build2, automatic), python-yaml:i386 (3.11-3build1, automatic), python-selinux:i386 (2.4-3build2, automatic), python-crypto:i386 (2.6.1-6ubuntu0.16.04.2, automatic), python-jinja2:i386 (2.8-1, automatic), python-paramiko:i386 (1.16.0-1, automatic), python-ecdsa:i386 (0.13-2, automatic), python-netaddr:i386 (0.7.18-1, automatic), ieee-data:i386 (20150531.1, automatic), ansible:i386 (2.0.0.2-2ubuntu1), python-httplib2:i386 (0.9.1+dfsg-1, automatic) DuplicateSignature: package:libdca0:i386:0.0.5-7build1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libdca0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-02-13 (29 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: libdca Title: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdca/+bug/1755973/+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 1755973] [NEW] package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration I have reinstalled it but getting same error every time I tried to install any package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdca0:i386 0.0.5-7build1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Thu Mar 15 09:14:55 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu10 DpkgHistoryLog: Start-Date: 2018-03-15 09:14:39 Commandline: apt-get install ansible Requested-By: ashish (1000) Install: python-markupsafe:i386 (0.23-2build2, automatic), python-yaml:i386 (3.11-3build1, automatic), python-selinux:i386 (2.4-3build2, automatic), python-crypto:i386 (2.6.1-6ubuntu0.16.04.2, automatic), python-jinja2:i386 (2.8-1, automatic), python-paramiko:i386 (1.16.0-1, automatic), python-ecdsa:i386 (0.13-2, automatic), python-netaddr:i386 (0.7.18-1, automatic), ieee-data:i386 (20150531.1, automatic), ansible:i386 (2.0.0.2-2ubuntu1), python-httplib2:i386 (0.9.1+dfsg-1, automatic) DuplicateSignature: package:libdca0:i386:0.0.5-7build1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libdca0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-02-13 (29 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: libdca Title: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libdca (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdca in Ubuntu. https://bugs.launchpad.net/bugs/1755973 Title: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libdca package in Ubuntu: New Bug description: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration I have reinstalled it but getting same error every time I tried to install any package. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdca0:i386 0.0.5-7build1 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Thu Mar 15 09:14:55 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 multiarch-support 2.23-0ubuntu10 DpkgHistoryLog: Start-Date: 2018-03-15 09:14:39 Commandline: apt-get install ansible Requested-By: ashish (1000) Install: python-markupsafe:i386 (0.23-2build2, automatic), python-yaml:i386 (3.11-3build1, automatic), python-selinux:i386 (2.4-3build2, automatic), python-crypto:i386 (2.6.1-6ubuntu0.16.04.2, automatic), python-jinja2:i386 (2.8-1, automatic), python-paramiko:i386 (1.16.0-1, automatic), python-ecdsa:i386 (0.13-2, automatic), python-netaddr:i386 (0.7.18-1, automatic), ieee-data:i386 (20150531.1, automatic), ansible:i386 (2.0.0.2-2ubuntu1), python-httplib2:i386 (0.9.1+dfsg-1, automatic) DuplicateSignature: package:libdca0:i386:0.0.5-7build1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package libdca0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-02-13 (29 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: libdca Title: package libdca0:i386 0.0.5-7build1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdca/+bug/1755973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~tou
[Touch-packages] [Bug 1755144] Re: No audio on vlc or videos sound or video files
Thanks. It looks like your issues might be caused by these unsupported package versions you have installed: ii libavcodec-extra 7:3.3.3-2~ubuntu16.04.1~ppa1 all FFmpeg library with extra codecs (metapackage) ii libavcodec-extra57:amd64 7:3.3.3-2~ubuntu16.04.1~ppa1 amd64FFmpeg library with additional de/encoders for audio/video codecs ii libavdevice57:amd64 7:3.2.6-1~backport1.1~xenial amd64FFmpeg library for handling input and output devices - runtime files ii libavfilter6:amd647:3.2.6-1~backport1.1~xenial amd64FFmpeg library containing media filters - runtime files ii libavformat57:amd64 7:3.2.6-1~backport1.1~xenial amd64FFmpeg library with (de)muxers for multimedia containers - runtime files ii libavresample3:amd64 7:3.3.3-2~ubuntu16.04.1~ppa1 amd64FFmpeg compatibility library for resampling - runtime files ii libavutil55:amd64 7:3.3.3-2~ubuntu16.04.1~ppa1 amd64FFmpeg library with functions for simplifying programming - runtime files Your system appears to be mixing and matching the standard ffmpeg packages from Ubuntu 16.04 (version 7:2.8.11-0ubuntu0.16.04.1) and nonstandard ones from PPAs. Please purge all PPAs from your system and retest: 1. sudo apt install ppa-purge 2. sudo ppa-purge (on all the PPAs you are using) 3. Retest and provide new output from 'dpkg -l | grep libav > libav.txt' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1755144 Title: No audio on vlc or videos sound or video files Status in pulseaudio package in Ubuntu: Incomplete Bug description: Up until a few weeks ago there was no problem with playing sound from mp3 files. I have a pair of usb speakers. Audio plays Ok on them for video clips using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok using Rhythmbox. I've also tried vlc 3.0 with no success. Interestingly, the standard Videos app (Totem?) also doesn't play sound on these speakers either of an mp4 file (downloaded from YouTube, though it plays Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I first reported this as bug 1752267 as I thought that the problem was with vlc. On that bug, it was suggested that the problem is with Pulseaudio. Just now, I've tried to play sound through my monitor's built in speakers connected by hdmi (though the monitor displays Ok) with no success even though the built-in speakers play sound using pavucontrol when testing is invoked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2410 F pulseaudio /dev/snd/controlC0: john 2410 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 12 11:06:46 2018 InstallationDate: Installed on 2016-12-08 (458 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
Trusty is technically not directly affected by the container proc issue as there was an Ubuntu patch dropped in xenial to skip setting rlimit- nproc when /run/container_type=lxc Could happen if that doesn't exist though, and the memory issue can still occur, so still recommend upload. ** Description changed: [Original Description] The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. [Issue] Avahi sets a number of rlimits on startup including the maximum number of processes (nproc=2) and limits on memory usage. These limits are hit in a number of cases - specifically the maximum process limit is hit if you run lxd containers in 'privileged' mode such that avahi has the same uid in multiple containers and large networks can trigger the memory limit. The fix is to remove these default rlimits completely from the configuration file. [Impact] - * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. - * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 + * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. + * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 [Test Case] - * setup lxd (apt install lxd, lxd init, get working networking) - * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true - * lxc exec avahi-test sudo apt install avahi-daemon + * setup lxd (apt install lxd, lxd init, get working networking) + * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true + * lxc exec avahi-test sudo apt install avahi-daemon This will fail if the parent host has avahi-daemon installed, however, if it does not you can setup a second container (avahi-test2) and install avahi there. That should then fail (as the issue requires 2 copies of avahi-daemon in the same uid namespace to fail) [Regression Potential] - * The fix removes all rlimits configured by avahi on startup, this is + * The fix removes all rlimits configured by avahi on startup, this is an extra step avahi takes that most programs did not take (limiting memory usage, running process count, etc). It's possible an unknown bug then consumes significant system resources as a result of that limit no longer being in place, that was previously hidden by Avahi crashing instead. However I believe this risk is significantly reduced as this change has been shipping upstream for many months and have not seen any reports of new problems - however it has fixed a number of existing crashes/problems. [Other Info] - - * This change already exists upstream in 0.7 which is in bionic. SRU required to artful, xenial, trusty. - * The main case this may not fix the issue is if they have modified their avahi-daemon.conf file - but it will fix new installs and most installs as most users don't modify the file. And users may be prompted on upgrade to replace the file. + + * This change already exists upstream in 0.7 which is in bionic. SRU required to artful, xenial, trusty. + * The main case this may not fix the issue is if they have modified their avahi-daemon.conf file - but it will fix new installs and most installs as most users don't modify the file. And users may be prompted on upgrade to replace the file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: Invalid Status in avahi package in Ubuntu: In Progress Status in lxd package in Ubuntu: Invalid Bug description: [Original Description] The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermai
[Touch-packages] [Bug 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
** Patch added: "lp1661869-trusty.debdiff" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079951/+files/lp1661869-trusty.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: Invalid Status in avahi package in Ubuntu: In Progress Status in lxd package in Ubuntu: Invalid Bug description: [Original Description] The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. [Issue] Avahi sets a number of rlimits on startup including the maximum number of processes (nproc=2) and limits on memory usage. These limits are hit in a number of cases - specifically the maximum process limit is hit if you run lxd containers in 'privileged' mode such that avahi has the same uid in multiple containers and large networks can trigger the memory limit. The fix is to remove these default rlimits completely from the configuration file. [Impact] * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 [Test Case] * setup lxd (apt install lxd, lxd init, get working networking) * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true * lxc exec avahi-test sudo apt install avahi-daemon This will fail if the parent host has avahi-daemon installed, however, if it does not you can setup a second container (avahi-test2) and install avahi there. That should then fail (as the issue requires 2 copies of avahi-daemon in the same uid namespace to fail) [Regression Potential] * The fix removes all rlimits configured by avahi on startup, this is an extra step avahi takes that most programs did not take (limiting memory usage, running process count, etc). It's possible an unknown bug then consumes significant system resources as a result of that limit no longer being in place, that was previously hidden by Avahi crashing instead. However I believe this risk is significantly reduced as this change has been shipping upstream for many months and have not seen any reports of new problems - however it has fixed a number of existing crashes/problems. [Other Info] * This change already exists upstream in 0.7 which is in bionic. SRU required to artful, xenial, trusty. * The main case this may not fix the issue is if they have modified their avahi-daemon.conf file - but it will fix new installs and most installs as most users don't modify the file. And users may be prompted on upgrade to replace the file. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1638345] Re: avahi-daemon crashes multiple times an hour
I have updated Bug #1661869 with an SRU template and new updates to fix this issue, plus the issue in that bug. The fix is simply to update /etc/avahi/avahi-daemon.conf and comment out the entire [rlimits] section. You can do this yourself (but the package update will do it for you). It'd be great if you can try this fix yourself and report back on if that fixes the issue for you, if not, please consider opening a new bug using apport. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
** Patch added: "lp1661869-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079950/+files/lp1661869-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: Invalid Status in avahi package in Ubuntu: In Progress Status in lxd package in Ubuntu: Invalid Bug description: [Original Description] The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. [Issue] Avahi sets a number of rlimits on startup including the maximum number of processes (nproc=2) and limits on memory usage. These limits are hit in a number of cases - specifically the maximum process limit is hit if you run lxd containers in 'privileged' mode such that avahi has the same uid in multiple containers and large networks can trigger the memory limit. The fix is to remove these default rlimits completely from the configuration file. [Impact] * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 [Test Case] * setup lxd (apt install lxd, lxd init, get working networking) * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true * lxc exec avahi-test sudo apt install avahi-daemon This will fail if the parent host has avahi-daemon installed, however, if it does not you can setup a second container (avahi-test2) and install avahi there. That should then fail (as the issue requires 2 copies of avahi-daemon in the same uid namespace to fail) [Regression Potential] * The fix removes all rlimits configured by avahi on startup, this is an extra step avahi takes that most programs did not take (limiting memory usage, running process count, etc). It's possible an unknown bug then consumes significant system resources as a result of that limit no longer being in place, that was previously hidden by Avahi crashing instead. However I believe this risk is significantly reduced as this change has been shipping upstream for many months and have not seen any reports of new problems - however it has fixed a number of existing crashes/problems. [Other Info] * This change already exists upstream in 0.7 which is in bionic. SRU required to artful, xenial, trusty. * The main case this may not fix the issue is if they have modified their avahi-daemon.conf file - but it will fix new installs and most installs as most users don't modify the file. And users may be prompted on upgrade to replace the file. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
** Patch added: "lp1661869-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661869/+attachment/5079949/+files/lp1661869-artful.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: Invalid Status in avahi package in Ubuntu: In Progress Status in lxd package in Ubuntu: Invalid Bug description: [Original Description] The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. [Issue] Avahi sets a number of rlimits on startup including the maximum number of processes (nproc=2) and limits on memory usage. These limits are hit in a number of cases - specifically the maximum process limit is hit if you run lxd containers in 'privileged' mode such that avahi has the same uid in multiple containers and large networks can trigger the memory limit. The fix is to remove these default rlimits completely from the configuration file. [Impact] * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 [Test Case] * setup lxd (apt install lxd, lxd init, get working networking) * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true * lxc exec avahi-test sudo apt install avahi-daemon This will fail if the parent host has avahi-daemon installed, however, if it does not you can setup a second container (avahi-test2) and install avahi there. That should then fail (as the issue requires 2 copies of avahi-daemon in the same uid namespace to fail) [Regression Potential] * The fix removes all rlimits configured by avahi on startup, this is an extra step avahi takes that most programs did not take (limiting memory usage, running process count, etc). It's possible an unknown bug then consumes significant system resources as a result of that limit no longer being in place, that was previously hidden by Avahi crashing instead. However I believe this risk is significantly reduced as this change has been shipping upstream for many months and have not seen any reports of new problems - however it has fixed a number of existing crashes/problems. [Other Info] * This change already exists upstream in 0.7 which is in bionic. SRU required to artful, xenial, trusty. * The main case this may not fix the issue is if they have modified their avahi-daemon.conf file - but it will fix new installs and most installs as most users don't modify the file. And users may be prompted on upgrade to replace the file. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1661869/+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 1661869] Re: maas install fails inside of a 16.04 lxd container due to avahi problems
** Description changed: - The bug, and workaround, are clearly described in this mailing list - thread: + [Original Description] + The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. + + [Issue] + Avahi sets a number of rlimits on startup including the maximum number of processes (nproc=2) and limits on memory usage. These limits are hit in a number of cases - specifically the maximum process limit is hit if you run lxd containers in 'privileged' mode such that avahi has the same uid in multiple containers and large networks can trigger the memory limit. + + The fix is to remove these default rlimits completely from the + configuration file. + + [Impact] + + * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. + * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 + + [Test Case] + + * setup lxd (apt install lxd, lxd init, get working networking) + * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true + * lxc exec avahi-test sudo apt install avahi-daemon + + This will fail if the parent host has avahi-daemon installed, however, + if it does not you can setup a second container (avahi-test2) and + install avahi there. That should then fail (as the issue requires 2 + copies of avahi-daemon in the same uid namespace to fail) + + [Regression Potential] + + * The fix removes all rlimits configured by avahi on startup, this is + an extra step avahi takes that most programs did not take (limiting + memory usage, running process count, etc). It's possible an unknown bug + then consumes significant system resources as a result of that limit no + longer being in place, that was previously hidden by Avahi crashing + instead. However I believe this risk is significantly reduced as this + change has been shipping upstream for many months and have not seen any + reports of new problems - however it has fixed a number of existing + crashes/problems. + + [Other Info] + + * This change already exists upstream in 0.7 which is in bionic. SRU required to artful, xenial, trusty. + * The main case this may not fix the issue is if they have modified their avahi-daemon.conf file - but it will fix new installs and most installs as most users don't modify the file. And users may be prompted on upgrade to replace the file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661869 Title: maas install fails inside of a 16.04 lxd container due to avahi problems Status in MAAS: Invalid Status in avahi package in Ubuntu: In Progress Status in lxd package in Ubuntu: Invalid Bug description: [Original Description] The bug, and workaround, are clearly described in this mailing list thread: https://lists.linuxcontainers.org/pipermail/lxc- users/2016-January/010791.html I'm trying to install MAAS in a LXD container, but that's failing due to avahi package install problems. I'm tagging all packages here. [Issue] Avahi sets a number of rlimits on startup including the maximum number of processes (nproc=2) and limits on memory usage. These limits are hit in a number of cases - specifically the maximum process limit is hit if you run lxd containers in 'privileged' mode such that avahi has the same uid in multiple containers and large networks can trigger the memory limit. The fix is to remove these default rlimits completely from the configuration file. [Impact] * Avahi is unable to start inside of containers without UID namespace isolation because an rlimit on the maximum number of processes is set by default to 2. When a container launches Avahi, the total number of processes on the system in all containers exceeds this limit and Avahi is killed. It also fails at install time, rather than runtime due to a failure to start the service. * Some users also have issues with the maximum memory allocation causing Avahi to exit on networks with a large number of services as the memory limit was quite small (4MB). Refer LP #1638345 [Test Case] * setup lxd (apt install lxd, lxd init, get working networking) * lxc launch ubuntu:16.04 avahi-test --config security.privileged=true * lxc exec
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
** Changed in: avahi (Ubuntu) Assignee: (unassigned) => Trent Lloyd (lathiat) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+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 1752819] Re: jackd crashed with SIGABRT in std::terminate()
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1752819 Title: jackd crashed with SIGABRT in std::terminate() Status in jackd2 package in Ubuntu: Invalid Bug description: Hi, as I first installed UBUNTU BIONIC with some problems on drivers etc. such as print samsung recognised but not working,Asus xonar not stilli recognised,and AMD video Radeon H4670 not recognised. Then I reinstalled UBUNT 17 lts with the same problems. So what's still wrong? What should I remove or install? Thank You all for your attention. BST RGDS Angelo ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: jackd2 1.9.12~dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 2 10:01:44 2018 ExecutablePath: /usr/bin/jackd InstallationDate: Installed on 2018-02-14 (15 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206) JournalErrors: -- Logs begin at Wed 2018-02-14 14:45:05 CET, end at Fri 2018-03-02 10:04:45 CET. -- mar 02 09:53:48 username-desktop kernel: radeon :01:00.0: Invalid PCI ROM header signature: expecting 0xaa55, got 0x mar 02 09:54:09 username-desktop pulseaudio[1067]: [autospawn] core-util.c: Home directory not accessible: Permesso negato mar 02 09:54:09 username-desktop pulseaudio[1067]: [pulseaudio] main.c: Failed to acquire autospawn lock mar 02 09:54:44 username-desktop pulseaudio[1376]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) ProcCmdline: /usr/bin/jackd -T -ndefault -dalsa -dhw:0 -r44100 -p1024 -n2 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: jackd2 StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libjackserver.so.0 Title: jackd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1752819/+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 1755949] Re: process-cpp FTBFS in bionic
Removing packages from bionic: process-cpp 3.0.1-0ubuntu5 in bionic libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic amd64 libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic arm64 libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic armhf libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic i386 libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic ppc64el libprocess-cpp-dev 3.0.1-0ubuntu5 in bionic s390x libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic amd64 libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic arm64 libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic armhf libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic i386 libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic ppc64el libprocess-cpp-doc 3.0.1-0ubuntu5 in bionic s390x libprocess-cpp3 3.0.1-0ubuntu5 in bionic amd64 libprocess-cpp3 3.0.1-0ubuntu5 in bionic arm64 libprocess-cpp3 3.0.1-0ubuntu5 in bionic armhf libprocess-cpp3 3.0.1-0ubuntu5 in bionic i386 libprocess-cpp3 3.0.1-0ubuntu5 in bionic ppc64el libprocess-cpp3 3.0.1-0ubuntu5 in bionic s390x Comment: Obsoleted product, FTBFS; LP: #1747128 1 package successfully removed. Removing packages from bionic-proposed: process-cpp 3.0.1-0ubuntu6 in bionic Comment: Obsoleted product, FTBFS; LP: #1747128 1 package successfully removed. ** Changed in: process-cpp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1755949 Title: process-cpp FTBFS in bionic Status in dbus-cpp package in Ubuntu: Fix Released Status in process-cpp package in Ubuntu: Fix Released Bug description: process-cpp fails to build with an inscrutable error from cmake about failing to find pthreads: Determining if the function pthread_create exists in the pthreads failed with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_b3690/fast" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make CMakeFiles/cmTC_b3690.dir/build make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -o CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.9/Modules/CheckFunctionExists.c Linking C executable cmTC_b3690 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -o cmTC_b3690 -lpthreads https://launchpad.net/ubuntu/+source/process- cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64 .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz pthreads are certainly supported. They're spelled '-pthread'. I have no idea why cmake is failing to find them, you'd think this is a pretty basic thing; and other cmake-using software doesn't seem to have this problem. Poking around in the CMakeFiles, it appears to be some sort of adverse interaction with gmock. But I don't know why this is or how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+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 1755949] Re: process-cpp FTBFS in bionic
Removing packages from bionic: dbus-cpp 5.0.0+18.04.20171031-1 in bionic dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic amd64 dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic arm64 dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic armhf dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic i386 dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic ppc64el dbus-cpp-bin 5.0.0+18.04.20171031-1 in bionic s390x dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic amd64 dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic arm64 dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic armhf dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic i386 dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic ppc64el dbus-cpp-dev-examples 5.0.0+18.04.20171031-1 in bionic s390x libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic amd64 libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic arm64 libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic armhf libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic i386 libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic ppc64el libdbus-cpp-dev 5.0.0+18.04.20171031-1 in bionic s390x libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic amd64 libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic arm64 libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic armhf libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic i386 libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic ppc64el libdbus-cpp5 5.0.0+18.04.20171031-1 in bionic s390x Comment: Obsoleted product, build-depends on process-cpp which is broken; LP: #1747128 1 package successfully removed. ** Changed in: dbus-cpp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1755949 Title: process-cpp FTBFS in bionic Status in dbus-cpp package in Ubuntu: Fix Released Status in process-cpp package in Ubuntu: Fix Released Bug description: process-cpp fails to build with an inscrutable error from cmake about failing to find pthreads: Determining if the function pthread_create exists in the pthreads failed with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_b3690/fast" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make CMakeFiles/cmTC_b3690.dir/build make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -o CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.9/Modules/CheckFunctionExists.c Linking C executable cmTC_b3690 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -o cmTC_b3690 -lpthreads https://launchpad.net/ubuntu/+source/process- cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64 .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz pthreads are certainly supported. They're spelled '-pthread'. I have no idea why cmake is failing to find them, you'd think this is a pretty basic thing; and other cmake-using software doesn't seem to have this problem. Poking around in the CMakeFiles, it appears to be some sort of adverse interaction with gmock. But I don't know why this is or how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+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 1752417] Re: network-manager doesn't offer IKE VPN connections
Hello Apicultor, You can install network-manager-strongswan and the associated StrongSwan suite of utilities if you want to use IKEv2 VPNs with Network Manager. LT2P requires 17.10 or the upcoming 18.04 LTS for the network-manager- l2tp package: https://launchpad.net/ubuntu/+source/network-manager-l2tp Thanks -- 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/1752417 Title: network-manager doesn't offer IKE VPN connections Status in network-manager package in Ubuntu: Invalid Bug description: network-manager lists only PPTP as an available VPN client connection type (and also offers to import a file). I'd expect L2TP-over-IPSec and IKEv1/IKEv2 options as well. In fact, most major desktop OSes have removed PPTP altogether because it's insecure, and Ubuntu should probably do so in 18.04 as well, at least from the GUI! $ apt list network-manager Llistant… Fet network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat] $ uname -a Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752417/+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 1752417] Re: network-manager doesn't offer IKE VPN connections
** Information type changed from Private Security to Public Security ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- 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/1752417 Title: network-manager doesn't offer IKE VPN connections Status in network-manager package in Ubuntu: Invalid Bug description: network-manager lists only PPTP as an available VPN client connection type (and also offers to import a file). I'd expect L2TP-over-IPSec and IKEv1/IKEv2 options as well. In fact, most major desktop OSes have removed PPTP altogether because it's insecure, and Ubuntu should probably do so in 18.04 as well, at least from the GUI! $ apt list network-manager Llistant… Fet network-manager/bionic,now 1.10.4-1ubuntu2 amd64 [instal·lat] $ uname -a Linux machinename 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1752417/+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 1755949] Re: process-cpp FTBFS in bionic
** No longer affects: mediascanner2 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1755949 Title: process-cpp FTBFS in bionic Status in dbus-cpp package in Ubuntu: New Status in process-cpp package in Ubuntu: New Bug description: process-cpp fails to build with an inscrutable error from cmake about failing to find pthreads: Determining if the function pthread_create exists in the pthreads failed with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_b3690/fast" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make CMakeFiles/cmTC_b3690.dir/build make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -o CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.9/Modules/CheckFunctionExists.c Linking C executable cmTC_b3690 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -o cmTC_b3690 -lpthreads https://launchpad.net/ubuntu/+source/process- cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64 .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz pthreads are certainly supported. They're spelled '-pthread'. I have no idea why cmake is failing to find them, you'd think this is a pretty basic thing; and other cmake-using software doesn't seem to have this problem. Poking around in the CMakeFiles, it appears to be some sort of adverse interaction with gmock. But I don't know why this is or how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+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 1747128] Re: RM: obsolete product
Removing packages from bionic: mediascanner2 0.112+17.04.20170322-0ubuntu1 in bionic libmediascanner-2.0-4 0.112+17.04.20170322-0ubuntu1 in bionic amd64 libmediascanner-2.0-4 0.112+17.04.20170322-0ubuntu1 in bionic arm64 libmediascanner-2.0-4 0.112+17.04.20170322-0ubuntu1 in bionic armhf libmediascanner-2.0-4 0.112+17.04.20170322-0ubuntu1 in bionic i386 libmediascanner-2.0-4 0.112+17.04.20170322-0ubuntu1 in bionic ppc64el libmediascanner-2.0-4 0.112+17.04.20170322-0ubuntu1 in bionic s390x libmediascanner-2.0-dev 0.112+17.04.20170322-0ubuntu1 in bionic amd64 libmediascanner-2.0-dev 0.112+17.04.20170322-0ubuntu1 in bionic arm64 libmediascanner-2.0-dev 0.112+17.04.20170322-0ubuntu1 in bionic armhf libmediascanner-2.0-dev 0.112+17.04.20170322-0ubuntu1 in bionic i386 libmediascanner-2.0-dev 0.112+17.04.20170322-0ubuntu1 in bionic ppc64el libmediascanner-2.0-dev 0.112+17.04.20170322-0ubuntu1 in bionic s390x mediascanner2.0 0.112+17.04.20170322-0ubuntu1 in bionic amd64 mediascanner2.0 0.112+17.04.20170322-0ubuntu1 in bionic arm64 mediascanner2.0 0.112+17.04.20170322-0ubuntu1 in bionic armhf mediascanner2.0 0.112+17.04.20170322-0ubuntu1 in bionic i386 mediascanner2.0 0.112+17.04.20170322-0ubuntu1 in bionic ppc64el mediascanner2.0 0.112+17.04.20170322-0ubuntu1 in bionic s390x qml-module-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic amd64 qml-module-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic arm64 qml-module-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic armhf qml-module-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic i386 qml-module-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic ppc64el qml-module-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic s390x qtdeclarative5-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic amd64 qtdeclarative5-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic arm64 qtdeclarative5-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic armhf qtdeclarative5-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic i386 qtdeclarative5-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic ppc64el qtdeclarative5-ubuntu-mediascanner0.1 0.112+17.04.20170322-0ubuntu1 in bionic s390x Comment: Obsoleted product, build-depends on process-cpp which is broken; LP: #1747128 1 package successfully removed. ** Changed in: mediascanner2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1747128 Title: RM: obsolete product Status in mediascanner2 package in Ubuntu: Fix Released Bug description: mediascanner2 was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:mediascanner2 No reverse dependencies found $ reverse-depends -b src:mediascanner2 No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1747128/+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 1755949] [NEW] process-cpp FTBFS in bionic
Public bug reported: process-cpp fails to build with an inscrutable error from cmake about failing to find pthreads: Determining if the function pthread_create exists in the pthreads failed with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_b3690/fast" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make CMakeFiles/cmTC_b3690.dir/build make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -o CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.9/Modules/CheckFunctionExists.c Linking C executable cmTC_b3690 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -o cmTC_b3690 -lpthreads https://launchpad.net/ubuntu/+source/process- cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64 .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz pthreads are certainly supported. They're spelled '-pthread'. I have no idea why cmake is failing to find them, you'd think this is a pretty basic thing; and other cmake-using software doesn't seem to have this problem. Poking around in the CMakeFiles, it appears to be some sort of adverse interaction with gmock. But I don't know why this is or how to fix it. ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Affects: process-cpp (Ubuntu) Importance: Undecided Status: New ** Also affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Also affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to process-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1755949 Title: process-cpp FTBFS in bionic Status in dbus-cpp package in Ubuntu: New Status in process-cpp package in Ubuntu: New Bug description: process-cpp fails to build with an inscrutable error from cmake about failing to find pthreads: Determining if the function pthread_create exists in the pthreads failed with the following output: Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp Run Build Command:"/usr/bin/make" "cmTC_b3690/fast" make[1]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' /usr/bin/make -f CMakeFiles/cmTC_b3690.dir/build.make CMakeFiles/cmTC_b3690.dir/build make[2]: Entering directory '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp' Building C object CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -o CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -c /usr/share/cmake-3.9/Modules/CheckFunctionExists.c Linking C executable cmTC_b3690 /usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_b3690.dir/link.txt --verbose=1 /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DCHECK_FUNCTION_EXISTS=pthread_create -Wl,-Bsymbolic-functions -Wl,-z,relro -rdynamic CMakeFiles/cmTC_b3690.dir/CheckFunctionExists.c.o -o cmTC_b3690 -lpthreads https://launchpad.net/ubuntu/+source/process- cpp/3.0.1-0ubuntu6/+build/13627287/+files/buildlog_ubuntu-bionic-amd64 .process-cpp_3.0.1-0ubuntu6_BUILDING.txt.gz pthreads are certainly supported. They're spelled '-pthread'. I have no idea why cmake is failing to find them, you'd think this is a pretty basic thing; and other cmake-using software doesn't seem to have this problem. Poking around in the CMakeFiles, it appears to be some sort of adverse interaction with gmock. But I don't know why this is or how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1755949/+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 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is
Is there any chance someone from the desktop team could add a Conflicts: line (or whichever line is most appropriate) to account-plugin-facebook in account-plugins before 18.04 LTS is released, so we could avoid another five years of this bug? :) Please? :) Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1617564 Title: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in One Hundred Papercuts: Confirmed Status in account-plugins package in Ubuntu: Confirmed Status in kaccounts-providers package in Ubuntu: Confirmed Bug description: showing this error when installing kde environment in ubuntu 16.04. it say kaccounts niot installed. so i think it may cause some security issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Aug 27 18:11:18 2016 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-08-25 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1617564/+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 1754888] Re: Menulibre: invalid desktop files detected!
I'd be willing to test the fix, if that is at useful. If so: could you advice me how to go about this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1754888 Title: Menulibre: invalid desktop files detected! Status in vim package in Ubuntu: New Status in xubuntu-default-settings package in Ubuntu: New Bug description: Not sure whether to report this as a bug, but: Running xubuntu 18.04, updated. Linux Xubuntu-18-04 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Menulibre 2.1.5 On starting menulibre I get a warning: Menulibre: invalid desktop files detected! See: http://i.imgur.com/Jqdge9z.png If I click on details, I get: http://i.imgur.com/H7RwsOO.png I think these invalid desktop files are part of the initial installation of menulibre/xubuntu. As a simple end user I do not know what to do with this warning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1754888/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
I just cleaned up my /boot (old kernels and stuff) and Bng! worked like a charm. -- 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/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space Status in initramfs-tools: Confirmed Status in Ubuntu Software Center: Invalid Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+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 592434] Re: ssh -X user@machine hangs when using exit to terminate
Try running the remote X client using dbus-run-session(1), which I have on my FreeBSD build of dbus: $ ssh mybox $ dbus-run-session -- gedit I came across this thread looking for why ssh sessions in which I ran /certain/ X clients would hang the session when I tried to exit. Now that I know it's a dbus issue, I came across a dbus session wrapper program that suits my needs perfectly. Now I can alias those naughty commands while in an ssh session. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/592434 Title: ssh -X user@machine hangs when using exit to terminate Status in D-Bus: Confirmed Status in dbus package in Ubuntu: Fix Released Status in dbus package in Debian: New Bug description: ssh -X user@server hangs when using exit to terminate Steps to reproduce: user@client:~$ ssh -X user@server user@server:~$ gedit At this point gedit from server will run locally. Closing the program and returning to the terminal you run: user@server:~$ exit logout At this point the terminal hangs on the echo logout, but does not return to the client prompt. The action has been consistent when connecting to a server running opensolaris or ubuntu 8.04. The client is using Ubuntu 10.04 and the server is using 8.04, and using default password authentication. As you will see in the video attached I can confirm the issue when using a clean Ubuntu 10.04 as a client and Ubuntu 8.04 as the server, using default password authentication. Workaround -- -When logging out with "exit" and it hangs, press Ctrl-C -If you would like to simply use gedit on another computer use the following command: $ dbus-launch gedit Date: Thu Jun 10 17:34:26 2010 To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/592434/+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 1751006] Re: Journalctl compiled without pattern matching support
pcre2 library is not in Ubuntu Main, and therefore cannot be used, at runtime, by such a core package as systemd. once pcre2 is available in main, and thus has full Ubuntu Security support, I will be able to enable pattern matching support. ** Also affects: pcre2 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Journalctl compiled without pattern matching support + Journalctl compiled without pattern matching support, pcre2 is not in main ** No longer affects: systemd (Ubuntu Bionic) ** No longer affects: pcre2 (Ubuntu Bionic) ** Changed in: systemd (Ubuntu) Milestone: ubuntu-18.03 => later ** Changed in: systemd (Ubuntu) Importance: High => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751006 Title: Journalctl compiled without pattern matching support, pcre2 is not in main Status in pcre2 package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: Please add pattern matching support to journalctl. At the moment, the -g (--grep) option as described in the man page doesn't work: ╰─▶ journalctl --grep=xhci-hcd Compiled without pattern matching support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre2/+bug/1751006/+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 1755885] Re: Night Light won't turn on after start on display #1
Reload and the workaround didn't work this time. And mirroring screen worked. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755885 Title: Night Light won't turn on after start on display #1 Status in xorg package in Ubuntu: New Bug description: I have two displays and have Night Light mode enabled with Sunset to Sunrise setting (tried to change it into Manual, but this didn't make any difference). It was perfectly OK some time before, but now only display #2 is started with the Night Light mode switched on. I can work around it: go to the Display Settings, try to switch into non-native mode for Display #1 and it switched into it with Night Light enabled. Then choose not to keep settings and it returns into native resolution with Night Light on. Not all changes help to switch the mode on though. For instance, mirroring screen doesn't switch it on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Mar 14 21:31:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed nvidia, 390.42, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5] InstallationDate: Installed on 2018-02-05 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-K/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1755885/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
** Also affects: fonts-hack (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-hack package in Ubuntu: New Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 1718771] Re: Incorrect handling of link-local IPv6 DNS servers
Trying to reproduce this error: I did: $ lxc launch ubuntu-daily:artful $ lxc exec relaxed-fly bash Edited /run/systemd/network/10-netplan-eth0.network to become: [Match] Name=eth0 [Network] DHCP=ipv4 DNS=fe80::307e:12ff:fec4:90ba [DHCP] UseMTU=true RouteMetric=100 UseDNS=no where fe80... address is the right address for the lxd host provided dnsmasq. Then I restarted everything: $ sudo systemctl restart systemd-networkd systemd-resolved $ systemd-resolve --flush-caches $ ip link set dev eth0 down $ ip link set dev eth0 up # systemd-resolve --status eth0 Link 28 (eth0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: fe80::307e:12ff:fec4:90ba DNS Domain: lxd # systemd-resolve google.com google.com: 216.58.204.46%eth0 2a00:1450:4009:80d::200e%eth0 -- Information acquired via protocol DNS in 26.2ms. -- Data is authenticated: no # host google.com google.com has address 216.58.204.46 google.com has IPv6 address 2a00:1450:4009:80d::200e google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. Looks like a correct and valid responses to me. This is with 234-2ubuntu12.1 Seems like it works correctly. I do wonder, if the bug here is that systemd-resolved is not up yet, and is not responding on dbus and/or over 127.0.0.53 at the point in time? I.e. https://bugs.launchpad.net/ubuntu/artful/+source/systemd/+bug/1734167 which is currently awaiting verification. I'll try to revert the docker.io upload you did locally; and rerun all of these tests again; to see if i can make this work again. ** Changed in: systemd (Ubuntu) Status: Confirmed => Incomplete ** Changed in: systemd (Ubuntu Artful) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1718771 Title: Incorrect handling of link-local IPv6 DNS servers Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Artful: Incomplete Bug description: We've recently seen odd looking DNS failures on autopkgtest: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/d/docker.io/20170921_065231_181b8@/log.gz This shows a fe80:: link-local IPv6 address as one of the DNS servers on the interface. That's because dnsmasq includes both the link-local and global addresses of its DNS server in the router advertisement. systemd-networkd appears to pick that up and send it to resolved, which includes it in its config but apparently doesn't know how to actually query it, leading to the failure above. This is racy because once DHCPv4 completes, the resolved config will then work properly again. I've confirmed that dnsmasq properly answers on all addresses: http://paste.ubuntu.com/25588197/ I've uploaded a workaround for this issue as part of the docker.io package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718771/+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 1755885] [NEW] Night Light won't turn on after start on display #1
Public bug reported: I have two displays and have Night Light mode enabled with Sunset to Sunrise setting (tried to change it into Manual, but this didn't make any difference). It was perfectly OK some time before, but now only display #2 is started with the Night Light mode switched on. I can work around it: go to the Display Settings, try to switch into non-native mode for Display #1 and it switched into it with Night Light enabled. Then choose not to keep settings and it returns into native resolution with Night Light on. Not all changes help to switch the mode on though. For instance, mirroring screen doesn't switch it on. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.42 Sat Mar 3 04:10:22 PST 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-5ubuntu1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Mar 14 21:31:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-10-generic, x86_64: installed nvidia, 390.42, 4.15.0-10-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e5] InstallationDate: Installed on 2018-02-05 (37 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=68661197-00b4-4652-9c8f-2ef606012d2d ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-K/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd03/17/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-K/USB3.1:rvrRevX.0x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic has-workaround regression reproducible ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755885 Title: Night Light won't turn on after start on display #1 Status in xorg package in Ubuntu: New Bug description: I have two displays and have Night Light mode enabled with Sunset to Sunrise setting (tried to change it into Manual, but this didn't make any difference). It was perfectly OK some time before, but now only display #2 is started with the Night Light mode switched on. I can work around it: go to the Display Settings, try to switch into non-native mode for Display #1 and it switched into it with Night Light enabled. Then choose not to keep settings and it returns into native resolution with Night Light on. Not all changes help to switch the mode on though. For i
[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
I cca two days the same problem. Two Core CPU's all time on 60% and nm- applet not shown on panel: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 459 root 20 0 45500868680 S 62,2 0,0 53:20.26 systemd-logind 25499 root 20 0 25708 1344 1120 R 58,2 0,0 1:55.28 cgmanager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754836] Re: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service
Don't appear to be able to find the appropriate log in Ubuntu - however grepping journalctl there for blue* gives me: journalctl |grep blue* Mar 14 17:51:27 ubuntu NetworkManager[985]: [1521049887.5999] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Mar 14 17:51:33 ubuntu dbus-daemon[949]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.36' (uid=999 pid=1532 comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") Mar 14 17:51:58 ubuntu dbus-daemon[949]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Mar 14 17:51:58 ubuntu pulseaudio[1532]: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1754836 Title: Xubuntu: ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms) Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Xubuntu seeing long first time boot to desktop from login. Possibly also causing the long time to desktop from try/install livesession dialogue. Including xsession-errors from the first time boot on installed system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 11:32:59 2018 InstallationDate: Installed on 2018-03-08 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) InterestingModules: bluetooth MachineType: NOVATECH LTD MBB-44608 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=8d9f054a-4c7a-481f-966e-fc2cd6f51aca ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: 7383241-001 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnMBB-44608:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: MBB-44608 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD hciconfig: rfkill: syslog: Mar 10 11:30:16 test-MBB-44608 NetworkManager[679]: [1520681416.8951] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blueman/+bug/1754836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755719] Re: Please sync qt5-default from debian experimental
** Package changed: ubuntu => qtbase-opensource-src (Ubuntu) ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1755719 Title: Please sync qt5-default from debian experimental Status in qtbase-opensource-src package in Ubuntu: New Bug description: I mean of course please sync all qt5 packages to the version of experimental. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1755719/+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 1755719] [NEW] Please sync qt5-default from debian experimental
You have been subscribed to a public bug: I mean of course please sync all qt5 packages to the version of experimental. ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- Please sync qt5-default from debian experimental https://bugs.launchpad.net/bugs/1755719 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638345] Re: avahi-daemon crashes multiple times an hour
Why was this task "unassigned"? This issue still affects me and many others. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1638345 Title: avahi-daemon crashes multiple times an hour Status in avahi package in Ubuntu: Confirmed Bug description: Ever since upgrading to 16.10, avahi-daemon crashes multiple times an hour, leading to the prompt to report the issue to Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 1 10:48:35 2016 InstallationDate: Installed on 2016-07-08 (115 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: avahi UpgradeStatus: Upgraded to yakkety on 2016-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1638345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest
Fix will conme with the upcoming CUPS 2.2.7 bug fix release which we will upload to Bionic. ** Changed in: cups (Ubuntu Bionic) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1750514 Title: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest Status in CUPS: Fix Released Status in cups package in Ubuntu: Triaged Status in cups source package in Bionic: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups. This problem was most recently seen with package version 2.2.6-5, the problem page at https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1750514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755202] Re: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10)
** Description changed: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. + Hardware Info + Lenovo Z470 - Core i5 Second Gen + I used external wifi adapter - Card King http://a.co/gMrHzZQ (RT3072 Chipset) + + #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status - - journalctl log is pasted here. - https://pastebin.com/Ki3R48pw + Update Journalctl with network-manager log + First I Connect my wifi named "blizzart" without using spoof address. Connected and works fine. + After 2 minutes later, I disconnected. + And then add spoof address and try to connect again. + But It is still trying to connect. You can see in the log. + https://pastebin.com/vmFMefih -- 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/1755202 Title: Clone Mac Address Function On Default Wifi Setting Does Not Work (Ubuntu 17.10) Status in network-manager package in Ubuntu: Incomplete Bug description: I am Just Using Ubuntu 17.10. My Uname -a Result -> Linux user 4.13.0-36-generic #40-Ubuntu SMP Fri Feb 16 20:07:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux. Before Using Ubuntu 17.10, I was on fedora 26. I notice that there is also (MAC Address Randomization issue). I can fixed it and can use default mac address spoofing function from wifi setting -> Network Profile Setting (*) -> Identity -> Cloned Address -> And Add mac address to spoof for particular network. This Default mac address spoof function is very useful for me. Clearly, I doesn't mean (MAC Address Randomization issue) https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513 Now I have a trouble with this feature (default mac spoffing). I can connect Wifi-s with great signal easily without using cloned address function. But when I added spoof address to setting, the wifi-s cannot be connected. I tried two wifi-s from near me which can connect on fedora 26. One is open type network and the other is WPA Enterprise network. If this function doesn't work for anyone, this must be a bug. If it is a bug, hope it will fix it next release. Please, Don't Hesitate to ask more information. I really want to help to fix bug. Hardware Info Lenovo Z470 - Core i5 Second Gen I used external wifi adapter - Card King http://a.co/gMrHzZQ (RT3072 Chipset) #info lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 network-manager: Installed: 1.8.4-1ubuntu3 Candidate: 1.8.4-1ubuntu3 Version table: *** 1.8.4-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status Update Journalctl with network-manager log First I Connect my wifi named "blizzart" without using spoof address. Connected and works fine. After 2 minutes later, I disconnected. And then add spoof address and try to connect again. But It is still trying to connect. You can see in the log. https://pastebin.com/vmFMefih To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755202/+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 1722101] Re: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su config
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1722101 Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in cups package in Ubuntu: Confirmed Bug description: Since some weeks ago, I got problems with "cups-daemon" updating, my system say: the file is has not found and I don't know what to do. Please help me. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic i686 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: i386 CupsErrorLog: Date: Thu Oct 5 18:09:33 2017 DpkgHistoryLog: Start-Date: 2017-10-05 18:09:02 Commandline: apt-get -f install Requested-By: alex (1000) Upgrade: libcups2:i386 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-bsd:i386 (2.1.3-4, 2.1.3-4ubuntu0.3), cups:i386 (2.1.3-4, 2.1.3-4ubuntu0.3), cups-client:i386 (2.1.3-4, 2.1.3-4ubuntu0.3) ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2016-11-01 (341 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Hewlett-Packard Compaq Presario C700 Notebook PC Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=ee27e26c-dc63-4754-a015-5bbfe542d39d ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic root=UUID=ee27e26c-dc63-4754-a015-5bbfe542d39d ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.34 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 30D9 dmi.board.vendor: Hewlett-Packard dmi.board.version: 83.21 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.34:bd09/25/2008:svnHewlett-Packard:pnCompaqPresarioC700NotebookPC:pvrF.34:rvnHewlett-Packard:rn30D9:rvr83.21:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: Compaq Presario C700 Notebook PC dmi.product.version: F.34 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1722101/+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 1755859] [NEW] idk
Public bug reported: idk ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 14 19:19:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1840] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-03-09 (4 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1840 dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.27:bd09/07/2016:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr07921020561610100:rvnHewlett-Packard:rn1840:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.version: 07921020561610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91+git1803091830.5236de~oibaf~x version.libgl1-mesa-dri: libgl1-mesa-dri 18.1~git1803121343.e76cf1~oibaf~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.1~git1803121343.e76cf1~oibaf~x version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755859 Title: idk Status in xorg package in Ubuntu: New Bug description: idk ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Mar 14 19:19:35 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-36-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1840] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-03-09 (4 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1840 dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.27:bd09/07/2016:svn
[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor
I'm able to interact with the system normally using the ctrl-alt-F3 terminal, although none of the methods listed in https://askubuntu.com/questions/455301/how-to-restart-gnome-shell-after- it-became-unresponsive-freeze/496999 properly restart gnome-shell. It seems to be related to graphics. -- 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/1752145 Title: system freeze after full screen video viewing with Xorg on ultrawide monitor Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: 1. open a video (either youtube or totem) 2. put it in full screen. 3. wait Eventually (within minutes) the system will freeze in one of 2 ways. 1. There will be only blackness with no response ( even unresponsive). 2. There will be snow that shifts with keyboard and mouse interaction (see photo). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 19:08:13 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'" InstallationDate: Installed on 2018-01-05 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752145/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
After killing and restarting the keyring which fixed Network Manager, then Chromium developed a slow start problem caused by gnome-keyring. smm@laptop ~ $ chromium-browser --enable-logging=stderr ATTENTION: default value of option force_s3tc_enable overridden by environment. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [7981:7981:0314/102437.107901:WARNING:password_store_factory.cc(241)] Using basic (unencrypted) store for password storage. See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_password_storage.md for more information about password storage options. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Every time I turn around, I have a no failure related to gnome-keyring. After having Chromium running for a few minutes it hangs again for a minute or so with the same error message: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Keyring may end up making Chromium unusable. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
Comment #20 appears to recommend filing a deliberate duplicate: > Please open your own report if you are affected. One such duplicate is Bug #1617630. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in at-spi: Invalid Status in at-spi2-core package in Ubuntu: Invalid Status in gnome-session package in Ubuntu: Invalid Status in at-spi2-core package in Debian: Invalid Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+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 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
I even encountered this bug when I tried to report it. $ ubuntu-bug at-spi2-core ** (apport-gtk:): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-##: Connection refused -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1617630] Re: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -*
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: at-spi2-core (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1617630 Title: Mousepad show the warning Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus -* Status in at-spi2-core package in Ubuntu: Confirmed Bug description: When I start mousepad in a terminal, I have this warning : ** (mousepad:25021): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-5pX3Lo3SAH: Connexion refusée When I start it with GKSU, the warning is not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1617630/+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 1689825] Re: gnome-keyring not unlocked on xenial when dbus-user-session is installed
Running "chromium-browser --enable-logging=stderr" results in: $ chromium-browser --enable-logging=stderr ATTENTION: default value of option force_s3tc_enable overridden by environment. I'm also running the gnome-keyring-daemon in the foreground and see this message: ** (gnome-keyring-daemon:31165): WARNING **: asked to register item /org/freedesktop/secrets/collection/login/12, but it's already registered ** Message: The Secret Service was already initialized Chromium starts up quickly, but network manager can't access the keyring and hangs for a minute or two before it gives up when I try to connect to a VPN. Then it prompts me for the passwords, as it was unable to retrieve them from gnome-keyring. Killing and restarting the daemon fixes the problem. Every night I suspend my laptop when I go home and find the deamon is hung again the next morning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on xenial when dbus-user-session is installed Status in chromium-browser package in Ubuntu: Invalid Status in dbus package in Ubuntu: Triaged Status in flatpak package in Ubuntu: Fix Released Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+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 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor
it's likely a kernel bug if the whole system freezes, so maybe try newer/older kernels: http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- 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/1752145 Title: system freeze after full screen video viewing with Xorg on ultrawide monitor Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: 1. open a video (either youtube or totem) 2. put it in full screen. 3. wait Eventually (within minutes) the system will freeze in one of 2 ways. 1. There will be only blackness with no response ( even unresponsive). 2. There will be snow that shifts with keyboard and mouse interaction (see photo). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 19:08:13 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'" InstallationDate: Installed on 2018-01-05 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs
Initial comments from the email:- a) There is some confusion over "metadata_csum" with/without "64bit". -- Those who have 'reverted' are usually reverting BOTH flags [as I've done some places], not just metadata_csum. My understanding is 64bit is of no benefit except support >16TB fs and to strengthen metadata_csum's [if used, which help notice dodgy disks in theory.]. b) The business of including e2fsprogs-1.44.0 in 18.04 at tytso's request [NON-default extra feature support may benefit Samba users etc. later] is not addressed. c) Its' worth pointing-out explicitly e2fsprogs only enabled 64bit,metadata_csum 'by default' for 'everybody' within last few weeks, Debian change was as-you-rightly-quote. d) Considering the above, also think outside the ubuntu-box! What do canonical's customers/partners expect compatibility-wise with other non- ubuntu systems, virtualizers/ISCSI-hosts/etc (e2fsprogs 1.42 still very common!), let alone "backports to ubuntu LTS versions" only?. e) My understanding from TJ in IRC is he's started doing some tests on some datacentre cases, there are particular issues with things like ISCSI hosts, the host system needs to fsck guest-FS and break otherwise!. HOPEFULLY this will appear soon and can be added to the mail-discussion. I can try to join email/post directly to mail if appropriate/helpful. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1755675] Re: Ubuntu 17.10 OpenVPN DNS Leaks
** Package changed: ubuntu => network-manager (Ubuntu) ** Tags added: artful -- 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/1755675 Title: Ubuntu 17.10 OpenVPN DNS Leaks Status in network-manager package in Ubuntu: New Bug description: On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager and OpenVPN, that DNS leaks from the Router or ISP, instead of only being tunneled from the VPN... I have spent hours playing with this, it's beyond absurd, the amount of time and effort needed to try and resolve something that should be working out the box! This is not LFS, or Slackware, in fact Slackware is simpler and easier to make this work in less then 5 mins! Seriously this has been an ongoing issue for ages/years in Ubuntu, and the end-users typically for Ubuntu are inexperienced users, again, the only thing end-users should have to do is install the correct OpenVPN packages, configure OpenVPN in the NetworkManager and it works, but it doesn't! While Canonical works on trying to resolve this, can someone PLEASE tell me a simple way in which to prevent DNS leaks while using OpenVPN through the NetworkManager? THANKS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1755675/+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 1755675] [NEW] Ubuntu 17.10 OpenVPN DNS Leaks
You have been subscribed to a public bug: On Ubuntu 17.10 x64 I have noticed that when using the NetworkManager and OpenVPN, that DNS leaks from the Router or ISP, instead of only being tunneled from the VPN... I have spent hours playing with this, it's beyond absurd, the amount of time and effort needed to try and resolve something that should be working out the box! This is not LFS, or Slackware, in fact Slackware is simpler and easier to make this work in less then 5 mins! Seriously this has been an ongoing issue for ages/years in Ubuntu, and the end-users typically for Ubuntu are inexperienced users, again, the only thing end-users should have to do is install the correct OpenVPN packages, configure OpenVPN in the NetworkManager and it works, but it doesn't! While Canonical works on trying to resolve this, can someone PLEASE tell me a simple way in which to prevent DNS leaks while using OpenVPN through the NetworkManager? THANKS ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 17.10 OpenVPN DNS Leaks https://bugs.launchpad.net/bugs/1755675 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1601997] Re: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs
I posted to the mailing list about this: https://lists.ubuntu.com/archives/ubuntu-devel/2018-March/040230.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1601997 Title: Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is incompatible with older (LTS) e2fsprogs Status in e2fsprogs package in Ubuntu: Triaged Bug description: Ubuntu 16.10 installer sets metadata_csum option on ext4 partition which is incompatible with other LTS Ubuntu versions (12.04 LTS, 14.04 LTS, 16.04 LTS). Steps to reproduce: 1. Download Ubuntu 16.10 installation media. 2. Install Ubuntu. 3. Try to do fsck -fy /dev/sdX1 from other supported Ubuntu distro. Expected results: User can check and fix errors on ext4 filesystem, created on Ubuntu 16.10. Actual results: User can not check and fix errors on ext4 filesystem because of lack of 'metadata_csum' option in previous LTS Ubuntu versions. The only one working solution was to scan from 16.10 live install media. Note: it is known, that Dan Watkins disabled metadata_csum when creating ext4 filesystems ( see http://bazaar.launchpad.net/~daniel-thewatkins/maas-images/fix-yakkety-builds/revision/305 ). It is good solution. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: e2fsprogs 1.43.1-1 ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13 Uname: Linux 4.4.0-30-generic i686 ApportVersion: 2.20.2-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Mon Jul 11 23:42:49 2016 SourcePackage: e2fsprogs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1601997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin
Just tested clean installation of Xubuntu. It does not affected by this bug. But `sudo apt-get install xubuntu-desktop` is affected. Below is comparison of `dpkg -l` from mini.iso and from Xubuntu beta-1 (formatted as patch): --- /tmp/xubuntu/mini_dpkg_-l_installed +++ /tmp/xubuntu/xubuntu_dpkg_-l_installed -ii activity-log-manager 0.9.7-0ubuntu26 -ii apg 2.2.3.dfsg.1-5 +ii chromium-codecs-ffmpeg-extra 65.0.3325.146-0ubuntu1 -ii cracklib-runtime 2.9.2-5build1 -ii dconf-cli 0.26.0-2 -ii evolution-data-server 3.28.0-1ubuntu1 -ii evolution-data-server-common 3.28.0-1ubuntu1 +ii firefox-locale-en 57.0.1+build2-0ubuntu1 -ii fonts-sipa-arundina 0.2.2-1 -ii gconf-service 3.2.6-4ubuntu1 -ii gconf-service-backend 3.2.6-4ubuntu1 -ii gconf2 3.2.6-4ubuntu1 -ii gconf2-common 3.2.6-4ubuntu1 -ii geoclue 0.12.99-4ubuntu2 -ii geoclue-2.0 2.4.7-1ubuntu1 -ii geoclue-ubuntu-geoip 1.0.2+18.04.20180223-0ubuntu1 -ii gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu1 -ii gkbd-capplet 3.26.0-3 -ii gnome-bluetooth 3.27.90-1 -ii gnome-control-center 1:3.27.92-1ubuntu1 -ii gnome-control-center-data 1:3.27.92-1ubuntu1 -ii gnome-control-center-faces 1:3.27.92-1ubuntu1 -ii gnome-online-accounts 3.27.92-1 -ii gnome-power-manager 3.26.0-1 -ii gnome-screensaver 3.6.1-8ubuntu3 -ii gnome-session-bin 3.27.91-0ubuntu4 -ii gnome-settings-daemon 3.27.92-0ubuntu1 -ii gnome-settings-daemon-schemas 3.27.92-0ubuntu1 -ii gnome-user-docs 3.26.2.1-0ubuntu1 +ii gnupg1 1.4.22-3ubuntu2 +ii gnupg1-l10n 1.4.22-3ubuntu2 -ii gsettings-ubuntu-schemas 0.0.7+17.10.20170922-0ubuntu1 -ii gstreamer1.0-clutter-3.0:amd64 3.0.24-2 +ii gstreamer1.0-fluendo-mp3:amd64 0.10.32.debian-1 +ii gstreamer1.0-plugins-ugly:amd64 1.13.1-1 +ii gstreamer1.0-vaapi:amd64 1.13.1-1ubuntu1 +ii hyphen-en-us 2.8.8-5 -ii ibus 1.5.17-3ubuntu1 -ii ibus-gtk:amd64 1.5.17-3ubuntu1 -ii ibus-gtk3:amd64 1.5.17-3ubuntu1 -ii iio-sensor-proxy 2.4-2 -ii indicator-applet 12.10.2+17.10.20170425-0ubuntu1 -ii indicator-application 12.10.1+17.04.20161201-0ubuntu1 -ii indicator-bluetooth 0.0.6+17.10.20170605-0ubuntu3 -ii indicator-datetime 15.10+17.10.20170829.2-0ubuntu3 -ii indicator-keyboard 0.0.0+18.04.20180216-0ubuntu1 -ii indicator-power 12.10.6+17.10.20170829.1-0ubuntu3 -ii indicator-session 17.3.20+17.10.20171006-0ubuntu1 -ii indicator-sound 12.10.2+17.10.20170829.1-0ubuntu1 -ii installation-report 2.62ubuntu1 +ii liba52-0.7.4:amd64 0.7.4-19 -ii libaccounts-glib0:amd64 1.23+17.04.20161104-0ubuntu1 -ii libbonobo2-0:amd64 2.32.1-3 -ii libbonobo2-common 2.32.1-3 -ii libbonoboui2-0:amd64 2.24.5-4 -ii libbonoboui2-common 2.24.5-4 -ii libcamel-1.2-61:amd64 3.28.0-1ubuntu1 -ii libcanberra-pulse:amd64 0.30-5ubuntu1 -ii libcheese-gtk25:amd64 3.26.0-4ubuntu2 -ii libcolord-gtk1:amd64 0.1.26-2 -ii libcrack2:amd64 2.9.2-5build1 +ii libcurl3:amd64 7.58.0-2ubuntu2 -ii libcurl4:amd64 7.58.0-2ubuntu2 +ii libdvdnav4:amd64 6.0.0-1 +ii libdvdread4:amd64 6.0.0-1 -ii libebackend-1.2-10:amd64 3.28.0-1ubuntu1 -ii libebook-1.2-19:amd64 3.28.0-1ubuntu1 -ii libebook-contacts-1.2-2:amd64 3.28.0-1ubuntu1 -ii libecal-1.2-19:amd64 3.28.0-1ubuntu1 -ii libedata-book-1.2-25:amd64 3.28.0-1ubuntu1 -ii libedata-cal-1.2-28:amd64 3.28.0-1ubuntu1 -ii libedataserver-1.2-23:amd64 3.28.0-1ubuntu1 -ii libfcitx-config4:amd64 1:4.2.9.6-1 -ii libfcitx-gclient1:amd64 1:4.2.9.6-1 -ii libfcitx-utils0:amd64 1:4.2.9.6-1 -ii libgconf-2-4:amd64 3.2.6-4ubuntu1 -ii libgeoclue-2-0:amd64 2.4.7-1ubuntu1 -ii libgeoclue0:amd64 0.12.99-4ubuntu2 -ii libgeocode-glib0:amd64 3.25.4.1-4 -ii libgeonames-common 0.2+17.04.20170220-0ubuntu1 -ii libgeonames0:amd64 0.2+17.04.20170220-0ubuntu1 -ii libglade2-0:amd64 1:2.6.4-2 -ii libgles2:amd64 1.0.0-2ubuntu2 -ii libgmime-3.0-0:amd64 3.2.0-1 -ii libgnome-2-0:amd64 2.32.1-6 -ii libgnome-bluetooth13:amd64 3.27.90-1 -ii libgnome-keyring-common 3.12.0-1build1 -ii libgnome-keyring0:amd64 3.12.0-1build1 -ii libgnome2-common 2.32.1-6 -ii libgnomecanvas2-0:amd64 2.30.3-3 -ii libgnomecanvas2-common 2.30.3-3 -ii libgnomekbd-common 3.26.0-3 -ii libgnomekbd8:amd64 3.26.0-3 -ii libgnomeui-0:amd64 2.24.5-3.2 -ii libgnomeui-common 2.24.5-3.2 -ii libgnomevfs2-0:amd64 1:2.24.4-6.1ubuntu2 -ii libgnomevfs2-common 1:2.24.4-6.1ubuntu2 -ii libgoa-backend-1.0-1:amd64 3.27.92-1 -ii libgrilo-0.3-0:amd64 0.3.4-1 +ii libgstreamer-plugins-bad1.0-0:amd64 1.13.1-1ubuntu1 -ii libgtop-2.0-11:amd64 2.38.0-2 -ii libgtop2-common 2.38.0-2 -ii libgweather-3-15:amd64 3.28.0-1 -ii libgweather-common 3.28.0-1 -ii libibus-1.0-5:amd64 1.5.17-3ubuntu1 +ii libisl15:amd64 0.18-1ubuntu1 -ii libjpeg-turbo-progs 1.5.2-0ubuntu5 +ii libmpeg2-4:amd64 0.5.1-8 -ii libnet-libidn-perl 0.12.ds-2build4 -ii libnm-glib4:amd64 1.10.4-1ubuntu2 -ii libnm-gtk0:amd64 1.8.10-2ubuntu1 -ii libnm-util2:amd64 1.10.4-1ubuntu2 -ii libnss-myhostname:amd64 237-3ubuntu4 +ii libopencore-amrnb0:amd64 0.1.3-2.1 +ii libopencore-amrwb0:amd64 0.1.3-2.1 -ii liborbit-2-0:amd64 1:2.14.19-4 -ii libpanel-applet3 1:3.26.0-1ubuntu5 -ii libphonenumber7:amd64 7.1.0-5ubuntu5 -ii libprotobuf10:amd64 3.0.0-9ubuntu5 -ii lib
[Touch-packages] [Bug 1752145] Re: system freeze after full screen video viewing with Xorg on ultrawide monitor
I tried using Unity instead of gnome-shell and am experiencing the same problem. Does this mean it's not a problem with mutter? What is worse, is that this problems seems to crop up every day or so during work. In other words, everything will freeze except for the mouse even if I've never watched a video. Could you please tell me details on how to get the best debug information for you? -- 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/1752145 Title: system freeze after full screen video viewing with Xorg on ultrawide monitor Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: 1. open a video (either youtube or totem) 2. put it in full screen. 3. wait Eventually (within minutes) the system will freeze in one of 2 ways. 1. There will be only blackness with no response ( even unresponsive). 2. There will be snow that shifts with keyboard and mouse interaction (see photo). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 27 19:08:13 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'enabled-extensions' b"['workspace-g...@mathematical.coffee.gmail.com', 'alt-tab-worksp...@kwalo.net', 'system-moni...@paradoxxx.zero.gmail.com', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'ubuntu-d...@ubuntu.com', 'ubuntu-appindicat...@ubuntu.com']" b'org.gnome.shell' b'enable-hot-corners' b'true' b'org.gnome.shell' b'favorite-apps' b"['googleinbox.desktop', 'googlecalendar.desktop', 'org.gnome.Nautilus.desktop', 'firefox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'monospace-font-name' b"'Ubuntu Mono 11'" InstallationDate: Installed on 2018-01-05 (53 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2018-01-05 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752145/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
Correction: "Hack Bold" renders correctly, "Hack Regular" doesn't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 1755806] Re: X crashed, maybe related to touchpad
*** This bug is a duplicate of bug 1753735 *** https://bugs.launchpad.net/bugs/1753735 Looks like the backtrace isn't in the attached logs, let me fix that. Mar 14 09:54:21 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) event5 - SynPS/2 Synaptics TouchPad: kernel bug: Touch jump detected and discarded. Mar 14 09:54:21 nsnx /usr/lib/gdm3/gdm-x-session[5239]: See https://wayland.freedesktop.org/libinput/doc/1.10.1/touchpad_jumping_cursor.html for details Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: Xorg: ../src/evdev-mt-touchpad-tap.c:1028: tp_tap_handle_state: Assertion `tp->tap.nfingers_down >= 1' failed. Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Backtrace: Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d) [0x55ab4d64391d] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 1: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1bc6b9) [0x55ab4d6476b9] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbf1f27f000+0x12890) [0x7fbf1f291890] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xc7) [0x7fbf1eecce97] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x141) [0x7fbf1eece801] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbf1ee8e000+0x3039a) [0x7fbf1eebe39a] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbf1ee8e000+0x30412) [0x7fbf1eebe412] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 7: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0x1d9e3) [0x7fbf1be869e3] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 8: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0x18e17) [0x7fbf1be81e17] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 9: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0x1ad90) [0x7fbf1be83d90] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 10: /usr/lib/x86_64-linux-gnu/libinput.so.10 (0x7fbf1be69000+0xf5e1) [0x7fbf1be785e1] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 11: /usr/lib/x86_64-linux-gnu/libinput.so.10 (libinput_dispatch+0x5f) [0x7fbf1be7460f] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 12: /usr/lib/xorg/modules/input/libinput_drv.so (0x7fbf1c0b8000+0x8988) [0x7fbf1c0c0988] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 13: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1baa93) [0x55ab4d645a93] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 14: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1bd191) [0x55ab4d648191] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 15: /usr/lib/xorg/Xorg (0x55ab4d48b000+0x1ba8de) [0x55ab4d6458de] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 16: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fbf1f27f000+0x76db) [0x7fbf1f2866db] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) 17: /lib/x86_64-linux-gnu/libc.so.6 (clone+0x3f) [0x7fbf1efaf88f] Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: Fatal server error: Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Caught signal 6 (Aborted). Server aborting Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: Please consult the The X.Org Foundation support Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: #011 at http://wiki.x.org Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: for help. Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Please also check the log file at "/home/andreas/.local/share/xorg/Xorg.0.log" for additional information. Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Mar 14 09:54:22 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (II) AIGLX: Suspending AIGLX clients for VT switch Mar 14 09:54:23 nsnx /usr/lib/gdm3/gdm-x-session[5239]: (EE) Server terminated with error (1). Closing log file. Mar 14 09:54:23 nsnx kernel: [30169.675729] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Mar 14 09:54:28 nsnx hexchat.desktop[8618]: hexchat: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Mar 14 09:54:28 nsnx update-notifier[8801]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. ** This bug has been marked a duplicate of private bug 1753735 -- You received this bug notification because you are a member of Ubuntu Touch se
[Touch-packages] [Bug 1755806] [NEW] X crashed, maybe related to touchpad
*** This bug is a duplicate of bug 1753735 *** https://bugs.launchpad.net/bugs/1753735 Public bug reported: Happened twice now. During normal usage, the screen just goes blank and I'm thrown back at the GUI login prompt. Logs show X crashed, have a backtrace, and it looks like it's related to the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Mar 14 09:57:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed root=ZFS=hostname/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET41W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1MET41W(1.26):bd11/09/2017:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 5th dmi.product.name: 20HRCTO1WW dmi.product.version: ThinkPad X1 Carbon 5th dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1755806 Title: X crashed, maybe related to touchpad Status in xorg package in Ubuntu: New Bug description: Happened twice now. During normal usage, the screen just goes blank and I'm thrown back at the GUI login prompt. Logs show X crashed, have a backtrace, and it looks like it's related to the touchpad. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Wed Mar 14 09:57:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 (ThinkPad X1 Carbon 5th Gen) [17aa:224f] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 003: ID 04f2:b5ce Chicony Electronics Co., Ltd Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HRCTO1WW ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic.efi.signed root=ZFS=hostname/ROOT/ubuntu ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1MET41W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HRCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: d
[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
Hofer-Temmel Christoph, I've got the binary packages for the 204-5ubuntu20.25 version from Launchpad itself. The pages for the x86 versions you need are: https://launchpad.net/ubuntu/trusty/i386/libpam-systemd/204-5ubuntu20.25 https://launchpad.net/ubuntu/trusty/i386/libsystemd-daemon0/204-5ubuntu20.25 https://launchpad.net/ubuntu/trusty/i386/systemd-services/204-5ubuntu20.25 Hope it helps, Marcelo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin
** Also affects: xubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: New Status in indicator-datetime package in Ubuntu: New Status in xubuntu-meta package in Ubuntu: New Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754872/+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 299158] Re: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place
My test case: echo -e 'a\u0308a' Correct rendering: äa (That's what I see with: Courier, Cousine, DejaVu Sans Mono, FreeMono, Hack, Monospace) Incorrect rendering: aä (That's what I see with: Andale Mono, Bitstream Vera Sans Mono, Courier 10 Pitch, Courier New, Liberation Mono, Mitra Mono, Nimbus Mono L, Noto Mono, Oxygen Mono, Tlwg Mono, Tlwg Typo, Ubuntu Mono) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+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 299158] Re: Liberation Mono, Droid Sans Mono: Combining diacritics out of place
This is still broken in Ubuntu 18.04 bionic. It's notoriously annoying with text or filenames coming from OSX, which keeps diacritics separate from the character they're combined with, also for characters that have a distinct unicode code point for the combined variant. ** Also affects: ttf-bitstream-vera (Ubuntu) Importance: Undecided Status: New ** Also affects: fonts-noto (Ubuntu) Importance: Undecided Status: New ** Also affects: oxygen-fonts (Ubuntu) Importance: Undecided Status: New ** Also affects: fonts-tlwg (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Liberation Mono, Droid Sans Mono: Combining diacritics out of place + DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/299158 Title: DejaVu, Liberation Mono, Noto Mono, Tlwg Mono, Oxygen Mono, Bitstream Vera Mono: Combining diacritics out of place Status in fonts-dejavu package in Ubuntu: Confirmed Status in fonts-droid package in Ubuntu: Won't Fix Status in fonts-liberation package in Ubuntu: Confirmed Status in fonts-noto package in Ubuntu: New Status in fonts-tlwg package in Ubuntu: New Status in msttcorefonts package in Ubuntu: Won't Fix Status in oxygen-fonts package in Ubuntu: New Status in ttf-bitstream-vera package in Ubuntu: New Bug description: In the Liberation Mono font, combining diacritical marks are drawn over the following character rather than the preceding. According to the Unicode standard since at least version 3.0, chapter 3.6, verse D56, combining characters apply to the preceding base character. However, this font renders them on the following base character. Version info: Ubuntu Intrepid ttf-liberation 1.04~beta2-2 To reproduce: 1. Open gedit. 2. Type the following three code points: U+0061 U+0301 U+0065 (Latin small letter a, Combining acute accent, Latin small letter e). 3. Via Edit|Preferences|Font & Colors|Font, select the Liberation Mono font. Expected: * Two grapheme clusters are displayed: Latin small letter a with acute accent, Latin small letter e. Observed: * The grapheme clusters displayed are: Latin small letter a, Latin small letter e with acute accent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/299158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365874] Re: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming
FWIW, As was discussed, I checked into Grub2 and os-prober in older supported ubuntu (which may have similar incompatibility to e2fsprogs, thereby creating a multibooting issue with 18.04). After experimenting carefully with a 14.04+16.04+18.04 (GA kernels, no HWE specifically) BIOS-style triple boot, can confirm the grub ext4 support is all cross-compatible (14.04 can autodetect and boot 64bit,metadata_csum 18.04 from its' own grub2). However, e2fsprogs is DEFINITELY an issue as above, definitely worth sorting-out whatever-happens to the 18.04 default filesystem options, in my view. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1365874 Title: Ubuntu 12.04 LTS, 14.04 LTS, 16.04 LTS do not support ext4 metadata checksumming Status in e2fsprogs package in Ubuntu: Triaged Bug description: In the Trusty release notes "Metadata checksumming" is listed as one of the tech highlights of kernel 3.13. https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#New_features_in_14.04_LTS However, the userland tools do not support this kernel feature. To the best of my knowledge this will be supported in 1.43, and won't be backported to 1.42. IMHO this is very misleading. It's like a car salesperson sold you a sports car with an V8 engine. After you drove it home, you opened the hood and realized only 6 cylinders are working because 2 of the spark plugs were not included, and you have to buy aftermarket ones. BTW, I've been following the development of e2fsprogs for over a year. 1.43 release has been in limbo for God knows how long :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1365874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746463] Re: apparmor profile load in stacked policy container fails
** Changed in: linux (Ubuntu Artful)
Status: Confirmed => Fix Committed
--
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/1746463
Title:
apparmor profile load in stacked policy container fails
Status in snapd:
Triaged
Status in apparmor package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in linux-gcp package in Ubuntu:
Fix Released
Status in apparmor source package in Xenial:
Won't Fix
Status in linux source package in Xenial:
Invalid
Status in linux-gcp source package in Xenial:
Confirmed
Status in apparmor source package in Artful:
Fix Committed
Status in linux source package in Artful:
Fix Committed
Status in linux-gcp source package in Artful:
Invalid
Status in apparmor source package in Bionic:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux-gcp source package in Bionic:
Fix Released
Bug description:
LXD containers on an artful or bionic host with aa namespaces, should
be able to load the lxc policies. However /lib/apparmor/profile-load
skips that part when running in a container.
aa-status shows 0 policies
/lib/apparmor/profile-load is failing due to
is_container_with_internal_policy() failing
due to
/sys/kernel/security/apparmor/.ns_name being empty which causes
if [ "${ns_name#lxd-*}" = "$ns_name" ] && \
[ "${ns_name#lxc-*}" = "$ns_name" ]; then
return 1
fi
to fail
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1746463/+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 1754872] Re: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settin
Dear Sean! It seems you do not understand bug description. I install `xubuntu-desktop` task-package from mini.iso on 18.04 LTS with `sudo apt-get install xubuntu-desktop`. What is the difference with "a base install of Xubuntu"? What is wrong is this method? Users should be able to install desktop task as they want. Clean installation is not an option for some (or most do not really sure) users. I attach the list of installed packages. I do not have other desktops installed. You should check this again. It may be dependency problem or something similar. ** Attachment added: "dpkg -l output after `sudo apt-get install xubuntu-desktop` on minimal Bionic" https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1754872/+attachment/5079195/+files/dpkg_-l_installed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1754872 Title: gnome-control-center is unusable on xubuntu-desktop, but called from Gear (About this Computer, System Settings) icon, Text Entry Settings, clock (Time & Date Settings) Status in gnome-control-center package in Ubuntu: New Status in indicator-datetime package in Ubuntu: New Bug description: Steps to reproduce: 1. Install `xubuntu-desktop` meta package on 18.04 LTS 2. Login to session 3a. Click on clock indicator on panel, select "Time & Date Settings" 3b. Click on Gear, select "About this Computer" or "System Settings" 3c. Click on keyboard layout indicator, select "Text Entry Settings" Expected results: xfce-oriented control center is opened Actual results: gnome-control-center is opened, but with empty window. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xubuntu-desktop 2.223 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Mar 10 21:10:11 2018 SourcePackage: xubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1754872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303649] Re: systemd-logind spins in cgmanager_ping_sync()
I am having the same issue since this morning (14 march): cgmanager and systemd-logind both using 60-70% of system resources, gui unusable, login via console possible. Looking at /var/log/apt/term.log I see that the update has been installed on 9 march, but did not give any issues until now. Intermediate updates were samba packages yesterday (13 march) evening ... but the system worked after that just fine for the first bootup this morning. Only on the second boot did things go wrong. I tried to apply the fix outlined in 4 steps by Marcelo [4 steps], just for i386 instead of amd64. The problem I have is getting those 3 deb packages. I found the build for libpam 20.25 [libpam20.25], but this one offers no artefacts. On the various package sites only 20.26 is available. Do I have to build on my own? Or is a timeline for an update known, so that I can just upgrade? Cordially, htc [4 steps]: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1303649/comments/20 [libpam20.25]: https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.25/+build/13545611 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1303649 Title: systemd-logind spins in cgmanager_ping_sync() Status in cgmanager package in Ubuntu: Invalid Status in libnih package in Ubuntu: Invalid Status in lxc package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: systemd-logind is consuming a high level of cpu on a continual basis: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 676 root 20 0 43644 2144 1568 R 100.0 0.0 74:43.77 systemd-logind ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: systemd-services 204-5ubuntu17 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 09:09:37 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-04-23 (348 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423) SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2013-11-11 (146 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1303649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551351] Re: dhclient does not renew leases
Major categorization aspects: - this very important core functionality (properly reliable resource management of DHCP leases, also in suspend-to-RAM etc.) **NEVER EVER WORKS** (exclusively suspend-to-RAM use case here, ending up with stale IP address): - this did not work in 12.04LTS - this still did not work after upgrade to 14.04LTS - this STILL did not work after upgrade to 16.04LTS (recently upgraded, i.e. after activity of #12 which says that it DID work there, yet perhaps not suspend-to-RAM) - importance of this bug should be "a lot higher than High" Justification: - messes with/breaks (CORRUPTS!!) environment even *beyond* local system scope (--> inacceptable!!), due to continuing communication via a stale IP address which has long since been re-assigned to other hosts (as can be verified via DNS query) - has been observed in *all* recent LTS releases (which are expected to work fine in large enterpriseish environments??) --> Ubuntu release process is sorely missing reliable verification (persistently executed test case) for this core functionality, to ensure that this is (and keeps!) not causing damage, at least in production (stable) distributions Example to achieve fixing stale IP (renew DHCP lease): nmcli c nmcli c down uuid nmcli c up uuid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1551351 Title: dhclient does not renew leases Status in bind9 package in Ubuntu: Fix Released Status in isc-dhcp package in Ubuntu: Fix Released Status in bind9 source package in Xenial: Fix Released Status in isc-dhcp source package in Xenial: Fix Released Bug description: Release: Xenial I think this only recently started after some bind9 updates triggered a rebuild. When booting dhclient gets started and acquires an IP address, but it does seem to lock up somewhere as it does not renew the lease. In my environment I set the lease time to 5 minutes, so I notice such things rather soon. I looked on the dhcp server side but saw any further dhcp messages come in from the client side. Related bugs: * bug 1551415: systemctl stop networking hang / timeout ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: isc-dhcp-client 4.3.3-5ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3 Uname: Linux 4.4.0-9-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Mon Feb 29 12:32:52 2016 DhclientLeases: SourcePackage: isc-dhcp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1551351/+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 1488620] Re: Add LZ4 support
Apparently the kernel does not yet support zstd for initramfs, but it would be nice if it did. -- 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/1488620 Title: Add LZ4 support Status in initramfs-tools package in Ubuntu: Triaged Bug description: I found that I could enable LZ4 compression for initramfs on my vivid machine by installing liblz4-tool package, adding one line to mkinitramfs and installing a kernel compiled with CONFIG_CRYPTO_LZ4=y. Please include support for (legacy) LZ4. Attached patch includes changes made to the latest version (initramfs- tools_0.120ubuntu3). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1488620/+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 1753776] Re: Graphics corruption (or distortion?) in login animation to Xorg sessions
Reported upstream: https://gitlab.gnome.org/GNOME/mutter/issues/67 -- 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/1753776 Title: Graphics corruption (or distortion?) in login animation to Xorg sessions Status in gnome-shell package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Immediately after login (I enter the password and hit enter) the screen "crumbles" for few seconds, then all becomes normal and the system works fine. I have done apt update+upgrade many times, also with proposed enabled, I have also installed a new ISO (now i'm using the Alpha dated 20180305) but the problem remains. The problem happens with the x11 session but not with wayland. Also problem does not show with different hardware. corrado@corrado-p7-bb-0305:~$ inxi -Fx System:Host: corrado-p7-bb-0305 Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.27.92 (Gtk 3.22.28-1ubuntu3) Distro: Ubuntu Bionic Beaver (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 1018 MHz 2: 3150 MHz 3: 3153 MHz 4: 3081 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.15.0-10-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (1.3% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 4.3G (15%) fs: ext4 dev: /dev/sda7 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 38.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 11 min Memory: 1144.7/7680.8MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.181) inxi: 2.3.56 corrado@corrado-p7-bb-0305:~$ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 6 15:47:50 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2018-03-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=9a36b498-59f5-4a36-81db-3046ff6bdeaa ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.
[Touch-packages] [Bug 1747354] Re: Update bluez to version 5.48 in bionic
the update migrated to bionic proper now, closing the bug ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- 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/1747354 Title: Update bluez to version 5.48 in bionic Status in bluez package in Ubuntu: Fix Released Bug description: Update bluez to version 5.48 in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1733032] Re: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed)
I'll see if I can get a fix for GDK/GTK accepted upstream to clean up that device detection. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed) Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: Since upgrading to 17.10, my mouse pointer is repeatedly and frequently getting moved against my will when I am typing on my laptop keyboard (as opposed to external keyboard) because my hand brushes against the touchpad or even just near its surface. Furthermore, I don't want tap-to-click to be enabled. I want to actually have to push down on the mousepad hard enough to click it to generate a mouse button event. I can't figure out how to disable tap- to-click in 17.10 either. I did not have these problems _at all_ in 17.04. I have the touchpad click method set to "Areas" and "Disable While Typing" enabled in gnome-tweak-tool. This does not help. I have these lines in the touchpad section of /usr/share/X11/xorg.conf.d/40-libinput.conf as well: Option "DisableWhileTyping" "true" Option "PalmDetection" "true" Option "Tapping" "false" They don't help either. This is a substantial regression in functionality from 17.04. It appears to be a problem using both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 21:28:05 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (182 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733032/+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 1733032] Re: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed)
Patch for gnome-control-center. This has reminded me that gtk/gdk also needs a fix but I've worked around that for now. ** Patch added: "gnome-control-center_3.27.92-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1733032/+attachment/5079021/+files/gnome-control-center_3.27.92-1ubuntu2.debdiff ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1733032 Title: Touchpad settings don't work after upgrading to 17.10 (because xserver-xorg-input-synaptics is still installed) Status in gnome-control-center package in Ubuntu: In Progress Status in gtk+3.0 package in Ubuntu: New Status in mutter package in Ubuntu: In Progress Bug description: Since upgrading to 17.10, my mouse pointer is repeatedly and frequently getting moved against my will when I am typing on my laptop keyboard (as opposed to external keyboard) because my hand brushes against the touchpad or even just near its surface. Furthermore, I don't want tap-to-click to be enabled. I want to actually have to push down on the mousepad hard enough to click it to generate a mouse button event. I can't figure out how to disable tap- to-click in 17.10 either. I did not have these problems _at all_ in 17.04. I have the touchpad click method set to "Areas" and "Disable While Typing" enabled in gnome-tweak-tool. This does not help. I have these lines in the touchpad section of /usr/share/X11/xorg.conf.d/40-libinput.conf as well: Option "DisableWhileTyping" "true" Option "PalmDetection" "true" Option "Tapping" "false" They don't help either. This is a substantial regression in functionality from 17.04. It appears to be a problem using both Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 17 21:28:05 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-05-19 (182 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-10-20 (28 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1733032/+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 1755717] [NEW] FFE: xcb-proto/libxcb 1.13
Public bug reported: This will be needed for the first HWE stack in 18.04.2, so best to add them now and not as an SRU which will be more painful. xcb-proto Release 1.13 (2018-02-28) = * dri3: Add multi-plane/modifier protocol for v1.2 * present: Add suboptimal-copy protocol for v1.2 * randr: Add output-lease protocol for v1.6 * Add support for variable-sized lists of FDs * xge: Add safe generic-event sending support * Fix initial connection handshaking * Updated XML DTD * Python 3.x cleanups and compatibility libxcb Release 1.13 (2018-02-28) = * Add support for variable-sized lists of FDs * Poll for events when blocking waiting for special events * xinput: Enable XInput extension by default * ge: Add explicit support for GenericEvent extension * Fix documentation warnings from clang * Cosmetic cleanups although it's hard for me to prove, but libxcb should fix a number of threading issues seen in the past. These are already in Debian testing, so they build and haven't caused regressions. ** Affects: libxcb (Ubuntu) Importance: Undecided Status: New ** Affects: xcb-proto (Ubuntu) Importance: Undecided Status: New ** Also affects: xcb-proto (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1755717 Title: FFE: xcb-proto/libxcb 1.13 Status in libxcb package in Ubuntu: New Status in xcb-proto package in Ubuntu: New Bug description: This will be needed for the first HWE stack in 18.04.2, so best to add them now and not as an SRU which will be more painful. xcb-proto Release 1.13 (2018-02-28) = * dri3: Add multi-plane/modifier protocol for v1.2 * present: Add suboptimal-copy protocol for v1.2 * randr: Add output-lease protocol for v1.6 * Add support for variable-sized lists of FDs * xge: Add safe generic-event sending support * Fix initial connection handshaking * Updated XML DTD * Python 3.x cleanups and compatibility libxcb Release 1.13 (2018-02-28) = * Add support for variable-sized lists of FDs * Poll for events when blocking waiting for special events * xinput: Enable XInput extension by default * ge: Add explicit support for GenericEvent extension * Fix documentation warnings from clang * Cosmetic cleanups although it's hard for me to prove, but libxcb should fix a number of threading issues seen in the past. These are already in Debian testing, so they build and haven't caused regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1755717/+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 1453429] Re: Add a new variant to symbols/lk
** Package changed: libxcb (Ubuntu) => xkeyboard-config (Ubuntu) ** Changed in: xkeyboard-config (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1453429 Title: Add a new variant to symbols/lk Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: We have registered a new variant for the X11\kbd\symbols\lk file: https://bugs.freedesktop.org/show_bug.cgi?id=90345 What is the procedure to make that layout variant also available in the upcoming Ubuntu releases? Thank you. JC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1453429/+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 1755144] Re: No audio on vlc or videos sound or video files
I did the "sudo dpkg -i *,deb" after cd to the directory containing the downloaded 3.7 pulseaudio deb files. All installed with warnings about downgrading from 3.8 to 3.7. However, there was now a No Entry sign on the 'systray'. So I ran Synaptic and there were 3 'missing' packages, namely: libpulse-dev_8.0-0ubuntu3.7_amd64.debg libpulse-mainloop-glib0_8.0-0ubuntu3.7_amd64.deb pulseaudio-module-bluetooth_8.0-0ubuntu3.7_amd64.deb So I downloaded them and installed them Ok. And No Entry sign went away. However, audio problems are still there as before. Audio working on: (with speakers connected by jackplug to PC, and any mp3/mp4 files or CD or DVD) OR (with hdmi (in monitor) speakers or usb speakers AND Clementine or RhythmBox on mp3 files or CDs, or Chrome on YouTube videos) However, audio not working on: with hdmi (in monitor) speakers or usb speakers AND VLC for mp3 or mp4 files or CDs or DVDs, or Videos (Totem) for mp4 files or DVDs. Results of 'dpkg -l | grep gstreamer > gst.txt' and 'dpkg -l | grep libav > libav.txt' are attached in a tar.gz file. ** Attachment added: "Contains gst.txt & libav.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+attachment/5078994/+files/gst-libav.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1755144 Title: No audio on vlc or videos sound or video files Status in pulseaudio package in Ubuntu: Incomplete Bug description: Up until a few weeks ago there was no problem with playing sound from mp3 files. I have a pair of usb speakers. Audio plays Ok on them for video clips using Chrome (e.g. from BBC website). Using vlc 2.2.2 (from Ubuntu repos), neither a CD nor DVD (video is Ok) nor mp3 file plays audio. mp3 files play Ok using Rhythmbox. I've also tried vlc 3.0 with no success. Interestingly, the standard Videos app (Totem?) also doesn't play sound on these speakers either of an mp4 file (downloaded from YouTube, though it plays Ok on YouTube website using Chrome) or a DVD. Clemenetine plays mp3 files Ok. I first reported this as bug 1752267 as I thought that the problem was with vlc. On that bug, it was suggested that the problem is with Pulseaudio. Just now, I've tried to play sound through my monitor's built in speakers connected by hdmi (though the monitor displays Ok) with no success even though the built-in speakers play sound using pavucontrol when testing is invoked. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.8 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: john 2410 F pulseaudio /dev/snd/controlC0: john 2410 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 12 11:06:46 2018 InstallationDate: Installed on 2016-12-08 (458 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0043.2015.0904.1904 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0043.2015.0904.1904:bd09/04/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1755144/+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 1751011] Re: bash crashes in qemu-user environments (bionic)
I'd like to know any progress from the qemu community. I feel like it would be long journey to address this problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1751011 Title: bash crashes in qemu-user environments (bionic) Status in bash package in Ubuntu: Triaged Status in bash package in Debian: Fix Released Bug description: Attempts to launch bash in an arm64 qemu-user environment in bionic results in the following error message: bash: xmalloc: .././shell.c:1709: cannot allocate 10 bytes (0 bytes allocated) This causes any qemu/chroot based bootstrapping to fail as many packages invoke bash during postinst. Version: bash_4.4.18-1ubuntu1_arm64 Release: 18.04 pre-release QEMU: 2.8.0 This appears to have been reported and fixed in the corresponding Debian package (https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=889869) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1751011/+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
