[Touch-packages] [Bug 1787324] Re: Snap policy module denies recording access to classic snaps
** Merge proposal linked: https://code.launchpad.net/~ubuntu-audio-dev/pulseaudio/+git/pulseaudio/+merge/353214 -- 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/1787324 Title: Snap policy module denies recording access to classic snaps Status in pulseaudio package in Ubuntu: Confirmed Bug description: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787324] [NEW] Snap policy module denies recording access to classic snaps
Public bug reported: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. ** Affects: pulseaudio (Ubuntu) Importance: High Assignee: James Henstridge (jamesh) Status: Confirmed -- 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/1787324 Title: Snap policy module denies recording access to classic snaps Status in pulseaudio package in Ubuntu: Confirmed Bug description: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787320] [NEW] After update Ethernet not working - Connection failed
Public bug reported: In a fresh ubuntu 18.04 installation after running: sudo apt-get update sudo apt-get upgrade Ethernet stopped working and I'm receiving the error: Connection failed - "Activation of network connection failed" This was the packages I upgraded: Start-Date: 2018-08-15 23:19:08 Commandline: apt-get upgrade Upgrade: python3-distupgrade:amd64 (1:18.04.17, 1:18.04.24), ubuntu-release-upgrader-core:amd64 (1:18.04.17, 1:18.04.24), gnome-initial-setup:amd64 (3.28.0-2ubuntu6, 3.28.0-2ubuntu6.16.04.1), ubuntu-release-upgrader-gtk:amd64 (1:18.04.17, 1:18.04.24), unattended-upgrades:amd64 (1.1ubuntu1, 1.1ubuntu1.18.04.5) End-Date: 2018-08-15 23:19:11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:32:57 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.133.32.1 dev wlp2s0 proto dhcp metric 600 10.133.32.0/21 dev wlp2s0 proto kernel scope link src 10.133.32.75 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICETYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0wifi connected /org/freedesktop/NetworkManager/Devices/3 WeWork 94a3cf50-7615-4dea-8d44-9692e3663ceb /org/freedesktop/NetworkManager/ActiveConnection/2 docker0 bridgeconnected /org/freedesktop/NetworkManager/Devices/4 docker0 23ad18e4-d80b-4d1d-bd3c-d2d5b8d1d284 /org/freedesktop/NetworkManager/ActiveConnection/3 enp3s0f1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- loloopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1787320 Title: After update Ethernet not working - Connection failed Status in network-manager package in Ubuntu: New Bug description: In a fresh ubuntu 18.04 installation after running: sudo apt-get update sudo apt-get upgrade Ethernet stopped working and I'm receiving the error: Connection failed - "Activation of network connection failed" This was the packages I upgraded: Start-Date: 2018-08-15 23:19:08 Commandline: apt-get upgrade Upgrade: python3-distupgrade:amd64 (1:18.04.17, 1:18.04.24), ubuntu-release-upgrader-core:amd64 (1:18.04.17, 1:18.04.24), gnome-initial-setup:amd64 (3.28.0-2ubuntu6, 3.28.0-2ubuntu6.16.04.1), ubuntu-release-upgrader-gtk:amd64 (1:18.04.17, 1:18.04.24), unattended-upgrades:amd64 (1.1ubuntu1, 1.1ubuntu1.18.04.5) End-Date: 2018-08-15 23:19:11 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 15 23:32:57 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-08-16 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 10.133.32.1 dev wlp2s0 proto dhcp metric 600 10.133.32.0/21 dev wlp2s0 proto kernel scope link src 10.133.32.75 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: nmcli-dev: DEVICETYPE STATE
[Touch-packages] [Bug 1786574] Re: remove i2c-i801 from blacklist
** Changed in: kmod (Ubuntu Cosmic) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1786574 Title: remove i2c-i801 from blacklist Status in HWE Next: New Status in kmod package in Ubuntu: New Status in kmod source package in Xenial: New Status in kmod source package in Bionic: New Status in kmod source package in Cosmic: New Bug description: We have a Lenovo Thinkpad machine that requires i2c-i801 kernel module to work, but it is listed in /etc/modprobe/blacklist.conf in Ubuntu. To use the touchpad, users have to remove the i2c-i801 line manually. i2c-i801 in blacklist.conf is a very old workaround to fix HP compaq nc6000 (Bug #16602), this module should be removed from blacklist. There is also another bug (Bug #1475945) that needs this module for Acer trackpad to work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1786574/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787115] Re: No display on hdmi1
You seem to be using unsupported graphics drivers from LP-PPA-paulo- miguel-dias-pkppa Please: 1. Install 'ppa-purge'. 2. Use it to remove the PPA from from your system. 3. See if the bug still happens. 4. If it still happens then open a new bug by running: ubuntu-bug xorg-server ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- 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/1787115 Title: No display on hdmi1 Status in xorg-server package in Ubuntu: Invalid Bug description: Hdmi1 and sound on Hdmi1 not working. In ubuntu 16.04 it was working perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 Uname: Linux 4.15.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 15 13:14:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-31-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-26-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3975] InstallationDate: Installed on 2017-12-31 (226 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO HuronRiver Platform ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-31-generic root=UUID=06c9bcee-717f-4abd-aff0-9f3b1d431be5 ro acpi = force Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN43WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 3 22:21:54 2018 xserver.configfile: /etc/X11/xorg.conf xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
I'm not sure what the right component to assign this bug is. To progress this issue please open a bug with the GTK developers here: https://gitlab.gnome.org/GNOME/gtk/issues and the let us know the new bug ID. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787294] Re: ".ico" icon files are shown as random noise
If nautilus also shows noise then this is a lower level bug, not in gnome-shell. Reassigning to GTK to start with... ** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1787294 Title: ".ico" icon files are shown as random noise Status in gtk+3.0 package in Ubuntu: New Bug description: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1787294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787294] [NEW] ".ico" icon files are shown as random noise
You have been subscribed to a public bug: Steps to reproduce Create an .ico file (for using the same icon between multiple platforms) create a desktop file linking to the ico file. here is an example of the one that doesn't work [Desktop Entry] Type=Application Version=0.9.4 Name=ChromisPos Comment=Chromis Point of Sale Icon=/opt/chromispos/pos.ico Exec=/opt/chromispos/start.sh Terminal=false Path=/opt/chromispos gnome-shell (possibly dashtodock) displays this icon as a wash of noise. (see screenshot) In 16.04 the .ico works fine, and switching to Unity desktop also shows the .ico just fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 00:29:47 2018 DisplayManager: lightdm GsettingsChanges: b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2015-11-15 (1004 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- ".ico" icon files are shown as random noise https://bugs.launchpad.net/bugs/1787294 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
The error message still exists in the latest (12.2) PulseAudio:
pa_log("Module \"%s\" should be loaded once at most. Refusing to load.",
name);
errcode = -PA_ERR_EXIST;
goto fail;
So if it seems fixed then that probably means the KDE/Kubuntu side got
fixed.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Won't Fix
--
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/1720519
Title:
KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once
at most. Refusing to load.
Status in PulseAudio:
Confirmed
Status in pulseaudio package in Ubuntu:
Won't Fix
Bug description:
Pulseaudio daemon does not start after the update to Kubuntu 17.10
beta2, because the module fails to load although it is there.
From 'pulseaudio -vv'
E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded
once at most. Refusing to load.
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.
PS sorry I am not a seasoned bug reporter. Let me know if I can
provide more info.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC0D0p: ben2809 F...m chrome
/dev/snd/controlC0: ben2809 F chrome
/dev/snd/timer: ben2809 f chrome
CurrentDesktop: KDE
Date: Sat Sep 30 11:20:55 2017
InstallationDate: Installed on 2017-04-07 (175 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago)
dmi.bios.date: 10/29/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: B150M-ITX
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787272] [NEW] Administrators are not added to adm group
Public bug reported: Currently administrators are only added to the sudo group. This was fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/810907, but there has likely been a regression. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1787272 Title: Administrators are not added to adm group Status in accountsservice package in Ubuntu: New Bug description: Currently administrators are only added to the sudo group. This was fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source /gnome-control-center/+bug/810907, but there has likely been a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1787272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
THank you Egor! that did the trick on Kubuntu 18.04. Now if I could only figure out why it disconnects from the VPN after .5-2 hours... -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Triaged Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777010] Re: ip token set, results in: Invalid argument
I think, it is because the token is already set? https://www.mail-archive.com/netdev@vger.kernel.org/msg103122.html maybe someone have a good contact to Daniel Borkmann? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1777010 Title: ip token set, results in: Invalid argument Status in iproute2 package in Ubuntu: Confirmed Bug description: Hi, I can't set any ipv6 token with ip command. It seems that it has a bug. Also it is not possible to set it with netplan (see bug #1737976) ~# ip token list token :: dev enp1s0 token :: dev enp2s0 token :: dev ovpn0 token :: dev br0 ~# ip token set ::2a:2a:2a:2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::2a/64 dev br0 RTNETLINK answers: Invalid argument ~# ip token set ::beef dev br0 RTNETLINK answers: Invalid argument It seems, that this Bug is really old?! https://bbs.archlinux.org/viewtopic.php?id=202757 This is really fatal, because I cant set a static ip. My prefix get mixed from my provider every x days. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Fri Jun 15 01:26:04 2018 InstallationDate: Installed on 2018-06-12 (2 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1777010/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786940] Re: Enable arm-linux-gnueabi target on ppc64el toolchain
This bug was fixed in the package binutils - 2.31.1-3ubuntu2 --- binutils (2.31.1-3ubuntu2) cosmic; urgency=medium * Build armel and armhf cross binutils on ppc64el. LP: #1786940. binutils (2.31.1-3ubuntu1) cosmic; urgency=medium * Merge with Debian; remaining changes: - Build from upstream sources. binutils (2.31.1-3) unstable; urgency=medium * Snapshot, taken from the 2.31 branch (20180814). - Fix PR ld/23428, properly add X86_ISA_1_NEEDED property. - Fix PR ld/23486, properly merge GNU_PROPERTY_X86_ISA_1_USED. - x32: Align the .note.gnu.property section to 4 bytes. - PowerPC64 __tls_get_addr_opt stub .eh_frame fix. - PowerPC64: __tls_get_addr_opt stubs and tocsave optimization. - PR gas/23465, x86: don't mistakenly scale non-8-bit displacements. - PR gold/23455, add --warn-drop-version option; by default, do not warn when discarding version info. - hppa: Fix unwind offset for call_info->start_symbol. * Build arm64 cross binutils on ppc64el. -- Matthias Klose Tue, 14 Aug 2018 18:28:27 +0200 ** Changed in: binutils (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1786940 Title: Enable arm-linux-gnueabi target on ppc64el toolchain Status in The Ubuntu-power-systems project: Triaged Status in binutils package in Ubuntu: Fix Released Status in gcc-7-cross package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-defaults package in Ubuntu: Incomplete Bug description: Dear Canonical. We would like to have arm-linux-gnueabi target on ppc64el cross toolchain. This would enable us to use a ppc64el host to do cross compilation for aarch64. I talked to Matthias Klose already, and he is aware of this request. Thank you, Breno To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1786940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Phillip: I don't know why they even allow you to speak on this thread. Please stop spreading misinformation . Your gdm3 / XAUTHORITY "bug" has been closed as obsolete, it does not work the way you envision. https://bugzilla.gnome.org/show_bug.cgi?id=789867 Yes it was migrated, but there is no acknowledgement in the new location that your gdm3 / XAUTHORITY "bug" is going to get addressed in the new location and, as with your other "bugs", will be closed . The other "bug" you claimed earlier was closed as "not a bug" https://bugs.freedesktop.org/show_bug.cgi?id=91071 Your continued comments on the subject are misleading at best -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost
[Touch-packages] [Bug 1787238] [NEW] package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Public bug reported: plusieurs applications n'ont pas été chargées et ne se sont pas installées correctement lors de la mise à niveau d'ubuntu mais je n'ai pas les compétences techniques pour décrire davantage les problèmes ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 15 06:11:15 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-03-05 (1624 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1787238 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: plusieurs applications n'ont pas été chargées et ne se sont pas installées correctement lors de la mise à niveau d'ubuntu mais je n'ai pas les compétences techniques pour décrire davantage les problèmes ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 15 06:11:15 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-03-05 (1624 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786629] Re: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
It looks like grub tried to ask a question and debconf ran the gtk frontend and somehow dropped you to a subshell, which you typed exit from, then the gtk frontend errored out, causing the grub script to return the error. ** Package changed: grub2 (Ubuntu) => debconf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1786629 Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 Status in debconf package in Ubuntu: New Bug description: while upgrading to Ubantu 18.04 version pc hanged and it did not orked even after leaving for hours ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.2 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Aug 11 22:33:39 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-30 (103 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=51e2afee-e9ee-4527-adf4-853e7c5827d5 ro acpi_rev_override quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1786629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786629] [NEW] package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1
You have been subscribed to a public bug: while upgrading to Ubantu 18.04 version pc hanged and it did not orked even after leaving for hours ProblemType: Package DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64 2.02-2ubuntu8.2 ProcVersionSignature: Ubuntu 4.4.0-131.157-generic 4.4.134 Uname: Linux 4.4.0-131-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sat Aug 11 22:33:39 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-30 (103 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-131-generic.efi.signed root=UUID=51e2afee-e9ee-4527-adf4-853e7c5827d5 ro acpi_rev_override quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 apt 1.6.3 SourcePackage: grub2 Title: package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-08-11 (0 days ago) ** Affects: debconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- package grub-efi-amd64 2.02-2ubuntu8.2 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1 https://bugs.launchpad.net/bugs/1786629 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786465] Re: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
You have a broken third party init script named ".depend.boot" and ".depend.start" that you will need to remove. ** Changed in: util-linux (Ubuntu) Status: New => Invalid -- 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/1786465 Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: Invalid Bug description: I dont know, it was a automatic update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.6 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Aug 9 11:57:45 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-02-26 (164 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1786465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766542] Re: Installation blocks when the machine is behind a proxy server
** Changed in: ubiquity (Ubuntu) Status: Incomplete => Confirmed ** Changed in: ubiquity (Ubuntu) Status: Confirmed => Fix Released -- 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/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Fix Released Status in apt package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in apt source package in Bionic: Fix Released Status in ubiquity source package in Bionic: New Bug description: [Impact] APT takes a long time to notice when certain connections time out [Test case] * Change the default route to not route stuff successfully (wrong gateway, for example) * Make your sources.list look like this: deb http://archive.ubuntu.com/ubuntu bionic main restricted deb http://archive.ubuntu.com/ubuntu bionic-updates main restricted * Run apt update You should see that it fails with a long verbose error message for the first entry, with all possible IP addresses listed in it; while for the second one it fails with just "Unable to connect to archive.ubuntu.com:http:" as it recognizes it has been blacklisted. [Regression potential] APT will not attempt to retry the host given that it could not connect to it for previous entries. If your network recovered in the meantime, it might update less than previously. [Original bug report] When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
On 8/6/2018 12:57 PM, PeterPall wrote: > This isn't a bug but a major feature of wayland: If you have root rights > you no more get access to the graphical user interface which makes it > harder for a gui application to spy on another application's keyboard > input. The backdraw of this is that every application that needs root > rights for its work has to be re-written to have 2 parts: No Peter, this is incorrect. Wayland is just fine with programs running as root. The bug is in gdm3 which is supposed to generate an Xorg configuration that sets up XAUTHORITY. Instead when it configures the Xwayland X11 compatibility server, it configures it to check UID instead of using XAUTHORITY. The result is that X11 apps running as root fail to work, but native Wayland/GTK3 applications run as root work just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*&perpkg=1&page=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: ca
[Touch-packages] [Bug 1783757] Re: shrinking previous file systems makes them corrupted
** Package changed: ubiquity (Ubuntu) => e2fsprogs (Ubuntu) ** Changed in: e2fsprogs (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1783757 Title: shrinking previous file systems makes them corrupted Status in e2fsprogs package in Ubuntu: New Bug description: Booted in UEFI mode, running test example 'Install (auto-resize) in Kubuntu Desktop amd64 in Bionic Daily' the previous file system was shrunk in order to create space for the current one. But it was corrupted and must be fixed. Workaround: sudo e2fsck -f /dev/sda2 The same thing happened when booted in UEFI mode, running test example 'Install (manual partitioning) in Kubuntu Desktop amd64 in Bionic Daily' Workaround: sudo e2fsck -f /dev/sda3 (This current operating system's file system was fixed and made bootable again.) --- tester@tester-SATELLITE-PRO-C850-19W:~$ sudo parted -ls [sudo] password for tester: Model: ATA KINGSTON SUV400S (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 2098kB 317MB 315MB fat32 boot, esp 2 317MB 20,3GB 20,0GB ext4 3 20,3GB 45,9GB 25,6GB ext4 4 45,9GB 107GB 61,4GB ext4 tester@tester-SATELLITE-PRO-C850-19W:~$ sudo lsblk -fm NAME FSTYPE LABEL UUID MOUNTPOINT SIZE OWNER GROUP MODE sda 111,8G root disk brw-rw ├─sda1 vfat 6106-B035/boot/efi300M root disk brw-rw ├─sda2 ext4 d6df56de-4490-4508-beb4-8259dda193c4 18,6G root disk brw-rw ├─sda3 ext4 e375e0d6-e162-4136-af21-377a635761a8 / 23,9G root disk brw-rw └─sda4 ext4 646734a2-45bf-4000-815e-31bbafcdfd29 57,2G root disk brw-rw sr0 1024M root cdrom brw-rw tester@tester-SATELLITE-PRO-C850-19W:~$ ubuntu-bug ubiquity --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 26 14:01:38 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --- InstallationDate: Installed on 2018-07-26 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1783757/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787225] [NEW] systemctl disable apache2 does nothing
Public bug reported: I installed apache2 on Ubuntu 16.04, and out of the box it was enabled as a service, meaning it would automatically start at every boot. That is not what I want as this is my personal computer, not a server. $ systemctl is-enabled apache2.service enabled So I ran: $ sudo systemctl disable apache2 and this was the output: apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable apache2 insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Then I rebooted. I expected to find apache2 not running. Instead, it was running. Surprisingly: $ systemctl is-enabled apache2.service apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled apache2 disabled so, it shows up as disabled, yet it is started at startup. I wonder if this is what those warnings were about. Those messages are unclear as fuck, I have no f***ing clue what they are supposed to mean. I read that the CURRENT runlevel overrides a DEFAULT. I guess that should be fine, unless what systemctl actually changes are the defaults, and those are overwritten by something else, which means that "sysctl disable" will have no effect. If that is the case, then the warning should be more explicit: - be specific about the fact that "LSB defaults" are what the command is changing - tell me that as a result, the services will not be disabled - tell me WHAT is overriding the defaults that I'm attempting to change - and/or tell me what I am supposed to do to fix the issue ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 4.4.0-133.159-generic 4.4.134 Uname: Linux 4.4.0-133-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 15 16:26:28 2018 InstallationDate: Installed on 2013-10-11 (1768 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-133-generic.efi.signed root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.name: Aspire V3-571G dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- 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/1787225 Title: systemctl disable apache2 does nothing Status in systemd package in Ubuntu: New Bug description: I installed apache2 on Ubuntu 16.04, and out of the box it was enabled as a service, meaning it would automatically start at every boot. That is not what I want as this is my personal computer, not a server. $ systemctl is-enabled apache2.service enabled So I ran: $ sudo systemctl disable apache2 and this was the output: apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install disable apache2 insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). insserv: warning: current start runlevel(s) (empty) of script `apache2' overrides LSB defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overrides LSB defaults (0 1 6). Then I rebooted. I expected to find apache2 not running. Instead, it was running. Surprisingly: $ systemctl is-enabled apache2.service apache2.service is not a native service, redirecting to systemd-sysv-install Executing /lib/systemd/systemd-sysv-install is-enabled apache2 disabled so, it shows up as disabled, yet it is started at startup.
[Touch-packages] [Bug 1134036] Re: Failure when using ssh with a locale that is not configured on the server
This bug was fixed in the package base-files - 10.1ubuntu5 --- base-files (10.1ubuntu5) cosmic; urgency=medium * Install locale-check command to /usr/bin and invoke it from /etc/profile.d/01-locale-fix.sh to ensure locale related environment variables are set to valid values. (LP: #1134036) -- Michael Hudson-Doyle Tue, 07 Aug 2018 11:53:28 +1200 ** Changed in: base-files (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: Fix Released Status in maas package in Ubuntu: Invalid Bug description: If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783757] [NEW] shrinking previous file systems makes them corrupted
You have been subscribed to a public bug: Booted in UEFI mode, running test example 'Install (auto-resize) in Kubuntu Desktop amd64 in Bionic Daily' the previous file system was shrunk in order to create space for the current one. But it was corrupted and must be fixed. Workaround: sudo e2fsck -f /dev/sda2 The same thing happened when booted in UEFI mode, running test example 'Install (manual partitioning) in Kubuntu Desktop amd64 in Bionic Daily' Workaround: sudo e2fsck -f /dev/sda3 (This current operating system's file system was fixed and made bootable again.) --- tester@tester-SATELLITE-PRO-C850-19W:~$ sudo parted -ls [sudo] password for tester: Model: ATA KINGSTON SUV400S (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: Number Start End SizeFile system Name Flags 1 2098kB 317MB 315MB fat32 boot, esp 2 317MB 20,3GB 20,0GB ext4 3 20,3GB 45,9GB 25,6GB ext4 4 45,9GB 107GB 61,4GB ext4 tester@tester-SATELLITE-PRO-C850-19W:~$ sudo lsblk -fm NAME FSTYPE LABEL UUID MOUNTPOINT SIZE OWNER GROUP MODE sda 111,8G root disk brw-rw ├─sda1 vfat 6106-B035/boot/efi300M root disk brw-rw ├─sda2 ext4 d6df56de-4490-4508-beb4-8259dda193c4 18,6G root disk brw-rw ├─sda3 ext4 e375e0d6-e162-4136-af21-377a635761a8 / 23,9G root disk brw-rw └─sda4 ext4 646734a2-45bf-4000-815e-31bbafcdfd29 57,2G root disk brw-rw sr0 1024M root cdrom brw-rw tester@tester-SATELLITE-PRO-C850-19W:~$ ubuntu-bug ubiquity --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE Date: Thu Jul 26 14:01:38 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --- InstallationDate: Installed on 2018-07-26 (0 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: e2fsprogs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic iso-testing ubiquity-18.04.14.6 -- shrinking previous file systems makes them corrupted https://bugs.launchpad.net/bugs/1783757 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745664] Re: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_cln
Agreed. I don't know if it technically qualifies as a duplicate. But I suspect its caused by the same systemd change. -- 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/1745664 Title: [regression] systemd-logind crashed with SIGABRT in __libc_connect() from __GI_clnttcp_create() from __GI___libc_rpc_getport() from __GI_pmap_getport() from __GI_clnttcp_create() Status in nis package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/54968dedd418de647365aa3f0127906ca9adbfe3 --- configured system to use nis. seems to be crashing when I attempt to use a NIS user account ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 Date: Fri Jan 26 13:45:06 2018 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2018-01-26 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. Z370 HD3 ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: __libc_connect (fd=39, addr=addr@entry=..., len=len@entry=16) at ../sysdeps/unix/sysv/linux/connect.c:26 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=10, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27301efc, sendsz=sendsz@entry=400, recvsz=recvsz@entry=400) at clnt_tcp.c:153 __GI___libc_rpc_getport (tottimeout_sec=60, timeout_sec=5, protocol=6, version=2, program=17, address=0x7ffc27302060) at pm_getport.c:106 __GI_pmap_getport (address=address@entry=0x7ffc27302060, program=program@entry=17, version=version@entry=2, protocol=protocol@entry=6) at pm_getport.c:154 __GI_clnttcp_create (raddr=raddr@entry=0x7ffc27302060, prog=prog@entry=17, vers=vers@entry=2, sockp=sockp@entry=0x7ffc27302050, sendsz=sendsz@entry=0, recvsz=recvsz@entry=0) at clnt_tcp.c:136 SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: systemd-logind crashed with SIGABRT in __libc_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: Software adm bin daemon lp mail nuucp root scswebadmin sys sysdesign tty uucp dmi.bios.date: 09/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: Z370 HD3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd09/22/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ370HD3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370HD3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 HD3 dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/1745664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1200009] Re: HP 1102 does not print
Hello, I haven't access to that device now, and not interested in solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/129 Title: HP 1102 does not print Status in cups package in Ubuntu: Incomplete Bug description: In printer status i see error message Printer "HP-LaserJet- Professional-p1102": "hplip.plugin" orlan@orlan-i5-3570k:~$ cupsd cupsd: Child exited on signal 15 orlan@orlan-i5-3570k:~$ orlan@orlan-i5-3570k:~$ lsb_release -rd Description: Ubuntu 13.04 Release: 13.04 orlan@orlan-i5-3570k:~$ apt-cache policy cups cups: Установлен: 1.6.2-1ubuntu7 Кандидат: 1.6.2-1ubuntu7 Таблица версий: *** 1.6.2-1ubuntu7 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.6.2-1ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages orlan@orlan-i5-3570k:~$ apt-cache policy cups hplip cups: Установлен: 1.6.2-1ubuntu7 Кандидат: 1.6.2-1ubuntu7 Таблица версий: *** 1.6.2-1ubuntu7 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring-proposed/main amd64 Packages 100 /var/lib/dpkg/status 1.6.2-1ubuntu5 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages hplip: Установлен: 3.13.3-1 Кандидат: 3.13.3-1 Таблица версий: *** 3.13.3-1 0 500 http://ru.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cups 1.6.2-1ubuntu7 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 Date: Thu Jul 11 09:05:57 2013 InstallationDate: Installed on 2013-09-07 (-58 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) Lpstat: device for HP-LaserJet-Professional-p1102: smb://1/SMIRNOF/HP%20LaserJet%20Professional%20P1102 MachineType: System manufacturer System Product Name MarkForUpload: True Papersize: a4 PpdFiles: HP-LaserJet-Professional-p1102: HP LaserJet Professional p1102, hpcups 3.13.3, requires proprietary plugin ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-27-generic root=UUID=2713a651-6fe1-43a6-ae53-9d453172ecdc ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B75-M 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.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M: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/cups/+bug/129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1762384] Re: libgpgme-dev installs libgpgme-pthread.so in /usr/lib/${DEB_HOST_MULTIARCH}, literally
** Tags added: id-5b72f74a5a43864c2f8d1a10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1762384
Title:
libgpgme-dev installs libgpgme-pthread.so in
/usr/lib/${DEB_HOST_MULTIARCH}, literally
Status in gpgme1.0 package in Ubuntu:
Fix Committed
Status in gpgme1.0 source package in Bionic:
In Progress
Bug description:
[Impact]
In Bionic, libgpgme-pthread.so it is installed in
/usr/lib/${DEB_HOST_MULTIARCH} instead of /usr/lib/x86_64-linux-gnu (the
variable is not replaced)
[Test case]
Check that package installs to correct location
[Regression potential]
Packages looking for libgpgme-pthread find it now and might enable gpgme when
they did not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1762384/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] Re: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: aptitude (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in aptitude package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785703] Re: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785703 Title: appstreamcli:13472): GLib-CRITICAL **: 16:15:30.753: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in aptitude package in Ubuntu: Confirmed Status in glib2.0 package in Ubuntu: Confirmed Bug description: Hello, I'm working with aptitude and message... Regards, -- Cristian Aravena Romero (caravena) https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 Uname: Linux 4.18.0-041800rc8-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:20:12 2018 InstallationDate: Installed on 2017-10-13 (297 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1785703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786635] Re: (appstreamcli:8218): GLib-CRITICAL error on exit of apt-get update
*** This bug is a duplicate of bug 1785498 *** https://bugs.launchpad.net/bugs/1785498 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apt (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1786635 Title: (appstreamcli:8218): GLib-CRITICAL error on exit of apt-get update Status in apt package in Ubuntu: Confirmed Bug description: # sudo apt-get update Get:1 http://archive.ubuntu.com/ubuntu cosmic InRelease [242 kB] Hit:2 http://archive.canonical.com/ubuntu cosmic InRelease Hit:3 http://archive.ubuntu.com/ubuntu cosmic-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu cosmic-security InRelease Hit:5 http://archive.ubuntu.com/ubuntu cosmic-backports InRelease Get:6 http://archive.ubuntu.com/ubuntu cosmic/universe Sources [9310 kB] Get:7 http://archive.ubuntu.com/ubuntu cosmic/main amd64 DEP-11 Metadata [470 kB] Get:8 http://archive.ubuntu.com/ubuntu cosmic/main DEP-11 48x48 Icons [120 kB] Get:9 http://archive.ubuntu.com/ubuntu cosmic/main DEP-11 64x64 Icons [243 kB] Get:10 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages [8764 kB] Get:11 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 DEP-11 Metadata [3320 kB] Get:12 http://archive.ubuntu.com/ubuntu cosmic/universe DEP-11 48x48 Icons [2464 kB] Get:13 http://archive.ubuntu.com/ubuntu cosmic/universe DEP-11 64x64 Icons [8480 kB] Get:14 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 DEP-11 Metadata [48.4 kB] Get:15 http://archive.ubuntu.com/ubuntu cosmic/multiverse DEP-11 64x64 Icons [221 kB] Fetched 33.7 MB in 13s (2607 kB/s) (appstreamcli:8218): GLib-CRITICAL **: 20:12:55.088: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Reading package lists... Done The GLib-CRITICAL message sounds like there should be something done about it. It does not appear when everything is completely up to date (and consequently to "Fetched ..." message appears either). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apt 1.7.0~alpha2 ProcVersionSignature: Ubuntu 4.17.0-6.7-lowlatency 4.17.9 Uname: Linux 4.17.0-6-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Aug 11 20:14:01 2018 InstallationDate: Installed on 2011-10-14 (2493 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111011) SourcePackage: apt UpgradeStatus: Upgraded to cosmic on 2018-07-30 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1786635/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4
This bug in systemd-networkd is affecting our environment also.
We have an RFC-compliant DHCP server that does not reply with Option 54
"Server Identifier". We have made the point to other vendors that this
is indeed compliant with the RFC because there is no routable address to
the DHCP server so it is not possible to send this option and also stay
in line with the RFC.
For context, the reason there is no routable address as this server
works in a cloud environment where it impersonates a server in multiple
VLANs that belong to customers. It cannot use addresses in those
subnets.
`To accommodate potentially incomplete network connectivity, a server MUST
choose an address as a 'server identifier' that, to the best of the server's
knowledge, is reachable from the client.`
This is the reason why its not possible to send the option in the DHCPOFFER as
there is no such address.
There is good support for this implementation from other software such as the
ISC dhclient and from Windows.
--
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/1779721
Title:
systemd-networkd does not configure DHCPv4
Status in netplan.io package in Ubuntu:
Invalid
Status in systemd package in Ubuntu:
Confirmed
Bug description:
I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
systemd 237-3ubuntu10) which has following netplan configuration:
```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
all:
match: {}
dhcp4: yes
root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network
[Match]
[Network]
DHCP=ipv4
[DHCP]
UseMTU=true
RouteMetric=100
```
Despite having DHCPv4 configured, no IPv4 address is configured on the
ethernet device:
```
root@ubuntu:~# ip a show ens6
2: ens6: mtu 64000 qdisc fq_codel state UP
group default qlen 1000
link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
inet6 fe80::1:71ff:fe8f:cc72/64 scope link
valid_lft forever preferred_lft forever
```
The kernel dmesg has no related messages and the journal log also
looks normal:
```
root@ubuntu:~# journalctl -u systemd-networkd
Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
```
Calling dhclient sets up the device correctly:
```
root@ubuntu:~# dhclient ens6
root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
}
root@ubuntu:~# ip a show ens6
2: ens6: mtu 64000 qdisc fq_codel state UP
group default qlen 1000
link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
valid_lft forever preferred_lft forever
inet6 fe80::1:71ff:fe8f:cc72/64 scope link
valid_lft forever preferred_lft forever
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439784] Re: [apport-kde] apport-collect: Can not import module PyQt5.QtCore
I can confirm that this does not work in 14.04 as these packages don't exist there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1439784 Title: [apport-kde] apport-collect: Can not import module PyQt5.QtCore Status in apport package in Ubuntu: Fix Released Bug description: I had to use apport-collect in a tty, because in kde it is not usable: benedikt@benediktZ50-70 ~ % apport-collect 1439694 ERROR: Could not import module, is a package upgrade in progress? Error: No module named PyQt5.QtCore System : Kubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1439784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787120] Re: apt show fails to show large records
** Changed in: apt (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787120 Title: apt show fails to show large records Status in apt package in Ubuntu: New Status in apt source package in Bionic: New Status in apt package in Debian: Confirmed Bug description: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest. [Other info] This is a duplicate of Debian bug #905527. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787120] [NEW] apt show fails to show large records
Public bug reported: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest. [Other info] This is a duplicate of Debian bug #905527. ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: apt (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #905527 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905527 ** Also affects: apt (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905527 Importance: Unknown Status: Unknown ** Also affects: apt (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787120 Title: apt show fails to show large records Status in apt package in Ubuntu: New Status in apt source package in Bionic: New Status in apt package in Debian: Unknown Bug description: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest. [Other info] This is a duplicate of Debian bug #905527. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I also had this problem after upgrading to 17.10 and solved it with commenting out load-module module-switch-on-connect in /etc/pulse/default.pa. When upgrading to 18.04 I opt for replacing the /etc/pulse/default.pa so the setting is back, but I don't have this issue, so it's fixed for me in 18.04. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787115] [NEW] No display on hdmi1
Public bug reported: Hdmi1 and sound on Hdmi1 not working. In ubuntu 16.04 it was working perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 Uname: Linux 4.15.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 15 13:14:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-31-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-26-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3975] InstallationDate: Installed on 2017-12-31 (226 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO HuronRiver Platform ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-31-generic root=UUID=06c9bcee-717f-4abd-aff0-9f3b1d431be5 ro acpi = force Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 44CN43WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Emerald Lake dmi.board.vendor: LENOVO dmi.board.version: FAB1 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvrLenovoB570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: HuronRiver Platform dmi.product.version: Lenovo B570 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 3 22:21:54 2018 xserver.configfile: /etc/X11/xorg.conf xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1787115 Title: No display on hdmi1 Status in xorg package in Ubuntu: New Bug description: Hdmi1 and sound on Hdmi1 not working. In ubuntu 16.04 it was working perfectly. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-31.33-generic 4.15.18 Uname: Linux 4.15.0-31-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Aug 15 13:14:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-31-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-26-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3975] InstallationDate: Installed on 2017-12-31 (226 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO HuronRiver Platform ProcEnviron: PATH=(custom, no user) LANG=en_US.
[Touch-packages] [Bug 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
I think so, yes. -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786821] Re: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux
Full ACK -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1786821 Title: pam.7.gz is a symlink to PAM.7.gz . This does not work for caseinsensitive filesystems e.g. Windows Subsystem for Linux Status in pam package in Ubuntu: Won't Fix Bug description: The package libpam-runtime contains a symlink pam.7.gz -> PAM.7.gz in ./usr/share/man/man7 and this doesn't work in Windows Subsystem for Linux since Windows has a caseinsensitive filesystem. On ubuntu 18.04 this PAM.7.gz exists too. I know it's not a linux centric issue. But why libpam-runtime is using Uppercase and symlinks anyway? Other packgages in man7 just use lowercase, and this is what I'm expecting. Hopefully you can fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1786821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
