[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04
I think this is what you're looking for. I upgraded to 21.04 and had the same issue. ``` MarkInstall qt5-default:amd64 < 5.14.2+dfsg-6 @ii mK Ib > FU=0 Installing qtbase5-gles-dev:amd64 as Depends of qt5-default:amd64 MarkKeep qtbase5-dev:amd64 < 5.14.2+dfsg-6 -> 5.15.2+dfsg-5 @ii umU > FU=0 Delayed Removing: qtbase5-dev:amd64 as upgrade is not an option for qtbase5-gles-dev:amd64 (5.15.2+dfsg-3) MarkInstall qtbase5-gles-dev:amd64 < none -> 5.15.2+dfsg-3 @un uN Ib > FU=0 Installing libqt5gui5-gles:amd64 as Depends of qtbase5-gles-dev:amd64 MarkKeep libqt5gui5:amd64 < 5.14.2+dfsg-6 -> 5.15.2+dfsg-5 @ii umU > FU=0 Delayed Removing: libqt5gui5:amd64 as upgrade is not an option for libqt5gui5-gles:amd64 (5.15.2+dfsg-3) MarkInstall libqt5gui5-gles:amd64 < none -> 5.15.2+dfsg-3 @un uN Ib > FU=0 MarkDelete libqt5gui5:amd64 < 5.14.2+dfsg-6 | 5.15.2+dfsg-5 @ii umH Ib > FU=0 MarkDelete qtbase5-dev:amd64 < 5.14.2+dfsg-6 | 5.15.2+dfsg-5 @ii umH Ib > FU=0 ``` ** Attachment added: "apt.log" https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1920130/+attachment/5496778/+files/apt.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtdeclarative-opensource-src package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src-gles package in Debian: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_F
[Touch-packages] [Bug 1920130] Re: System icons missing in kubuntu 21.04
** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1920130/+attachment/5496779/+files/apt-term.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1920130 Title: System icons missing in kubuntu 21.04 Status in qtdeclarative-opensource-src package in Ubuntu: Won't Fix Status in qtdeclarative-opensource-src-gles package in Debian: New Bug description: Hi, just testing Kubuntu 21.04 on a spare machine. The upgrade initially was fine, but I then install kdenlive and krita which has messed up the system icons and window decorations (corners of windows are showing black squares). I have been through all the normal checks and even created a new user, but the bug still persists. The system Icons are broken in the system and nothing to do with the user account. lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 Looking at the following may shed some light on the problem... Thanks, Paul. more .xsession-errors property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG libpng warning: iCCP: profile 'ICC profile': 'RGB ': RGB color space not permitted on grayscale PNG QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:94: TypeError: Cannot read pro perty 'position' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/AbstractApplicationItem.qml:93: TypeError: Cannot read pro perty 'background' of null file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/newstuff/qml/Page.qml:130: TypeError: Cannot read property 'useLabel' of null file:///usr/share/kpackage/kcms/kcm_splashscreen/contents/ui/main.qml:42:13: QML ColumnLayout: Cannot anchor to an ite m that isn't a parent or sibling. qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55182, resource id: 69206064, major code: 18 (ChangePr operty), minor code: 0 qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 64351, resource id: 69206065, major code: 18 (ChangePr operty), minor code: 0 QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "maximumWidth" QSGTextureAtlas: texture atlas allocation failed, code=501 file:///usr/share/kpackage/kcms/kcm_style/contents/ui/main.qml:52:13: QML ColumnLayout: Cannot anchor to an item that isn't a parent or sibling. xsettingsd: Reloading configuration xsettingsd: Loaded 11 settings from /home/paul/.config/xsettingsd/xsettingsd.conf kdeinit5: Got SETENV 'GTK_RC_FILES=/etc/gtk/gtkrc:/home/paul/.gtkrc:/home/paul/.config/gtkrc' from launcher. kdeinit5: Got SETENV 'GTK2_RC_FILES=/etc/gtk-2.0/gtkrc:/home/paul/.gtkrc-2.0:/home/paul/.config/gtkrc-2.0' from launch er. QDBusConnection: error: could not send signal to service "" path "//home/paul/.kde/share/config/kdeglobals" interface "org.kde.kconfig.notify" member "ConfigChanged": Invalid object path: //home/paul/.kde/share/config/kdeglobals QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls.2/org.kde.desktop/ScrollView.qml:86:25: QML ScrollBar: Bindi ng loop detected for property "visible" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kcm/GridViewKCM.qml:65:5: QML GridView: Binding loop detected for pro perty "rightPadding" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/private/globaltoolbar/PageRowGlobalToolBarUI.qml:65:9: QML RowLayout (parent or ancestor of QQuickLayoutAttached):
[Touch-packages] [Bug 1918876] [NEW] sudo segfaults when /etc/sudoers has syntax error
Public bug reported: If /etc/sudoers contains the following (syntactically invalid) line: %sudo ALL=(ALL:ALL) NOPASSWD ALL the sudo command will segfault: $ sudo true [1]12958 segmentation fault (core dumped) sudo true A better result would be to fail or warn with a syntax error. Release: groovy Architecture: amd64 sudo version: 1.9.1-1ubuntu1.1 ** Affects: sudo (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1918876 Title: sudo segfaults when /etc/sudoers has syntax error Status in sudo package in Ubuntu: New Bug description: If /etc/sudoers contains the following (syntactically invalid) line: %sudo ALL=(ALL:ALL) NOPASSWD ALL the sudo command will segfault: $ sudo true [1]12958 segmentation fault (core dumped) sudo true A better result would be to fail or warn with a syntax error. Release: groovy Architecture: amd64 sudo version: 1.9.1-1ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1918876/+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 1917451] [NEW] audacious audacious-plugins dependancy issue
Public bug reported: A recent update removed audacious. When trying to add it back it I get: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. audacious : Depends: libaudcore5 (= 4.0.5-1) but 4.1-1build1~ubuntu20.10 is to be installed audacious-plugins : Depends: audacious-plugins-data (= 4.0.5-1) but 4.1-0build1~ubuntu20.10 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: lsb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lsb in Ubuntu. https://bugs.launchpad.net/bugs/1917451 Title: audacious audacious-plugins dependancy issue Status in lsb package in Ubuntu: New Bug description: A recent update removed audacious. When trying to add it back it I get: Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. audacious : Depends: libaudcore5 (= 4.0.5-1) but 4.1-1build1~ubuntu20.10 is to be installed audacious-plugins : Depends: audacious-plugins-data (= 4.0.5-1) but 4.1-0build1~ubuntu20.10 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/1917451/+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 1763584] Re: ureadahead service fails with error Error while tracing: No such file or directory
This is affecting me running Ubuntu 20.10. Is ureadahead still used, 2 years on, or should I remove it? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1763584 Title: ureadahead service fails with error Error while tracing: No such file or directory Status in ureadahead package in Ubuntu: Confirmed Bug description: I'm reporting this as duplicate of #1176536 to provide more info. dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service ● ureadahead.service - Read required files in advance Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 10min ago Main PID: 379 (code=exited, status=5) Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while tracing: No such file or directory Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ureadahead 0.100.0-20 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 13:13:26 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1763584/+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 1895383] [NEW] package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1
Public bug reported: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shared-mime-info (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1895383 Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 Status in shared-mime-info package in Ubuntu: New Bug description: Failure occurred on update ProblemType: Package DistroRelease: Ubuntu 20.04 Package: shared-mime-info 1.15-1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 AptOrdering: bcompare:amd64: Install r-cran-mass:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 12 19:29:30 2020 DuplicateSignature: package:shared-mime-info:1.15-1 Processing triggers for shared-mime-info (1.15-1) ... Failed to rename /usr/share/mime/inode/socket.xml.new as /usr/share/mime/inode/socket.xml: No such file or directory dpkg: error processing package shared-mime-info (--configure): installed shared-mime-info package post-installation script subprocess returned error exit status 1 ErrorMessage: installed shared-mime-info package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-05-07 (127 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: shared-mime-info Title: package shared-mime-info 1.15-1 failed to install/upgrade: installed shared-mime-info package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1895383/+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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade
I've just encountered this issue myself, on a VM that started life as Ubuntu 16.04, do-release-upgrade to 18.04, then to 20.04, and now it fails to boot with a similar error: /lib/systemd/libsystemd- shared-245.so: undefined symbol: seccomp_api_get The only non-Ubuntu-standard stuff on this VM is some perl modules installed via CPAN, and none of those touch anything to do with Systemd, so I'm not sure why this is happening. I did see a post-install upgrade issue with the rkhunter package failing to find /usr/bin/egrep, but I ignored that issue and continued. I'm going to rollback, look for the lib involved, and see if I can remove it before retrying the do-release-upgrade -d to 20.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1876486 Title: Kernel panic booting after 18.04 to 20.04 upgrade Status in libseccomp package in Ubuntu: Incomplete Bug description: Upgraded Ubuntu 18.04 to 20.04. Following the upgrade, booting was not possible. The error messages is: /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: undefined symbol: seccomp_api_get [4.608900] Kernel panic - not syncing: Attempted to kill init! exitcode=0x7f00 See also attached photograph of screen during boot. Upgrade followed steps from here: https://help.ubuntu.com/community/FocalUpgrades/Kubuntu With the excpetion that The -d flag was used for the do-release-upgrade: sudo do-release-upgrade -d -m desktop 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Prior to upgrade: Ubuntu 18.04.4 After upgrade (but never booted): Ubuntu (Kubuntu) 20.04 Note that Ubuntu had originally be installed, but kubuntu-desktop was recently installed to change to Kubuntu, but no booting problems were experienced before updating to 20.04. 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Unknown -- Package version may have changed when upgrading to 20.04. 3) What you expected to happen Boot without kernel panic. 4) What happened instead Could not boot. Even selecting safe mode from grub could not boot. Had to restore system from backups. Will not attempt upgrade again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend
Also seeing the same behavior on 20.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1722478 Title: Two-finger scrolling and click-and-drag no longer works after resuming from suspend Status in Linux: Confirmed Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+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 1878814] [NEW] apparmor stays active even when the service is disabled
Public bug reported: Trying to access a fresh install of MySQL, what a complete pain that is!! I installed mysql-workbench-community from the app store. Attempts to access the database with user root were rebuffed by an AppArmor error about permissions. Running aa-status I could see the app in the enforce category, so I made many attempts to move it to complain, but this failed and I'll file a bug report about that as well. I decided to disable both the apparmor and ufw service. However, the AppArmor permissions error dialog continue to appear and it's not possible to access the database. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 09:40:01 2020 InstallationDate: Installed on 2020-03-10 (65 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] AppArmor D-Bus mediation is enabled May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] AppArmor D-Bus mediation is enabled May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1878814 Title: apparmor stays active even when the service is disabled Status in apparmor package in Ubuntu: New Bug description: Trying to access a fresh install of MySQL, what a complete pain that is!! I installed mysql-workbench-community from the app store. Attempts to access the database with user root were rebuffed by an AppArmor error about permissions. Running aa-status I could see the app in the enforce category, so I made many attempts to move it to complain, but this failed and I'll file a bug report about that as well. I decided to disable both the apparmor and ufw service. However, the AppArmor permissions error dialog continue to appear and it's not possible to access the database. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 15 09:40:01 2020 InstallationDate: Installed on 2020-03-10 (65 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] AppArmor D-Bus mediation is enabled May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] AppArmor D-Bus mediation is enabled May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1878814/+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 1878862] [NEW] AppArmor - Cannot move snap packages from enforce to complain
Public bug reported: I installed mysql-workbench-community from the app store but it is unable to actually access the local database due to AppArmor intervention. All attempts to move the app in to complain results in error messages. ~# aa-status apparmor module is loaded. 10 profiles are loaded. 10 profiles are in enforce mode. . snap.mysql-workbench-community.mysql-workbench-community . 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. ~# aa-complain /snap/bin/mysql-workbench-community Profile for /usr/bin/snap not found, skipping ~# aa-complain snap.mysql-workbench-community Can't find snap.mysql-workbench-community in the system path list. If the name of the application is correct, please run 'which snap.mysql-workbench-community' as a user with correct PATH environment set up in order to find the fully-qualified path and use the full path as parameter. ~# aa-complain snap.mysql-workbench-community.mysql-workbench-community Can't find snap.mysql-workbench-community.mysql-workbench-community in the system path list. If the name of the application is correct, please run 'which snap.mysql-workbench-community.mysql-workbench-community' as a user with correct PATH environment set up in order to find the fully-qualified path and use the full path as parameter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 15 09:47:56 2020 InstallationDate: Installed on 2020-03-10 (65 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=d73f3324-549c-4a63-b2bd-f813366411ac ro quiet splash vt.handoff=7 SourcePackage: apparmor Syslog: May 15 09:38:16 owen-AOD255 dbus-daemon[1118]: [session uid=125 pid=1118] AppArmor D-Bus mediation is enabled May 15 09:39:00 owen-AOD255 dbus-daemon[1762]: [session uid=1000 pid=1762] AppArmor D-Bus mediation is enabled May 15 09:39:04 owen-AOD255 dbus-daemon[2353]: [session uid=125 pid=2353] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1878862 Title: AppArmor - Cannot move snap packages from enforce to complain Status in apparmor package in Ubuntu: New Bug description: I installed mysql-workbench-community from the app store but it is unable to actually access the local database due to AppArmor intervention. All attempts to move the app in to complain results in error messages. ~# aa-status apparmor module is loaded. 10 profiles are loaded. 10 profiles are in enforce mode. . snap.mysql-workbench-community.mysql-workbench-community . 0 profiles are in complain mode. 0 processes have profiles defined. 0 processes are in enforce mode. 0 processes are in complain mode. 0 processes are unconfined but have a profile defined. ~# aa-complain /snap/bin/mysql-workbench-community Profile for /usr/bin/snap not found, skipping ~# aa-complain snap.mysql-workbench-community Can't find snap.mysql-workbench-community in the system path list. If the name of the application is correct, please run 'which snap.mysql-workbench-community' as a user with correct PATH environment set up in order to find the fully-qualified path and use the full path as parameter. ~# aa-complain snap.mysql-workbench-community.mysql-workbench-community Can't find snap.mysql-workbench-community.mysql-workbench-community in the system path list. If the name of the application is correct, please run 'which snap.mysql-workbench-community.mysql-workbench-community' as a user with correct PATH environment set up in order to find the fully-qualified path and use the full path as parameter. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apparmor 2.13.3-7ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri May 15 09:47:56 2020 InstallationDate: Installed on 2020-03-10 (65 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcEnviron: LANGUAGE=en_GB:
[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Released Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher
It's not just Minecraft, it's DropBox-2020 and BitDefender as well. I'm sure there are others as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869716 Title: Removing libpango1.0-0 broke Minecraft Launcher Status in pango1.0 package in Ubuntu: Fix Committed Bug description: I just updated my machine, and when I did libpango1.0-0 was removed. This removed minecraft-launcher - the (very) popular launcher for Minecraft Java edition. I have reported this upstream, in case they can update their package https://bugs.mojang.com/browse/MCL-13512 I am filing this bug so we can track it internally. I personally think this shouldn't have been done this late in the cycle, but there may well have been good reasons for it. As a result of the change though, it's now not possible to install Minecraft on Ubuntu 20.04. $ sudo apt install ./Minecraft\(1\).deb Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not installable E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869723] [NEW] latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender
Public bug reported: I'm using 20.04 beta. I think the latest updates to Pango have broken dependencies for DropBox-2020 and BitDefender, of less importance. Has libpango1.0-0 become libpango-1.0-0? I think DropBox depends on libpango-1.0-0, or maybe another package that's been superceded. doing a sudo apt upgrade gives: The following additional packages will be installed: libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools The following packages will be REMOVED bitdefender-scanner-gui dropbox libpango1.0-0 The following packages will be upgraded: gir1.2-pango-1.0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools ** Affects: pango1.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 pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1869723 Title: latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender Status in pango1.0 package in Ubuntu: New Bug description: I'm using 20.04 beta. I think the latest updates to Pango have broken dependencies for DropBox-2020 and BitDefender, of less importance. Has libpango1.0-0 become libpango-1.0-0? I think DropBox depends on libpango-1.0-0, or maybe another package that's been superceded. doing a sudo apt upgrade gives: The following additional packages will be installed: libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools The following packages will be REMOVED bitdefender-scanner-gui dropbox libpango1.0-0 The following packages will be upgraded: gir1.2-pango-1.0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869723/+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 1860985] Re: packagekitd using 100% CPU
It's off again, this time an opensuse repository. I would remove it about now but it seems it can't be removed without breaking other stuff. The following packages will be REMOVED apturl gnome-packagekit gnome-software gnome-software-plugin-flatpak gnome-software-plugin-snap gstreamer1.0-packagekit muon muon-discover muon-notifier muon-updater nautilus-share package-update-indicator packagekit pk-update-icon plasma-discover software-properties-common software-properties-gtk software-properties-qt ubuntu-desktop ubuntu-desktop-minimal ubuntu-software Good grief, it's got its tentacles in to loads. How do I disable it, how do I make it check for updates every few hours not seconds, how do I tell it not to retry broken PPAs insessently consuming 100% CPU. How do I turn this wretched thing off?! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: Incomplete Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1860985] Re: packagekitd using 100% CPU
The PPA was deb [arch=amd64] http://dl.google.com/linux/webdesigner/deb/ stable main The linked ticket does sound like the issue, but my other concern is despite setting the "Automatically check for updates" to "Never" is Software and Updates the system continues to look for update at quite a high frequency and even when packagekitd is "idle" it still uses 20% CPU -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: Incomplete Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1860985] Re: packagekitd using 100% CPU
So now running at about 33% CPU. It was a broken update PPA. Really! Exactly how many times a second are the PPAs being checked for updates?! It's a broken PPA, surely the package manager can handle a broken PPA better than 100% CPU usage. And exactly what is it doing that requires 20% CPU usage when it's idle?! Is there an admin program for this? I think it only needs to update a couple of times a day. The only admin I've found offers very few options as to the frequency of update checking and none of them seem to work. It slows down boot, even though this should be disabled and it's consuming far too much CPU given that it's showing as auto checks disabled. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: New Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1860985] [NEW] packagekitd using 100% CPU
Public bug reported: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago) ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1860985 Title: packagekitd using 100% CPU Status in packagekit package in Ubuntu: New Bug description: That's all I can report at this stage. Any attempt to kill it or disable the service fails and up goes its CPU usage, fans blowing the works! packagekit status give Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: missing initialization - please fix the application Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority after 2137ms Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying to obtain org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0) Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained auth for org.freedesktop.packagekit.system-sources-refresh I am uid: 1000. It would be helpful if it gave some indication as to "the application". I can't find anywhere to admin this. It looks like my trust level is too low "only_trusted:0" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: packagekit 1.1.13-2 Uname: Linux 5.5.0-050500rc7-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Mon Jan 27 13:54:13 2020 InstallationDate: Installed on 2017-12-06 (782 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: packagekit UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)
[Touch-packages] [Bug 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4
Command run and status set to Confirmed as requested ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1855297] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311418/+files/ProcEnviron.txt -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1855297] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311417/+files/ProcCpuinfoMinimal.txt -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1855297] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311416/+files/Dependencies.txt -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1855297] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311415/+files/ProcEnviron.txt ** Description changed: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu13 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2017-12-06 (734 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + NonfreeKernelModules: nvidia_modeset nvidia + Package: network-manager 1.20.4-2ubuntu3 + PackageArchitecture: amd64 + Tags: focal + Uname: Linux 5.4.2-050402-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04
[Touch-packages] [Bug 1855297] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311414/+files/ProcCpuinfoMinimal.txt -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+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 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4
apport information ** Tags added: apport-collected ** Description changed: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu13 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2017-12-06 (734 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + NonfreeKernelModules: nvidia_modeset nvidia + Package: network-manager 1.20.4-2ubuntu3 + PackageArchitecture: amd64 + Tags: focal + Uname: Linux 5.4.2-050402-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1855297/+attachment/5311413/+files/Dependencies.txt -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTI
[Touch-packages] [Bug 1855297] [NEW] NetworkManager service fails to secure Ethernet connection when using kernel 5.4
Public bug reported: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in network-manager package in Ubuntu: New Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855297/+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 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
so it is, thanks! So I think we can say this original bug is obsolete / already fixed -- 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/1690051 Title: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed 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:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c39b5c96e18a9e1b48ea983380914ce29fd79134 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/1690051/+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 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
I am still getting the crash, but the location of it has changed. Now it dies at txt = avahi_string_list_add_pair(txt, "device", s->name); Thread 4 "avahi-ml" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffe5984700 (LWP 5939)] 0x5590f820 in ?? () (gdb) bt #0 0x5590f820 in ?? () #1 0x77657566 in pa_hashmap_get (h=h@entry=0x557ee040, key=key@entry=0x7fffe5faa028) at pulsecore/hashmap.c:182 #2 0x77642901 in pa_proplist_gets (p=0x557ee040, key=key@entry=0x7fffe5faa028 "device.description") at pulse/proplist.c:283 #3 0x7fffe5fa846c in publish_service (api=, service=0x558bc280) at modules/module-zeroconf-publish.c:318 #4 0x773fd578 in once_callback (m=0x559484b8, e=0x55831ac0, userdata=) at pulse/mainloop-api.c:45 #5 0x774002ad in dispatch_defer (m=0x55948460) at pulse/mainloop.c:680 #6 pa_mainloop_dispatch (m=m@entry=0x55948460) at pulse/mainloop.c:889 #7 0x774004de in pa_mainloop_iterate (m=0x55948460, block=, retval=0x0) at pulse/mainloop.c:929 #8 0x77400560 in pa_mainloop_run (m=0x55948460, retval=retval@entry=0x0) at pulse/mainloop.c:944 #9 0x7740e3c9 in thread (userdata=0x55823ae0) at pulse/thread-mainloop.c:100 #10 0x7767e318 in internal_thread_func (userdata=0x55874580) at pulsecore/thread-posix.c:81 #11 0x76b676db in start_thread (arg=0x7fffe5984700) at pthread_create.c:463 #12 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (gdb) this is with pulseaudio_11.1-1ubuntu7.2 -- 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/1690051 Title: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed 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:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c39b5c96e18a9e1b48ea983380914ce29fd79134 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/1690051/+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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
I've done some more digging into the systemd package update issue. We have a number of Ubuntu 18.04 hosts, most of them are virtual machines running simple eth0 configurations under Hyper-V. All of those VMs updated the systemd package without issue. The only hosts which had issues after the systemd package upgrade were the two SuperMicros running bonded 10G interfaces. On both of those hosts, the bond defined in netplan seems to have lost its configuration during the systemd upgrade. There were multiple kern.log messages regarding the bond leaving one of its ports in a disabled state after the update. Both hosts logged this on the same second that dpkg.log shows the systemd package itself entering 'status installed', so I'm confident it was that systemd package rather than pam-systemd that followed several seconds later. I am still willing to provides logs and configurations if you tell me what you need to see. -- 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/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Incomplete Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
I followed up with my coworker who originally built our two misbehaving boxes. He also ended up having to reboot the second box I left for him, to get the br01 bridge configuration back in working order. Simply running 'netplan apply' and restarting the systemd network service did not resolve it, but a full reboot did. We are using the default 18.04 netplan setup, we haven't reversed back to ifupdown like the other reporter. Both hosts lost their networking immediately after the systemd update was applied this morning, which installed version 237-3ubuntu10.19. I can delve through them to find any logs or config files you want. These are Supermicro rack mounts with dual 10G interfaces, built as headless servers, so no ubuntu-desktop or X11 is installed on them. We have sssd installed on these with the required pam customizations to configure sssd to live in our Active Directory environment. pam-auth- updated printed about local mods to common-* so it wasn't updating. Those are the only unusual outputs from this mornings unattended- upgrades-dpkg.log file. I can attach any logs or other files you care to view. -- 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/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Incomplete Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces
Two of our Ubuntu 18.04 hosts applied this update this morning and both dropped offline. They're both using netplan and have bonded interfaces. The bond layer was offline. I had to reboot to get the network stack running again. I left one host offline so the coworker who configured them can look it over later this morning. Two identical hosts did not apply this systemd update this morning and they're both still online. -- 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/1823871 Title: After unattended-upgrade of systemd IP configuration removed from interfaces Status in systemd package in Ubuntu: Confirmed Bug description: Info: Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 2018). HP DL380 server I had this issue already twice in the past couple of months. After unattended upgrade of systemd my server's public IP address is removed from the interface. I statically configure the IP address using the interfaces file. I have opted out of the YML based network configuration. This is my apt history log: Start-Date: 2019-04-09 06:15:01 Commandline: /usr/bin/unattended-upgrade Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:07 Start-Date: 2019-04-09 06:15:12 Commandline: /usr/bin/unattended-upgrade Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:15:56 Start-Date: 2019-04-09 06:15:59 Commandline: /usr/bin/unattended-upgrade Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19) End-Date: 2019-04-09 06:16:15 After that my server was unavailable from the Internet. When I logged in via out of band management and simply brought down and up the interface everything went back to normal. As said above this is the second time I had this issue. Last time it was unattended upgrades and it was systemd again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+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 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
I was really hoping to keep this machine on LTS, is the fix not going to be backported? -- 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/1690051 Title: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed 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:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c39b5c96e18a9e1b48ea983380914ce29fd79134 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/1690051/+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 1690051] Re: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate()
>From my own debugging, the crash appears to be in this line: if (!s->userdata->client || avahi_client_get_state(s->userdata->client) != AVAHI_CLIENT_S_RUNNING) return; adding a check for !s->userdata seems to fix the issue (for some reason, probably due to a race condition, userdata is null at the time of the call). -- 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/1690051 Title: pulseaudio crashed with SIGSEGV in publish_service() from once_callback() from dispatch_defer() from pa_mainloop_dispatch() from pa_mainloop_iterate() Status in pulseaudio package in Ubuntu: Confirmed 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:10.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/c39b5c96e18a9e1b48ea983380914ce29fd79134 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/1690051/+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 1801532] Re: pulseaudio crashing when publishing sound devices to zeroconf
checking for !s->userdata seems to fix it -- 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/1801532 Title: pulseaudio crashing when publishing sound devices to zeroconf Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00 dB, front-right: 30419 / 46% / -20.00 dB D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time scheduling: Permission denied I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback. D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. I: [pulseaudio] core.c: default_source: alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> alsa_output.pci-_00_1f.3.analog-stereo.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds. I: [pulseaudio] core.c: default_sink: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" to output:analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo+input:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status no I: [pulseaudio] core.c: default_sink: alsa_output.pci-_00_1f.3.analog-stereo -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1 I: [pulseaudio] core.c: default_source: alsa_output.pci-_00_1f.3.analog-stereo.monitor -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port analog-output-headphones, found iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port iec958-stereo-output, preferred = iec958-stereo D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away. D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. backtrace: #0 0x7fffe67c135f in publish_service (api=0x55816b48, service=0x558d00d0) at modules/module-zeroconf-publish.c:298 #1 0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, userdata=) at pulse/mainloop-api.c:45 #2 0x7740027d in dispatch_defer (m=0x55816af0) at pulse/mainloop.c:680 #3 pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889 #4 0x774004ae in pa_mainloop_iterate (m=0x55816af0, block=, retval=0x0) at pulse/mainloop.c:929 #5 0x77400530 in pa_mainloop_run (m=0x55816af0, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x7740e399 in thread (userdata=0x55837a30) at pulse/thread-mainloop.c:100 #7 0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at pulsecore/thread-posix.c:81 #8 0x76b676db in start_thread (arg=0x7fffe619d700) at pthread_create.c:463 #9 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 In general the stream is pretty skippy, so I wonder if there's some sort of periodic restarting issue happening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@li
[Touch-packages] [Bug 1801532] Re: pulseaudio crashing when publishing sound devices to zeroconf
the line in question is, I think: if (!s->userdata->client || avahi_client_get_state(s->userdata->client) != AVAHI_CLIENT_S_RUNNING) return; something here is null, probably because there's a restart happening? -- 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/1801532 Title: pulseaudio crashing when publishing sound devices to zeroconf Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00 dB, front-right: 30419 / 46% / -20.00 dB D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time scheduling: Permission denied I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback. D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. I: [pulseaudio] core.c: default_source: alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> alsa_output.pci-_00_1f.3.analog-stereo.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds. I: [pulseaudio] core.c: default_sink: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" to output:analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo+input:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status no I: [pulseaudio] core.c: default_sink: alsa_output.pci-_00_1f.3.analog-stereo -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1 I: [pulseaudio] core.c: default_source: alsa_output.pci-_00_1f.3.analog-stereo.monitor -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port analog-output-headphones, found iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port iec958-stereo-output, preferred = iec958-stereo D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away. D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. backtrace: #0 0x7fffe67c135f in publish_service (api=0x55816b48, service=0x558d00d0) at modules/module-zeroconf-publish.c:298 #1 0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, userdata=) at pulse/mainloop-api.c:45 #2 0x7740027d in dispatch_defer (m=0x55816af0) at pulse/mainloop.c:680 #3 pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889 #4 0x774004ae in pa_mainloop_iterate (m=0x55816af0, block=, retval=0x0) at pulse/mainloop.c:929 #5 0x77400530 in pa_mainloop_run (m=0x55816af0, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x7740e399 in thread (userdata=0x55837a30) at pulse/thread-mainloop.c:100 #7 0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at pulsecore/thread-posix.c:81 #8 0x76b676db in start_thread (arg=0x7fffe619d700) at pthread_create.c:463 #9 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 In general the stream is pretty skippy, so I wonder if there's some sort of periodic restarting issue happening To manage notifications about this
[Touch-packages] [Bug 1801532] [NEW] pulseaudio crashing when publishing sound devices to zeroconf
Public bug reported: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00 dB, front-right: 30419 / 46% / -20.00 dB D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Thread starting up I: [alsa-sink-ALC887-VD Analog] core-util.c: Failed to acquire real-time scheduling: Permission denied I: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Starting playback. D: [alsa-sink-ALC887-VD Analog] ratelimit.c: 27 events suppressed D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. I: [pulseaudio] core.c: default_source: alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor -> alsa_output.pci-_00_1f.3.analog-stereo.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] module-suspend-on-idle.c: Sink alsa_output.pci-_00_1f.3.analog-stereo becomes idle, timeout in 5 seconds. I: [pulseaudio] core.c: default_sink: alsa_output.pci-_01_00.1.hdmi-stereo-extra1 -> alsa_output.pci-_00_1f.3.analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. I: [pulseaudio] card.c: Changed profile of card 2 "alsa_card.pci-_00_1f.3" to output:analog-stereo D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] card.c: Setting card alsa_card.pci-_00_1f.3 profile output:analog-stereo+input:analog-stereo to availability status unknown D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-alsa-card.c: Jack 'Front Headphone Jack' is now unplugged D: [pulseaudio] device-port.c: Setting port analog-output-headphones to status no I: [pulseaudio] core.c: default_sink: alsa_output.pci-_00_1f.3.analog-stereo -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1 I: [pulseaudio] core.c: default_source: alsa_output.pci-_00_1f.3.analog-stereo.monitor -> alsa_output.pci-_01_00.1.hdmi-stereo-extra1.monitor D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] core-subscribe.c: Dropped redundant event due to change event. D: [pulseaudio] module-switch-on-port-available.c: Trying to switch away from port analog-output-headphones, found iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Trying to switch to port iec958-stereo-output D: [pulseaudio] module-switch-on-port-available.c: Finding best profile for port iec958-stereo-output, preferred = iec958-stereo D: [pulseaudio] module-rescue-streams.c: No sink inputs to move away. D: [alsa-sink-ALC887-VD Analog] alsa-sink.c: Cutting sleep time for the initial iterations by half. backtrace: #0 0x7fffe67c135f in publish_service (api=0x55816b48, service=0x558d00d0) at modules/module-zeroconf-publish.c:298 #1 0x773fd548 in once_callback (m=0x55816b48, e=0x558a15b0, userdata=) at pulse/mainloop-api.c:45 #2 0x7740027d in dispatch_defer (m=0x55816af0) at pulse/mainloop.c:680 #3 pa_mainloop_dispatch (m=m@entry=0x55816af0) at pulse/mainloop.c:889 #4 0x774004ae in pa_mainloop_iterate (m=0x55816af0, block=, retval=0x0) at pulse/mainloop.c:929 #5 0x77400530 in pa_mainloop_run (m=0x55816af0, retval=retval@entry=0x0) at pulse/mainloop.c:944 #6 0x7740e399 in thread (userdata=0x55837a30) at pulse/thread-mainloop.c:100 #7 0x7767e2a8 in internal_thread_func (userdata=0x55874bf0) at pulsecore/thread-posix.c:81 #8 0x76b676db in start_thread (arg=0x7fffe619d700) at pthread_create.c:463 #9 0x760e688f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 In general the stream is pretty skippy, so I wonder if there's some sort of periodic restarting issue happening ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1801532 Title: pulseaudio crashing when publishing sound devices to zeroconf Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.04 pulseaudio crashes after 5-10 if advertising sound devices is enabled: logs leading up to the crash: [New Thread 0x7fffe7fff700 (LWP 9068)] D: [pulseaudio] alsa-sink.c: Read hardware volume: front-left: 30419 / 46% / -20.00
[Touch-packages] [Bug 1800813] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1
Public bug reported: Problem occurred while upgrading 16.04 -> 18.04. I can t tell if it's a unique problem or not. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 02:51:00 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-21 (1014 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-31 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1800813 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 Status in ca-certificates package in Ubuntu: New Bug description: Problem occurred while upgrading 16.04 -> 18.04. I can t tell if it's a unique problem or not. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 31 02:51:00 2018 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-21 (1014 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-10-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1800813/+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 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
The original bug title was '15:10: bluetoothd reports "Not enough handles to register service" at start', and the original bug description described both the "Not enough free handles to register service" problem and the "Failed to start discovery" problem[1]. Between #47 and #48, the title and description were changed to focus on the "Failed to start discovery" problem. It seems to me that most of the people in the thread are focused on the "Not enough free handles to register service", and aside from the close message in #48, the only mention of the "Failed to start discovery" problem was in the original description. Perhaps it would be useful to split the "Failed to start discovery" problem off into its own bug and keep this bug focused on "Not enough free handles to register service"? That way the history and relevant log files are all kept in one place, subscribers won't have to subscribe to another bug, and links pointing to this bug for the "Not enough free handles to register service" problem won't need to be updated. [1] https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/comments/0 -- 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/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1666371] [NEW] package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status
*** This bug is a duplicate of bug 1654191 *** https://bugs.launchpad.net/bugs/1654191 Public bug reported: Just gives me a message saying "System error detected" I recently updated to 16.10 from 16.04 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17 Uname: Linux 4.8.0-38-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Feb 20 19:45:14 2017 DuplicateSignature: package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package libunity-scopes1.0:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-18 (278 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-02-21 (0 days ago) ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1666371 Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in unity-scopes-api package in Ubuntu: New Bug description: Just gives me a message saying "System error detected" I recently updated to 16.10 from 16.04 ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-38.41-generic 4.8.17 Uname: Linux 4.8.0-38-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Mon Feb 20 19:45:14 2017 DuplicateSignature: package:libunity-scopes1.0:amd64:1.0.7+16.10.20160921-0ubuntu2 Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ... Cannot start click due to a conflict with a different locally-installed Python 'click' package. Remove it using Python packaging tools and try again. dpkg: error processing package libunity-scopes1.0:amd64 (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-05-18 (278 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: unity-scopes-api Title: package libunity-scopes1.0:amd64 1.0.7+16.10.20160921-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2017-02-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1666371/+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 1633954] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I was doing the distro upgrade from 16.04 to 16.10 and I encountered this error. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 19:37:22 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-10 (1195 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) ** Affects: click (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1633954 Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click package in Ubuntu: New Bug description: I was doing the distro upgrade from 16.04 to 16.10 and I encountered this error. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click 0.4.43+16.04.20160203-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-43.63-generic 4.4.21 Uname: Linux 4.4.0-43-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Sun Oct 16 19:37:22 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-10 (1195 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.1 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to yakkety on 2016-10-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1633954/+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 1626288] Re: X fonts and widgets disappear after suspend/resume cycle
This happens to me too with intel graphics, although not on every suspend / resume cycle. I'll test the mainline kernel and see if that fixes the issue. My machine has had issues in the past with SNA acceleration, this may be another case where falling back to UXA fixes it. https://wiki.archlinux.org/index.php/intel_graphics#Troubleshooting -- 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/1626288 Title: X fonts and widgets disappear after suspend/resume cycle Status in xorg package in Ubuntu: Incomplete Bug description: not all the time, but at some suspend/resume operations fonts disapear from gnome terminal, nm-applet and soffice which then show spaces and underscore placeholders instead of characters. google chrome, thunderbird, firefox, virtualbox are not affected. As it happens not at each suspend resume I find it hard to diagnose what is going wrong. next time I will launch more apps to see wich ones are affected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 BootLog: /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks [[0;1;31mFAILED[0m] Failed to start Automatically refresh installed snaps. See 'systemctl status snapd.refresh.service' for details. [[0;32m OK [0m] Started Detect the available GPUs and deal with any system changes. Starting Light Display Manager... CompizPlugins: (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS daemon: Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused Failed to get value for `/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running CompositorRunning: None CurrentDesktop: i3 Date: Wed Sep 21 23:41:50 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:6504] InstallationDate: Installed on 2016-07-27 (56 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Notebook W65_67SZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05SB.02 dmi.board.asset.tag: Tag 12345 dmi.board.name: W65_67SZ dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05SB.02:bd08/26/2015:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W65_67SZ dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Sep 21 23:08:03 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5941 vendor CMN xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626288/+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 1587464] Re: ucf errors upgrading php5-cli and libapache2-mod-php5
Not actually a bug; it turns out GREP_OPTIONS was set in the environment to include "-n". ** Changed in: ucf (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1587464 Title: ucf errors upgrading php5-cli and libapache2-mod-php5 Status in ucf package in Ubuntu: Invalid Bug description: Ubuntu 14.04.3 LTS ucf package version: 3.0027+nmu1 Attempting to upgrade php5-cli and libapache2-mod-php5 packages produces the following error: Setting up php5-cli (5.5.9+dfsg-1ubuntu4.17) ... ucfr: Attempt from package php5-cli to take /etc/php5/cli/php.ini away from package 9:9:9:10:11:12:php5-cli ucfr: Aborting. dpkg: error processing package php5-cli (--configure): subprocess installed post-installation script returned error exit status 4 Setting up libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.17) ... ucfr: Attempt from package libapache2-mod-php5 to take /etc/php5/apache2/php.ini away from package 7:7:7:7:8:9:libapache2-mod-php5 ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 The strange package names seem to be present in /var/lib/ucf/registry which I attach. Previous versions of the registry file in registry.1 et seq have fewer prepended numbers until registry.5 which has none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1587464/+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 1587464] [NEW] ucf errors upgrading php5-cli and libapache2-mod-php5
Public bug reported: Ubuntu 14.04.3 LTS ucf package version: 3.0027+nmu1 Attempting to upgrade php5-cli and libapache2-mod-php5 packages produces the following error: Setting up php5-cli (5.5.9+dfsg-1ubuntu4.17) ... ucfr: Attempt from package php5-cli to take /etc/php5/cli/php.ini away from package 9:9:9:10:11:12:php5-cli ucfr: Aborting. dpkg: error processing package php5-cli (--configure): subprocess installed post-installation script returned error exit status 4 Setting up libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.17) ... ucfr: Attempt from package libapache2-mod-php5 to take /etc/php5/apache2/php.ini away from package 7:7:7:7:8:9:libapache2-mod-php5 ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 The strange package names seem to be present in /var/lib/ucf/registry which I attach. Previous versions of the registry file in registry.1 et seq have fewer prepended numbers until registry.5 which has none. ** Affects: ucf (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/var/lib/ucf/registry" https://bugs.launchpad.net/bugs/1587464/+attachment/4673420/+files/infoscreentest-registry -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1587464 Title: ucf errors upgrading php5-cli and libapache2-mod-php5 Status in ucf package in Ubuntu: New Bug description: Ubuntu 14.04.3 LTS ucf package version: 3.0027+nmu1 Attempting to upgrade php5-cli and libapache2-mod-php5 packages produces the following error: Setting up php5-cli (5.5.9+dfsg-1ubuntu4.17) ... ucfr: Attempt from package php5-cli to take /etc/php5/cli/php.ini away from package 9:9:9:10:11:12:php5-cli ucfr: Aborting. dpkg: error processing package php5-cli (--configure): subprocess installed post-installation script returned error exit status 4 Setting up libapache2-mod-php5 (5.5.9+dfsg-1ubuntu4.17) ... ucfr: Attempt from package libapache2-mod-php5 to take /etc/php5/apache2/php.ini away from package 7:7:7:7:8:9:libapache2-mod-php5 ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 The strange package names seem to be present in /var/lib/ucf/registry which I attach. Previous versions of the registry file in registry.1 et seq have fewer prepended numbers until registry.5 which has none. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1587464/+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 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
@adconrad As it happens, it did. I just came back to update my comment to say so and found your question. This suggests the libc6 update (not glibc, my server doesn't have glibc package installed) should have required a reboot? I don't recall if the server mentioned a reboot was required in the motd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Status in eglibc package in Ubuntu: Confirmed Bug description: This morning I applied the following updates to Ubuntu 12.04 webservers: The following packages are currently pending an upgrade: apt 0.8.16~exp12ubuntu10.27 apt-transport-https 0.8.16~exp12ubuntu10.27 apt-utils 0.8.16~exp12ubuntu10.27 libapache2-mod-php5 5.3.10-1ubuntu3.23 libapt-inst1.4 0.8.16~exp12ubuntu10.27 libapt-pkg4.12 0.8.16~exp12ubuntu10.27 php5-cli 5.3.10-1ubuntu3.23 php5-common 5.3.10-1ubuntu3.23 php5-curl 5.3.10-1ubuntu3.23 php5-dev 5.3.10-1ubuntu3.23 php5-gd 5.3.10-1ubuntu3.23 php5-mysql 5.3.10-1ubuntu3.23 php-pear 5.3.10-1ubuntu3.23 Apache fails to restart, siting error: apache2: Syntax error on line 212 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modules/libphp5.so into server: /lib/x86_64-linux- gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Into file /var/log/apache2/error.log Looks like I am trying to roll back all those php packages... Which I see several updates marked Security Update in the changelogs, thus checking the "security vulnerability" box as rolling back in this case is such. :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+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 1585614] Re: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference
This change in libm.so has also broken the pam_mysql.so library, thus my vsftpd service is also broken. My nagios started alarming about this breaking around 6:30 am this morning, dpkg.log shows only 5 packages were updated in this morning's automatic update: man-db, libc-bin, libc6, and multiarch-support (all from amd64 arch.) The error in auth.log is: vsftpd: PAM unable to dlopen(pam_mysql.so): /lib/x86_64-linux-gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference. vsftpd: PAM adding faulty module: pam_mysql.so (I had to manually type the above, as MS hyperv can't do simple clipboard operations like Xen has managed for over a decade now. So please forgive any typos that might be there.) I don't think this is an apache or pam bug, as libm.so is provided by libc6. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1585614 Title: PHP Update on 2016-05-25 causes Apache not to restart, libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Status in eglibc package in Ubuntu: Confirmed Bug description: This morning I applied the following updates to Ubuntu 12.04 webservers: The following packages are currently pending an upgrade: apt 0.8.16~exp12ubuntu10.27 apt-transport-https 0.8.16~exp12ubuntu10.27 apt-utils 0.8.16~exp12ubuntu10.27 libapache2-mod-php5 5.3.10-1ubuntu3.23 libapt-inst1.4 0.8.16~exp12ubuntu10.27 libapt-pkg4.12 0.8.16~exp12ubuntu10.27 php5-cli 5.3.10-1ubuntu3.23 php5-common 5.3.10-1ubuntu3.23 php5-curl 5.3.10-1ubuntu3.23 php5-dev 5.3.10-1ubuntu3.23 php5-gd 5.3.10-1ubuntu3.23 php5-mysql 5.3.10-1ubuntu3.23 php-pear 5.3.10-1ubuntu3.23 Apache fails to restart, siting error: apache2: Syntax error on line 212 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modules/libphp5.so into server: /lib/x86_64-linux- gnu/libm.so.6: symbol __strtold_nan, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference Into file /var/log/apache2/error.log Looks like I am trying to roll back all those php packages... Which I see several updates marked Security Update in the changelogs, thus checking the "security vulnerability" box as rolling back in this case is such. :-( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1585614/+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 1509776] Re: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps
I also started seeing this problem after I upgraded to 15.10. I'll be typing and then the cursor will zip to one edge of the screen or the other. I'm on a Dell XPS 13 (2013 model). Currently seeing the issue with kernel 4.2.0-27 My current experiment is to kill syndaemon to see if palm detection is the issue, and then being really really sure that I'm not touching the touchpad while I type. -- 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/1509776 Title: xubuntu 15.10 synaptics ps2 touchpad mouse cursor jumps Status in xorg package in Ubuntu: Triaged Bug description: running live xubuntu 15.10 from usb stick. Synaptics ps2 touchpad configured to act as simple mouse. Mouse cursor suddenly and frequently jumps to screen edge with no reason. Problem not present in 15.04 with same touchpad configuration but has occurred in some earlier versions. Not prepared to upgrade as touchpad practically unusable. --- ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CasperVersion: 1.365 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: wily DistroRelease: Ubuntu 15.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Pegatron Device [1b0a:2109] Subsystem: Pegatron Device [1b0a:2109] LiveMediaBuild: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Novatech Ltd. Novatech 15.6 NSPIRE Laptop Package: xorg 1:7.7+7ubuntu4 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash --- persistent ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Tags: wily ubuntu UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C15B.610 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: C15B dmi.board.vendor: Novatech Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Novatech Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC15B.610:bd12/05/2013:svnNovatechLtd.:pnNovatech15.6NSPIRELaptop:pvr1.0:rvnNovatechLtd.:rnC15B:rvr1.0:cvnNovatechLtd.:ct10:cvr1.0: dmi.product.name: Novatech 15.6 NSPIRE Laptop dmi.product.version: 1.0 dmi.sys.vendor: Novatech Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Mon Nov 2 10:44:16 2015 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 (0) NOUVEAU(G0): Error initialising acceleration. Falling back to NoAccel xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18412 vendor AUO xserver.version: 2:1.17.2-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509776/+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 1520059] [NEW] ctrl-alt-f1 has no effect
Public bug reported: I am working in a stable install of Ubuntu 15.10. Everything seems to be working fine but I needed to install nvidia drivers. When I attempt to drop to terminal, as X must be off before I can do the install, I used ctrl-alt-f1 but nothing happens. I have rebooted multiple times and updated but this has had no effect. If I kill X manually I am dropped to something that looks like the boot- up sequence and can not type. I can use ctrl-alt-delete to reboot once I am there but nothing else seems to work. ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on my desktop PC running 15.10. Expected Results: ctrl-alt-f1 should drop me into a terminal where I can login. Actual Results: ctrl-alt-f1 does nothing, and system continues to operate in normal unity mode. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 25 21:45:43 2015 InstallationDate: Installed on 2015-10-24 (32 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily ** Description changed: - I am working in a stable install of Ubuntu 15.04. Everything seems to + I am working in a stable install of Ubuntu 15.10. Everything seems to be working fine but I needed to install nvidia drivers. When I attempt to drop to terminal, as X must be off before I can do the install, I used ctrl-alt-f1 but nothing happens. I have rebooted multiple times and updated but this has had no effect. If I kill X manually I am dropped to something that looks like the boot- up sequence and can not type. I can use ctrl-alt-delete to reboot once I am there but nothing else seems to work. ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on - my desktop PC running 15.04. + my desktop PC running 15.10. Expected Results: ctrl-alt-f1 should drop me into a terminal where I can login. Actual Results: ctrl-alt-f1 does nothing, and system continues to operate in normal unity mode. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 25 21:45:43 2015 InstallationDate: Installed on 2015-10-24 (32 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1520059 Title: ctrl-alt-f1 has no effect Status in util-linux package in Ubuntu: New Bug description: I am working in a stable install of Ubuntu 15.10. Everything seems to be working fine but I needed to install nvidia drivers. When I attempt to drop to terminal, as X must be off before I can do the install, I used ctrl-alt-f1 but nothing happens. I have rebooted multiple times and updated but this has had no effect. If I kill X manually I am dropped to something that looks like the boot-up sequence and can not type. I can use ctrl-alt-delete to reboot once I am there but nothing else seems to work. ctrl-alt-f1 works fine on my Ubuntu 15.04 macbook but does not work on my desktop PC running 15.10. Expected Results: ctrl-alt-f1 should drop me into a terminal where I can login. Actual Results: ctrl-alt-f1 does nothing, and system continues to operate in normal unity mode. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: util-linux 2.26.2-6ubuntu3 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed Nov 25 21:45:43 2015 InstallationDate: Installed on 2015-10-24 (32 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1520059/+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 1455710] [NEW] package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
Public bug reported: VM under VMWare Fusion 7.1. I used the Ubuntu Studio Meta Installer on top of a standard desktop to get this package. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 14 01:12:20 2015 DuplicateSignature: package:jackd2:1.9.10+20140719git3eb0ae6a~dfsg-2:subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2015-05-14 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: jackd2 Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: jackd2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package vivid -- 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/1455710 Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in jackd2 package in Ubuntu: New Bug description: VM under VMWare Fusion 7.1. I used the Ubuntu Studio Meta Installer on top of a standard desktop to get this package. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Thu May 14 01:12:20 2015 DuplicateSignature: package:jackd2:1.9.10+20140719git3eb0ae6a~dfsg-2:subprocess installed post-installation script was killed by signal (Terminated) ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2015-05-14 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: jackd2 Title: package jackd2 1.9.10+20140719git3eb0ae6a~dfsg-2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1455710/+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 1444226] Re: [Kubuntu 15.04 beta] can't connect to wifi with Ralink RT2561/RT61 and NetworkManager
OK, I just found your workaround here YAFU https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1442908/comments/4 This fixed the problem for me too, as wifi is stable using wicd it definitely seems to be a NetworkManager problem. -- 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/1444226 Title: [Kubuntu 15.04 beta] can't connect to wifi with Ralink RT2561/RT61 and NetworkManager Status in network-manager package in Ubuntu: Confirmed Bug description: Hello. I have a Ralink with RT2561/RT61 chip: $ lspci | grep -i network 05:00.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI In Kubuntu 15.04 my connection is very unstable using NetworkManager. Most of the time the connection is not established. And very few times the connection is established but after a few seconds the connection drops. Unfortunately in this new Kubuntu version if you try to uninstall "network-manager" then "plasma-desktop" is requested to be uninstalled (apparently because of "plasma-nm"). WORKAROUND: I installed Wicd from Kubuntu 14.04 using "chroot": 1- Start the system and try not use Network Manager 2- kill network manager $ sudo pkill -9 NetworkManager 3- Start wicd from "menu" > "internet" ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-14-generic 3.19.0-14.14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nulluser 1308 F pulseaudio /dev/snd/controlC0: nulluser 1308 F pulseaudio CurrentDesktop: KDE Date: Tue Apr 14 22:22:23 2015 HibernationDevice: RESUME=UUID=1edec07e-cb6e-4ca2-b03e-29d7ef434bc8 InstallationDate: Installed on 2015-04-12 (2 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150408) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-14-generic root=UUID=0f5fd4c5-56a1-494b-9513-074a3e1a11f1 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-14-generic N/A linux-backports-modules-3.19.0-14-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1444226/+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 1444226] Re: [Kubuntu 15.04 beta] can't connect to wifi with Ralink RT2561/RT61 and NetworkManager
Xubuntu here, wireless has been working fine over multi distros and years on this machine, just ran the 15.04 upgrade last night. Now I have exactly the same problem: initially connects but drops almost immediately and can't reconnect, completely unusable. $ lspci |grep -i network 04:06.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g -- 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/1444226 Title: [Kubuntu 15.04 beta] can't connect to wifi with Ralink RT2561/RT61 and NetworkManager Status in network-manager package in Ubuntu: Confirmed Bug description: Hello. I have a Ralink with RT2561/RT61 chip: $ lspci | grep -i network 05:00.0 Network controller: Ralink corp. RT2561/RT61 802.11g PCI In Kubuntu 15.04 my connection is very unstable using NetworkManager. Most of the time the connection is not established. And very few times the connection is established but after a few seconds the connection drops. Unfortunately in this new Kubuntu version if you try to uninstall "network-manager" then "plasma-desktop" is requested to be uninstalled (apparently because of "plasma-nm"). WORKAROUND: I installed Wicd from Kubuntu 14.04 using "chroot": 1- Start the system and try not use Network Manager 2- kill network manager $ sudo pkill -9 NetworkManager 3- Start wicd from "menu" > "internet" ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-14-generic 3.19.0-14.14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nulluser 1308 F pulseaudio /dev/snd/controlC0: nulluser 1308 F pulseaudio CurrentDesktop: KDE Date: Tue Apr 14 22:22:23 2015 HibernationDevice: RESUME=UUID=1edec07e-cb6e-4ca2-b03e-29d7ef434bc8 InstallationDate: Installed on 2015-04-12 (2 days ago) InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150408) MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-14-generic root=UUID=0f5fd4c5-56a1-494b-9513-074a3e1a11f1 ro quiet splash RelatedPackageVersions: linux-restricted-modules-3.19.0-14-generic N/A linux-backports-modules-3.19.0-14-generic N/A linux-firmware 1.143 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2204:bd08/14/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1444226/+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 1389167] Re: HostbasedAuthentication produces spurious warnings
Further still, a convenient workaround is to remove read permission for everyone from /etc/ssh/ssh_host_ed25519_key.pub -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1389167 Title: HostbasedAuthentication produces spurious warnings Status in “openssh” package in Ubuntu: New Bug description: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1389167/+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 1389167] Re: HostbasedAuthentication produces spurious warnings
Digging a bit further, I think this arises because ssh-keysign punts off all its host key processing to openSSL, but openSSL does not support ED25519 keys. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1389167 Title: HostbasedAuthentication produces spurious warnings Status in “openssh” package in Ubuntu: New Bug description: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1389167/+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 1389167] [NEW] HostbasedAuthentication produces spurious warnings
Public bug reported: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1389167 Title: HostbasedAuthentication produces spurious warnings Status in “openssh” package in Ubuntu: New Bug description: Ubuntu 14.04.1 LTS openssh-client 1:6.6p1-2ubuntu2 We have HostbasedAuthentication set up in our environment so that users can ssh between equivalent hosts without a password. ssh_config contains (relevantly) HostbasedAuthentication yes PreferredAuthentications publickey,hostbased,password,keyboard-interactive EnableSSHKeysign yes sshd_config contains (relevantly) HostbasedAuthentication yes This works: ocelot:~$ ssh othermc othermc:~$ However, ssh-ing as an alternative user produces additional warning messages before the expected password prompt: ocelot:~$ ssh otheruser@othermc no matching hostkey found ssh_keysign: no reply key_sign failed otheruser@othermc's password: If instead of relying on EnableSSHKeysign in ssh_config I make the ssh binary setuid: chmod u+s /usr/bin/ssh ...the extra warnings go away and I get what I expect: ocelot:~$ ssh otheruser@othermc otheruser@othermc's password: This makes me suspect that there may be a problem with ssh-keysign. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1389167/+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 1373930] [NEW] apt-key fails silently
Public bug reported: The apt-key command just returns to the command prompt with no output. I am sure it's failing or crashing silently. The scenario is that I am getting the pgdg-keyring /usr/bin/dpkg returned an error code (1) issue. Following the instructions in a forum posting I moved all the files from /etc/apt/trusted.gpg.d and re-ran apt-get update. This reported several unverified keys. I then started adding the keys by running apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys foo and noticed there was no output and it returned to the command prompt too quickly. Also no keys were added. Unfortunately moving all the .gpg files back into /etc/apt/trusted.gpg.d has left me with three unverified keys; http://apt.postgresql.org and two for http://ppa.launchpad.net. apt.postgresql seemed to be the key that was causing the original pgdg- keyring, but this could also be because it was the first in the list and all the others would also fail. Description:Ubuntu 14.04.1 LTS Release:14.04 Installed: 1.0.1ubuntu2.4.1 Candidate: 1.0.1ubuntu2.4.1 Version table: *** 1.0.1ubuntu2.4.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.1ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.4.1 Uname: Linux 3.17.0-031700rc6-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 25 13:39:01 2014 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373930 Title: apt-key fails silently Status in “apt” package in Ubuntu: New Bug description: The apt-key command just returns to the command prompt with no output. I am sure it's failing or crashing silently. The scenario is that I am getting the pgdg-keyring /usr/bin/dpkg returned an error code (1) issue. Following the instructions in a forum posting I moved all the files from /etc/apt/trusted.gpg.d and re-ran apt-get update. This reported several unverified keys. I then started adding the keys by running apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv- keys foo and noticed there was no output and it returned to the command prompt too quickly. Also no keys were added. Unfortunately moving all the .gpg files back into /etc/apt/trusted.gpg.d has left me with three unverified keys; http://apt.postgresql.org and two for http://ppa.launchpad.net. apt.postgresql seemed to be the key that was causing the original pgdg-keyring, but this could also be because it was the first in the list and all the others would also fail. Description: Ubuntu 14.04.1 LTS Release: 14.04 Installed: 1.0.1ubuntu2.4.1 Candidate: 1.0.1ubuntu2.4.1 Version table: *** 1.0.1ubuntu2.4.1 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.1ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.4.1 Uname: Linux 3.17.0-031700rc6-lowlatency x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 CurrentDesktop: KDE Date: Thu Sep 25 13:39:01 2014 SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1373930/+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 276837] Re: Evince does not properly render some files
This is still present in 0.24.5-2ubuntu4 even though the patch in #10 has been applied in the source. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/276837 Title: Evince does not properly render some files Status in Poppler: Fix Released Status in “poppler” package in Ubuntu: Fix Released Bug description: Binary package hint: evince Some files are not properly rendered by evince, it misses lots of lines. I'm attaching a sample To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/276837/+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
