[Touch-packages] [Bug 2063078] [NEW] USB devices not detected
Public bug reported:
In some cases the kernel does detect a newly connected USB device, but
this device is never handled by systemd. The device handling shows up in
dmesg, but no device /dev/sd.. entries are created to access this newly
connected storage device.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Mon Apr 22 08:13:26 2024
InstallationDate: Installed on 2011-10-19 (4568 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4:
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
--
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4:
Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to mantic on 2019-04-27 (1822 days ago)
dmi.bios.date: 10/21/2013
dmi.bios.release: 2.15
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TravelMate P643-M
dmi.board.vendor: Acer
dmi.board.version: V2.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.15
dmi.ec.firmware.release: 1.19
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15:
dmi.product.family: TravelMate P643-M
dmi.product.name: TravelMate P643-M
dmi.product.sku: TravelMate P643-M_0681_2.15
dmi.product.version: V2.15
dmi.sys.vendor: Acer
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug mantic
--
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/2063078
Title:
USB devices not detected
Status in systemd package in Ubuntu:
New
Bug description:
In some cases the kernel does detect a newly connected USB device, but
this device is never handled by systemd. The device handling shows up
in dmesg, but no device /dev/sd.. entries are created to access this
newly connected storage device.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: systemd 253.5-1ubuntu6.1
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Mon Apr 22 08:13:26 2024
InstallationDate: Installed on 2011-10-19 (4568 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-28-generic
root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios
crashkernel=384M-2G:128M,2G-:256M vt.handoff=7
SourcePackage: systemd
SystemdFailedUnits:
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
--
Error: command ['systemctl', 'status', '--full', '●'] failed with exit code
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use
systemd-escape?).
Unit \xe2\x97\x8f.service could not be found.
UpgradeStatus: Upgraded to mantic on 2019-04-27 (1822 days ago)
dmi.bios.date: 10/21/2013
dmi.bios.release: 2.15
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.15
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TravelMate P643-M
dmi.board.vendor: Acer
dmi.board.version: V2.15
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.15
dmi.ec.firmware.release: 1.19
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15:
dmi.product.family: TravelMate P643-M
dmi.product.name: TravelMate P643-M
dmi.product.sku: TravelMate P643-M_0681_2.15
dmi.product.version: V2.15
dmi.sys.vendor: Acer
To manage notifications about this bug go
[Touch-packages] [Bug 2046650] [NEW] pcscd starts, then from applications all readers connected wont work
Public bug reported: pcscd starts, then all readers connected are listed, but wont work. starting pcsc_scan will never finish scanning, waiting on pcscd returning data. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pcscd 1.9.9-1ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Dec 17 13:52:28 2023 InstallationDate: Installed on 2011-10-19 (4441 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago) ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2046650 Title: pcscd starts, then from applications all readers connected wont work Status in pcsc-lite package in Ubuntu: New Bug description: pcscd starts, then all readers connected are listed, but wont work. starting pcsc_scan will never finish scanning, waiting on pcscd returning data. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pcscd 1.9.9-1ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Dec 17 13:52:28 2023 InstallationDate: Installed on 2011-10-19 (4441 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2046650/+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 2046650] Re: pcscd starts, then from applications all readers connected wont work
# pcscd --foreground --info --color debuglog.c:386:DebugLogSetLevel() debug level=info 0040 pcscdaemon.c:356:main() Force colored logs 0381 pcscdaemon.c:666:main() pcsc-lite 1.9.9 daemon ready. 00013684 hotplug_libudev.c:421:HPAddDevice() Adding USB device: REINER SCT cyberJack wave 0068 readerfactory.c:1093:RFInitializeReader() Attempting startup of REINER SCT cyberJack wave (3428049512) 00 00 using /usr/lib/pcsc/drivers/libifd-cyberjack.bundle/Contents/Linux/libifd-cyberjack.so CYBERJACK: Started 1582 readerfactory.c:968:RFBindFunctions() Loading IFD Handler 3.0 Same for some other readers. While pcscd ist starting they are reported, but starting pcsc_scan just prints $ pcsc_scan PC/SC device scanner V 1.6.2 (c) 2001-2022, Ludovic Rousseau then doing nothing more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/2046650 Title: pcscd starts, then from applications all readers connected wont work Status in pcsc-lite package in Ubuntu: New Bug description: pcscd starts, then all readers connected are listed, but wont work. starting pcsc_scan will never finish scanning, waiting on pcscd returning data. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pcscd 1.9.9-1ubuntu0.23.04.1 ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.26.1-0ubuntu2.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Dec 17 13:52:28 2023 InstallationDate: Installed on 2011-10-19 (4441 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: pcsc-lite UpgradeStatus: Upgraded to lunar on 2019-04-27 (1694 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/2046650/+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 2042749] [NEW] apt does not work with given convig files in new format
Public bug reported: assume /etc/apt/sources.list.d/somerepo.list: Types: deb URIs: https://repo.vivaldi.com/stable/deb/ Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg /etc/apt/trusted.gpg.d/4218647E.gpg Then 'apt update' will produce: # apt update E: Type 'Types:' is not known on line 4 in source list /etc/apt/sources.list.d/vivaldi.list E: The list of sources could not be read. A new apt version is available. Would be nice to upgrade. At the moment "man sources.list" does describe a file format not accepted by apt in sources.list-files. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 23:51:50 2023 InstallationDate: Installed on 2021-12-11 (693 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=de_DE.UTF-8 LANGUAGE=de_DE PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2042749 Title: apt does not work with given convig files in new format Status in apt package in Ubuntu: New Bug description: assume /etc/apt/sources.list.d/somerepo.list: Types: deb URIs: https://repo.vivaldi.com/stable/deb/ Suites: stable Components: main Architectures: amd64 Signed-By: /etc/apt/trusted.gpg.d/33EAAB8E.gpg /etc/apt/trusted.gpg.d/4218647E.gpg Then 'apt update' will produce: # apt update E: Type 'Types:' is not known on line 4 in source list /etc/apt/sources.list.d/vivaldi.list E: The list of sources could not be read. A new apt version is available. Would be nice to upgrade. At the moment "man sources.list" does describe a file format not accepted by apt in sources.list-files. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: apt 2.7.3 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 23:51:50 2023 InstallationDate: Installed on 2021-12-11 (693 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: LANG=de_DE.UTF-8 LANGUAGE=de_DE PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2042749/+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 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
I can't reproduce this issue on impish or jammy. It was fixed by a change in handling sockets in systemd. On Mon, May 9, 2022 at 6:25 PM Paride Legovini <1957...@bugs.launchpad.net> wrote: > > Hello Thomas. You filed this bug against: > > DistroRelease: Ubuntu 21.10 > Package: openssh-server 1:8.4p1-6ubuntu2.1 > > By "Solved by a later version of systemd and sshd". Do you mean that you > found you can't reproduce the issue on Jammy (22.04 LTS)? Can you still > reproruce the issue on Impish? Thank you. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1957104 > > Title: > updating openssh-server fails, because port 22 is in use by systemd > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+subscriptions > -- Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
xubuntu and kubuntu, as lubuntu do use pipewire for audio. kali switched last night to use it. openSUSE did so too. i did not test on a plain vanilla gnome based ubuntu until now. Will do it later this day (if time permits). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
These modules seem to collide with pipewire-media-session, but are required by bluez-stack to connect bluetooth headsets (or other devices) to pulseaudio. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968875] Re: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect
Meanwhile even the distros working until yesterday stopped working today (5. May 2022 around 22:00). The bug seems related to pipewire and switching to this new infrastructure. It breaks nearly everything related with sound and bluetooth. Modules involved: - pipewire-pulse - wireplumber -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: [Intel 7265][ThinkPad T450s] Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968028] Re: unattended-upgrades if enabled wont disable interactivemode
Solved by a new version of upgrade tools. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1968028 Title: unattended-upgrades if enabled wont disable interactivemode Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1968028/+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 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
Solved by a later version of systemd and sshd. To have it work as intended sshd has to be compiled with different options set. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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 1915707] Re: keyboard settings not applied
Solved with a later version of required packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1915707 Title: keyboard settings not applied Status in console-setup package in Ubuntu: Fix Released Bug description: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1915707/+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 1852474] Re: cups not printing if authentication required by server
Solved upstream with later versions of cups. -- 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/1852474 Title: cups not printing if authentication required by server Status in cups package in Ubuntu: Confirmed Bug description: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1852474/+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 1856187] Re: Cups wont print to smb-shared printer requiring user authentication via kerberos
Solved upstream with later versions of cups -- 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/1856187 Title: Cups wont print to smb-shared printer requiring user authentication via kerberos Status in cups package in Ubuntu: New Bug description: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not true: the printer requires authentication. Maybe a bug. This print server requires any user to be authenticated and have a kerberos ticket. This is true. The user has a kerberos ticket and this user is allowed to print. The users kerberos ticket cache is available in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it into account. May be a bug too. Changing "AuthInfoRequired" from "none" to "username,password" allows cups to print. But this has to be done editing /etc/cups/printers.conf. The web printer configuration just does not allow to set anything else than "none". This is a bug. Documentation misses what "AuthInfoRequired" has to be set for if kerberos authentication will be used. This is a bug too! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 13:54:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856187/+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 1971534] [NEW] connecting bluetooth devices fails
Public bug reported: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1971534 Title: connecting bluetooth devices fails Status in bluez package in Ubuntu: New Bug description: Bluetooth devices do not connect. Or better: they connect, disconnect, connect, then finally disconnect. It is the same using graphical tools or cli. It is the same for - ubuntu, kubuntu, xubuntu, versions 20.04 LTS, 21.10, 22.04 LTS, 22.10 (beta) - debian 11.3 - fedora 35 Working distros are: - kali (latest rolling) - openSUSE Leap 15.4 - openSUSE tumbleweed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed May 4 08:57:30 2022 InstallationDate: Installed on 2021-08-18 (258 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-27-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:4581 acl:7 sco:0 events:435 errors:0 TX bytes:46460 acl:7 sco:0 commands:399 errors:0 To manage notifications about this bug go to:
[Touch-packages] [Bug 1968875] [NEW] Bluetooth devices disconnect, connect, disconnect
Public bug reported: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1968875 Title: Bluetooth devices disconnect, connect, disconnect Status in bluez package in Ubuntu: New Bug description: Paired Bluetooth devices are connected, then disconnected, connected again, then finally disconected. This is with - Ubuntu, xUbuntu 21.10 - Ubuntu, xUbuntu 22.04(beta) It works with - kali (latest) - debian 11.3 (latest) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.64-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Wed Apr 13 13:31:07 2022 InstallationDate: Installed on 2021-08-18 (238 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20BWS33U00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_sxscpx@/vmlinuz-5.15.0-25-generic root=ZFS=rpool/ROOT/ubuntu_sxscpx ro splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2015 dmi.bios.release: 1.17 dmi.bios.vendor: LENOVO dmi.bios.version: JBET52WW (1.17 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS33U00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnLENOVO:bvrJBET52WW(1.17):bd08/12/2015:br1.17:efr1.1:svnLENOVO:pn20BWS33U00:pvrThinkPadT450s:rvnLENOVO:rn20BWS33U00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20BW_BU_Think_FM_ThinkPadT450s: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS33U00 dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 4C:34:88:AE:51:86 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:3994 acl:7 sco:0 events:403 errors:0 TX bytes:46327 acl:7 sco:0 commands:367 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1968875/+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 1968028] Re: unattended-upgrades if enabled wont disable interactivemode
This can be seen with - 16.04 - 18.04 - 20.04 - 21.10 - 22.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1968028 Title: unattended-upgrades if enabled wont disable interactivemode Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1968028/+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 1968028] [NEW] unattended-upgrades if enabled wont disable interactivemode
Public bug reported: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1968028 Title: unattended-upgrades if enabled wont disable interactivemode Status in unattended-upgrades package in Ubuntu: New Bug description: unattended-upgrades if enabled wont disable interactive mode. In tune an unattended upgrade stops waiting for input never to expect, because the dialog displayed is never seen by anyone. Updates will not be installed at all in some cases. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: unattended-upgrades 2.8ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Apr 6 12:27:22 2022 InstallationDate: Installed on 2021-08-18 (231 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1968028/+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 1957104] Re: updating openssh-server fails, because port 22 is in use by systemd
sshd is started by systemd. No special configurations besides defaults by Ubuntu/xUbuntu. Only change in /etc/ssh/sshd_config: "PermitRootLogin prohibit-password" -> "PermitRootLogin yes" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: Incomplete Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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 1963825] [NEW] udev does not create devices plugged into USB 3.0 ports
Public bug reported: Hotplugging devices into USB 3.0/1/2 Ports does not create devices in /dev. The plugged device is not accessible afterwards. This is for all of them: USB-Disks (HD, CDROM, Tapes), USB to serial converters, Audio, Video, Cameras. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udev 248.3-1ubuntu8.2 ProcVersionSignature: Ubuntu 5.13.0-32.35-generic 5.13.19 Uname: Linux 5.13.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 49-micronucleus.rules 70-snap.core.rules 51-android.rules 70-snap.chromium.rules Date: Sun Mar 6 16:55:19 2022 InstallationDate: Installed on 2011-10-19 (3790 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-32-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to impish on 2019-04-27 (1044 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- 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/1963825 Title: udev does not create devices plugged into USB 3.0 ports Status in systemd package in Ubuntu: New Bug description: Hotplugging devices into USB 3.0/1/2 Ports does not create devices in /dev. The plugged device is not accessible afterwards. This is for all of them: USB-Disks (HD, CDROM, Tapes), USB to serial converters, Audio, Video, Cameras. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udev 248.3-1ubuntu8.2 ProcVersionSignature: Ubuntu 5.13.0-32.35-generic 5.13.19 Uname: Linux 5.13.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CustomUdevRuleFiles: 49-micronucleus.rules 70-snap.core.rules 51-android.rules 70-snap.chromium.rules Date: Sun Mar 6 16:55:19 2022 InstallationDate: Installed on 2011-10-19 (3790 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-32-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to impish on 2019-04-27 (1044 days ago) dmi.bios.date: 10/21/2013 dmi.bios.release: 2.15 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:br2.15:efr1.19:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15:skuTravelMateP643-M_0681_2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1963825/+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 1961849] Re: bluetooth connects with headset, deconects, connects, deconnects
Start-Date: 2022-02-21 01:16:18 Commandline: apt -y upgrade Requested-By: tps (1000) Upgrade: firefox-locale-en:amd64 (97.0+build2-0ubuntu1, 97.0.1+build1-0ubuntu1), dmeventd:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), udev:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf-nobfd0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), systemd-container:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libqmi-proxy:amd64 (1.30.2-1, 1.30.4-1), gir1.2-snapd-1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), systemd-timesyncd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libpam-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libarchive13:amd64 (3.5.2-1, 3.5.2-1ubuntu1), openmpi-bin:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), libbinutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libfwupd2:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libsnapd-glib1:amd64 (1.58-4ubuntu1, 1.60-0ubuntu1), openmpi-common:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), liblvm2cmd2.03:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libsystemd0:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libsystemd0:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), binutils-x86-64-linux-gnu:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libnss-systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), systemd:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libudev1:i386 (249.9-0ubuntu2, 249.10-0ubuntu1), lvm2:amd64 (2.03.11-2.1ubuntu3, 2.03.11-2.1ubuntu4), libnss-mymachines:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libctf0:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), dmsetup:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), python3-pil.imagetk:amd64 (9.0.0-1, 9.0.1-1), libhypre-2.22.1:amd64 (2.22.1-6, 2.22.1-7), libdevmapper-event1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils-common:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), libqmi-glib5:amd64 (1.30.2-1, 1.30.4-1), python3-pil:amd64 (9.0.0-1, 9.0.1-1), libopenmpi3:amd64 (4.1.2-1ubuntu1, 4.1.2-1ubuntu2), systemd-sysv:amd64 (249.9-0ubuntu2, 249.10-0ubuntu1), libfwupdplugin5:amd64 (1.7.4-1ubuntu1, 1.7.5-3), libdevmapper1.02.1:amd64 (2:1.02.175-2.1ubuntu3, 2:1.02.175-2.1ubuntu4), binutils:amd64 (2.38-1ubuntu1, 2.38-2ubuntu1), fwupd:amd64 (1.7.4-1ubuntu1, 1.7.5-3) End-Date: 2022-02-21 01:18:20 Start-Date: 2022-02-21 01:18:24 Commandline: apt -y dist-upgrade Requested-By: tps (1000) Install: libnfsidmap1:amd64 (1:2.6.1-1~exp1ubuntu1, automatic) Upgrade: nfs-common:amd64 (1:1.3.4-6ubuntu1, 1:2.6.1-1~exp1ubuntu1) Remove: libnfsidmap2:amd64 (0.25-6build1) End-Date: 2022-02-21 01:18:28 Start-Date: 2022-02-22 07:07:20 Commandline: apt -y upgrade Requested-By: tps (1000) Install: polkitd:amd64 (0.105-32, automatic), pkexec:amd64 (0.105-32, automatic) Upgrade: libpolkit-agent-1-0:amd64 (0.105-31.1, 0.105-32), libsmartcols1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), debconf-i18n:amd64 (1.5.79, 1.5.79ubuntu1), apt:amd64 (2.3.15, 2.3.15build1), packagekit-tools:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libxcb-image0:amd64 (0.4.0-1build2, 0.4.0-2), zfs-zed:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libpipewire-0.3-common:amd64 (0.3.45-1, 0.3.47-1ubuntu1), zfs-initramfs:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), libaom3:amd64 (3.2.0-2, 3.3.0-1), libjpeg-turbo8:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libjpeg-turbo8:i386 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libnvpair3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), grub-pc-bin:amd64 (2.06-2ubuntu4, 2.06-2ubuntu5), libapt-pkg6.0:amd64 (2.3.15, 2.3.15build1), libuutil3linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), debconf:amd64 (1.5.79, 1.5.79ubuntu1), libmount1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libmount1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libzpool5linux:amd64 (2.1.2-1ubuntu2, 2.1.2-1ubuntu3), system-config-printer-udev:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), pipewire:amd64 (0.3.45-1, 0.3.47-1ubuntu1), libqpdf28:amd64 (10.5.0-1, 10.6.2-1), gir1.2-packagekitglib-1.0:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), util-linux:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libjpeg-turbo-progs:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), fdisk:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libfdisk1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), system-config-printer-common:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3), eject:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), packagekit:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), libturbojpeg:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libuuid1:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), libuuid1:i386 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), make:amd64 (4.3-4ubuntu2, 4.3-4.1build1), uuid-runtime:amd64 (2.37.2-4ubuntu1, 2.37.2-4ubuntu3), grub-efi-amd64-signed:amd64 (1.177+2.06-2ubuntu4, 1.178+2.06-2ubuntu5), libjpeg-turbo8-dev:amd64 (2.1.1-0ubuntu1, 2.1.2-0ubuntu1), libpolkit-gobject-1-0:amd64 (0.105-31.1, 0.105-32), gir1.2-polkit-1.0:amd64 (0.105-31.1, 0.105-32), libpackagekit-glib2-18:amd64 (1.2.4-1ubuntu2, 1.2.5-1ubuntu1), pipewire-bin:amd64 (0.3.45-1, 0.3.47-1ubuntu1), system-config-printer:amd64 (1.5.15-2ubuntu1, 1.5.16-0ubuntu3),
[Touch-packages] [Bug 1961849] [NEW] bluetooth connects with headset, deconects, connects, deconnects
Public bug reported: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1961849 Title: bluetooth connects with headset, deconects, connects, deconnects Status in bluez package in Ubuntu: New Bug description: bluetooth connects with headset, then times out, deconnects. Forcing it to connect again it does, then times out and deconnects again. Seen this with: - Cyber jack - Phonak Hearing Aids - Sennheiser Headset Since it worked until Feb. 21st, 2022 latest fixes applied at 18:00. And stopped working after Feb. 22nd, 2022 latest fixes applied at 21:00. One of the packages updated produced the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: bluez 5.63-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu77 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Feb 22 23:18:09 2022 InstallationDate: Installed on 2021-12-11 (73 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FAS16K00 ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_vwfg3u@/vmlinuz-5.15.0-18-generic root=ZFS=rpool/ROOT/ubuntu_vwfg3u ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2021 dmi.bios.release: 1.52 dmi.bios.vendor: LENOVO dmi.bios.version: N1CET84W (1.52 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FAS16K00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN1CET84W(1.52):bd07/08/2021:br1.52:efr1.14:svnLENOVO:pn20FAS16K00:pvrThinkPadT460s:rvnLENOVO:rn20FAS16K00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20FA_BU_Think_FM_ThinkPadT460s: dmi.product.family: ThinkPad T460s dmi.product.name: 20FAS16K00 dmi.product.sku: LENOVO_MT_20FA_BU_Think_FM_ThinkPad T460s dmi.product.version: ThinkPad T460s dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 34:F3:9A:EE:2A:4A ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:18813 acl:14 sco:0 events:2736 errors:0 TX bytes:606658 acl:14 sco:0 commands:2675 errors:0 To manage
[Touch-packages] [Bug 1957104] [NEW] updating openssh-server fails, because port 22 is in use by systemd
Public bug reported: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1957104 Title: updating openssh-server fails, because port 22 is in use by systemd Status in openssh package in Ubuntu: New Bug description: openssh-server tries to restart itself, but openssh-server reports port 22 in use. This is true: systemd has taken port 22 to start sshd if one connects to port 22. two solutions: 1. dont start sshd after installing. configure it without starting it afterwards. 2. stop systemd listening on port 22 before starting sshd, then start sshd, terminate it after configuring, then start systemd listening on port 22 again. Second problem: starting ssh.service does not check if "/run/sshd" exists. This directory has to be created before sshd is started. Unclear if this is an error with sshd not creating this directory before dropping privileges or if this has to be done once while installing. IMHO the first is the case. Workaround: systemctl stop ssh.service systemctl disable ssh.service apt upgrade systemctl enable ssh.service killall sshd mkdir /run/sshd systemctl start ssh.service ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: openssh-server 1:8.4p1-6ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 11 19:11:47 2022 InstallationDate: Installed on 2021-08-18 (146 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /run/sshd SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1957104/+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 1915748] [NEW] dnsmasq wont resolve dns
Public bug reported: dnsmasq ist set up to resolve DNS names with a local, static file given at /etc/dnsmasq-resolv.conf: # cat /etc/dnsmasq-resolv.conf nameserver 10.161.18.34 nameserver 10.177.18.34 nameserver 10.129.90.10 nameserver 10.160.90.10 nameserver 10.161.90.10 search All servers given can be reached: # host google.com 10.161.18.34 Using domain server: Name: 10.161.18.34 Address: 10.161.18.34#53 Aliases: google.com has address 216.58.213.238 google.com has IPv6 address 2a00:1450:4005:80a::200e google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. Within /etc/resolv.conf: nameserver 127.0.0.1 search trying to resolve a name using local bound dnsmasq on any of the bound addresses: dnsmasq 24106 dnsmasq6u IPv4 184802 0t0 UDP 172.18.8.1:53 dnsmasq 24106 dnsmasq7u IPv4 184803 0t0 TCP 172.18.8.1:53 (LISTEN) dnsmasq 24106 dnsmasq9u IPv4 184805 0t0 UDP 172.18.2.1:53 dnsmasq 24106 dnsmasq 10u IPv4 184806 0t0 TCP 172.18.2.1:53 (LISTEN) dnsmasq 24106 dnsmasq 12u IPv4 184808 0t0 UDP 172.18.1.1:53 dnsmasq 24106 dnsmasq 13u IPv4 184809 0t0 TCP 172.18.1.1:53 (LISTEN) dnsmasq 24106 dnsmasq 15u IPv4 184811 0t0 UDP 127.0.0.1:53 dnsmasq 24106 dnsmasq 16u IPv4 184812 0t0 TCP 127.0.0.1:53 (LISTEN) # host google.com 127.0.0.1 ;; connection timed out; no servers could be reached # host google.com 172.18.8.1 ;; connection timed out; no servers could be reached # host google.com 172.18.1.1 ;; connection timed out; no servers could be reached # host google.com 172.18.2.1 ;; connection timed out; no servers could be reached Names wont be resolved. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: dnsmasq 2.82-1ubuntu2 [modified: etc/dnsmasq.conf] ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 15 19:31:14 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to hirsute on 2018-11-23 (815 days ago) mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 mtime.conffile..etc.dnsmasq.conf: 2021-02-15T18:38:52.895027 ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1915748 Title: dnsmasq wont resolve dns Status in dnsmasq package in Ubuntu: New Bug description: dnsmasq ist set up to resolve DNS names with a local, static file given at /etc/dnsmasq-resolv.conf: # cat /etc/dnsmasq-resolv.conf nameserver 10.161.18.34 nameserver 10.177.18.34 nameserver 10.129.90.10 nameserver 10.160.90.10 nameserver 10.161.90.10 search All servers given can be reached: # host google.com 10.161.18.34 Using domain server: Name: 10.161.18.34 Address: 10.161.18.34#53 Aliases: google.com has address 216.58.213.238 google.com has IPv6 address 2a00:1450:4005:80a::200e google.com mail is handled by 10 aspmx.l.google.com. google.com mail is handled by 40 alt3.aspmx.l.google.com. google.com mail is handled by 30 alt2.aspmx.l.google.com. google.com mail is handled by 20 alt1.aspmx.l.google.com. google.com mail is handled by 50 alt4.aspmx.l.google.com. Within /etc/resolv.conf: nameserver 127.0.0.1 search trying to resolve a name using local bound dnsmasq on any of the bound addresses: dnsmasq 24106 dnsmasq6u IPv4 184802 0t0 UDP 172.18.8.1:53 dnsmasq 24106 dnsmasq7u IPv4 184803 0t0 TCP 172.18.8.1:53 (LISTEN) dnsmasq 24106 dnsmasq9u IPv4 184805 0t0 UDP 172.18.2.1:53 dnsmasq 24106 dnsmasq 10u IPv4 184806 0t0 TCP 172.18.2.1:53 (LISTEN) dnsmasq 24106 dnsmasq 12u IPv4 184808 0t0 UDP 172.18.1.1:53 dnsmasq 24106 dnsmasq 13u IPv4 184809 0t0 TCP 172.18.1.1:53 (LISTEN) dnsmasq 24106 dnsmasq 15u IPv4 184811 0t0 UDP 127.0.0.1:53 dnsmasq 24106 dnsmasq 16u IPv4 184812 0t0 TCP 127.0.0.1:53 (LISTEN) # host google.com 127.0.0.1 ;; connection timed out; no servers could be reached # host google.com 172.18.8.1 ;; connection timed out; no servers could be reached
[Touch-packages] [Bug 1915746] [NEW] systemd-resolved configuration does not resolve any hostnames
Public bug reported: systemd-resolved will, unter certain circumstances create local only DNS resolution: # host google.com ;; connection timed out; no servers could be reached looking at what is going on behind: # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf) nameserver 127.0.0.1 nameserver 127.0.0.53 searchDOMAINS # systemd-resolve --status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 DNS Domain: DOMAINS Link 2 (eth0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Domain: DOMAINS Link 3 (virbr0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (vmnet1) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 5 (vmnet2) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 6 (vmnet8) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported This is a useless configuration: dnsmasq asks systemd-resolvd, systemd- resolvd asks dnsmasq. Without ever going to any of the upstream servers. One of them: systemd-resolvd or dnsmasq shall ask upstream servers. But non of them does. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 15 19:16:05 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-36-generic root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ consoleblank=0 video=DP-1:e,HDMI-1:e SourcePackage: systemd UpgradeStatus: Upgraded to hirsute on 2018-11-23 (815 days ago) dmi.bios.date: 11/10/2011 dmi.bios.release: 2.15 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1497 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:br2.15:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 6200 Pro MT PC dmi.product.sku: XL504AV dmi.sys.vendor: Hewlett-Packard mtime.conffile..etc.systemd.resolved.conf: 2021-02-15T19:09:12.129281 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute 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/1915746 Title: systemd-resolved configuration does not resolve any hostnames Status in systemd package in Ubuntu: New Bug description: systemd-resolved will, unter certain circumstances create local only DNS resolution: # host google.com ;; connection timed out; no servers could be reached looking at what is going on behind: # cat /etc/resolv.conf (linked to /run/resolvconf/resolv.conf) nameserver 127.0.0.1 nameserver 127.0.0.53 searchDOMAINS # systemd-resolve --status Global Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported resolv.conf mode: foreign Current DNS Server: 127.0.0.1 DNS Servers: 127.0.0.1 DNS Domain: DOMAINS Link 2 (eth0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported DNS Domain: DOMAINS Link 3 (virbr0) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 4 (vmnet1) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 5 (vmnet2) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported Link 6 (vmnet8) Current Scopes: none Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported This is a useless configuration: dnsmasq asks systemd-resolvd, systemd-resolvd asks dnsmasq. Without ever going to any of the upstream servers. One of them: systemd-resolvd or dnsmasq shall ask upstream servers. But non of them does. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: systemd 247.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult:
[Touch-packages] [Bug 1915707] [NEW] keyboard settings not applied
Public bug reported: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1915707 Title: keyboard settings not applied Status in console-setup package in Ubuntu: New Bug description: Global keyboard settings are set in /etc/defaults/keyboard: XKBMODEL="pc105" XKBLAYOUT="de" XKBVARIANT="" XKBOPTIONS="lv3:ralt_switch,compose:menu,terminate:ctrl_alt_bksp" BACKSPACE="guess" These settings are not active any more after upgrading from focal to groovy. Same applies if upgrading from groovy to hirsute. The file /etc/defaults/keyboard is untouched, but any console uses an US keyboard. Same applies for X11-Sessions: all users have their keyboard defaulted to US layout. Any other layouts configured for any user vanishes. Configurations have to be done again as it they never where set. For all users settings -> Keyboard -> Keyboard Layout is set to use system-wide keyboard settings. This is set to US layout. This seems not changeable at all! If this depends on file /etc/defaults/keyboard. It does not respect this file. There has to be a way to set some other keyboard layout system-wide. Not only for one session or one user! And: this setting shall not be overwritten by upgrading. And it shall not be ignored after upgrading! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: console-setup 1.195ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 15 12:10:46 2021 InstallationDate: Installed on 2014-01-31 (2572 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to groovy on 2018-11-23 (814 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1915707/+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 1902721] [NEW] xrandr fails to set screen size while starting X11
Public bug reported: while starting X11 xrandr executes commands: xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync xrandr --addmode DP-1 "3840x2160_30.00" xrandr --output DP-1 --mode "3840x2160_30.00" while newmode, addmode work, the third command fails with "xrandr: Configure crtc 0 failed". Looking at all video interfaces, the mode added to DP-1 is there. Now, from some remote shell: DISPLAY=:0.0 xrandr --output DP-1 --mode 3840x2160_30.00 does not fail, but set graphics mode as desired. Trying to pause this to give it more time does not help. Does not work. It works as soon as i log in, set display to ":0.0" and then give the xrandr-command to use and set DP-1 to the desired mode. Removing all xrandr-commands does not help either: the display stays black. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-common 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompositorRunning: None Date: Tue Nov 3 14:52:24 2020 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: 2018-11-23 16:21:56,549 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:1497] InstallationDate: Installed on 2014-01-31 (2468 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Hewlett-Packard HP Compaq 6200 Pro MT PC PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-52-generic root=UUID=de4af024-5d59-4f85-b5ca-11f17f085706 ro rootflags=subvol=@ consoleblank=0 video=DP-1:3840x2160M-32@30e SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2018-11-23 (710 days ago) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie Error executing command as another user: Not authorized This incident has been reported. dmi.bios.date: 11/10/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.15 dmi.board.name: 1497 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.15:bd11/10/2011:svnHewlett-Packard:pnHPCompaq6200ProMTPC:pvr:rvnHewlett-Packard:rn1497:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq 6200 Pro MT PC dmi.product.sku: XL504AV dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal 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/1902721 Title: xrandr fails to set screen size while starting X11 Status in xorg package in Ubuntu: New Bug description: while starting X11 xrandr executes commands: xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync xrandr --addmode DP-1 "3840x2160_30.00" xrandr --output DP-1 --mode "3840x2160_30.00" while newmode, addmode work, the third command fails with "xrandr: Configure crtc 0 failed". Looking at all video interfaces, the mode added to DP-1 is there. Now, from some remote shell: DISPLAY=:0.0 xrandr --output DP-1 --mode 3840x2160_30.00 does not fail, but set graphics mode as desired. Trying to pause this to give it more time does not help. Does not work. It works as soon as i log in, set display to ":0.0" and then give the xrandr-command to use and set DP-1 to the desired mode. Removing all xrandr-commands does not help either: the display stays black. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: x11-common 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux
[Touch-packages] [Bug 1893838] [NEW] ubuntu-bug shall try to find the package a command belongs to
Public bug reported: ubuntu-bug shall try to find a package a command belongs to if the given name does not match an installed package. Now: # ubuntu-bug ubuntu-bug dpkg-query: Kein Paket gefunden, das auf ubuntu-bug passt ubuntu-bug shall do in such cases: - look for the package: # dpkg -S $( which ubuntu-bug ) apport: /usr/bin/ubuntu-bug and then use "apport" to generate the report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.8 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 1 21:32:23 2020 InstallationDate: Installed on 2011-10-19 (3240 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2019-04-27 (493 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1893838 Title: ubuntu-bug shall try to find the package a command belongs to Status in apport package in Ubuntu: New Bug description: ubuntu-bug shall try to find a package a command belongs to if the given name does not match an installed package. Now: # ubuntu-bug ubuntu-bug dpkg-query: Kein Paket gefunden, das auf ubuntu-bug passt ubuntu-bug shall do in such cases: - look for the package: # dpkg -S $( which ubuntu-bug ) apport: /usr/bin/ubuntu-bug and then use "apport" to generate the report. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.8 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportLog: ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Sep 1 21:32:23 2020 InstallationDate: Installed on 2011-10-19 (3240 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to focal on 2019-04-27 (493 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1893838/+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 1884101] Re: jackdbus produces high cpu load
Did that already, got rid of the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in jackd2 package in Ubuntu: Incomplete Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1884101/+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 1884101] [NEW] jackdbus produces high cpu load
Public bug reported: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1884101 Title: jackdbus produces high cpu load Status in pulseaudio package in Ubuntu: New Bug description: if jackd and jackdbus run, jackd and/or jackdbus produce high cpu load. jackd tends to take all availabl CPU power bringing the system to slow down remarkably. Killing jackd and jackdbus frees cpu and system load drops from 100%/per CPU down to ~4% overall. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio-module-jack 1:13.99.1-1ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sct-muc1800 F pulseaudio /dev/snd/pcmC0D0c: sct-muc1800 F...m pulseaudio /dev/snd/pcmC0D0p: sct-muc1800 F...m pulseaudio /dev/snd/timer: sct-muc1800 f pulseaudio CasperMD5CheckResult: skip Date: Thu Jun 18 18:08:25 2020 InstallationDate: Installed on 2019-09-09 (282 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2020 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd02/27/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1884101/+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 1862157] [NEW] dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles
asume following: / /data /data/tftp /data/tftp/grub /data/tftp/pxe tftp on some client: tftp-root unset: tftp grub/grub.0 -> file not found tftp /grub/grub.0 -> file not found tftp data/tftp/grub/grub.0 -> loads grub. tftp /data/tftp/grub/grub.0 -> loads grub. tftp-root=/data/tftp -- this prepends tftp-root to all paths given: tftp grub/grub.0 -> /data/tftp/grub/grub.0 -> loads grub. tftp /grub/grub.0 -> /data/tftp/grub/grub.0 -> loads grub tftp data/tftp/grub/grub.0 -> /data/tftp/data/tftp/grub/grub.0 -> file not found tftp /data/tftp/grub/grub.0 -> /data/tftp/data/tftp/grub/grub.0 -> file not found This way tftp in dnsmasq exposes what directory tftp-files reside. I'd awaited it to act if tftp-root is set as: tftp grub/grub.0 -> grub/grub.0 -> loads grub. tftp /grub/grub.0 -> grub/grub.0 -> loads grub tftp data/tftp/grub/grub.0 -> data/tftp/grub/grub.0 -> file not found tftp /data/tftp/grub/grub.0 -> /data/tftp/grub/grub.0 -> file not found Thus meaning tftp-root acts like chroot making tftp-clients see set tftp-root as root of the filesystem, not as forced path into a filesystem how dnsmasq handles tftp-root makes it difficult to have further software have correct paths to boot operating systems, because dnsmasq tftp handles back full paths which may be never available to nfs or smb based remote boots. On Fri, Feb 7, 2020 at 10:25 PM Simon Kelley wrote: > tftp-root is a security feature. The tftp protocol is entirely > unauthenticated, and if a request was allowed to go outside the > specified root directory, than that effectively makes all readable files > on the host available for internet-wide access, which is not generally > desirable. If you want TFTP to be able to access any file on the > machine, don't set a tftp-root. > > > Simon. > > > On 06/02/2020 11:02, Thomas Schweikle wrote: > > Public bug reported: > > > > dnsmasq does in all cases prepend "tftp_root" to tftp-files. > > > > tftp-root=/data/tftp > > dhcp-boot=grub/i386-pc/core.0 > > > > now have some config files for different subnets: > > dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1 > > dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1 > > dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de > > > > Now booting clients within subnet 172.18.1.0/24 will boot grub with: > > /data/tftp/grub/i386-pc/core.0 > > > > Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with: > > /data/tftp/pxelinux.0 > > > > And in subnet 172.18.7.0/24 clients will boot with: > > /data/tftp/var/lib/tftpboot/pxelinux.0 > > > > and return a "File not found" error. > > > > I'd expected: > > 172.18.1: grub/i386-pc/core.0 (file found within /data/tftp -- > without exposing path) > > 172.18.2: pxelinux.0(file found within /data/tftp -- > without exposing path) > > 172.18.3: /pxelinux.0 (file found within /) > > 172.18.7: /var/lib/tftpboot/pxelinux.0 (file found within > /var/lib/tftpboot/pxelinux.0) > > > > or even better: some way to set tftp-root for every subnet-config and > > having only relative paths to access files regardless of giving absolute > > or relative paths. > > > > ProblemType: Bug > > DistroRelease: Ubuntu 18.04 > > Package: dnsmasq 2.79-1 > > ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 > > Uname: Linux 4.15.0-87-generic x86_64 > > ApportVersion: 2.20.9-0ubuntu7.10 > > Architecture: amd64 > > Date: Thu Feb 6 11:43:07 2020 > > InstallationDate: Installed on 2014-01-31 (2197 days ago) > > InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release > amd64 (20131016) > > PackageArchitecture: all > > ProcEnviron: > > TERM=xterm > > PATH=(custom, no user) > > XDG_RUNTIME_DIR= > > LANG=de_DE.UTF-8 > > SHELL=/bin/bash > > SourcePackage: dnsmasq > > UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago) > > mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 > > mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353 > > > > ** Affects: dnsmasq (Ubuntu) > > Importance: Undecided > > Status: New > > > > > > ** Tags: amd64 apport-bug bionic > > > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1862157 > > Title: > dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/dnsmasq
[Touch-packages] [Bug 1862157] Re: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles
Simplest thing would be: tftp-root sets the tftp-root directory: /data/tftp -> / or: /var/lib/tftpboot -> / Whatever is done is relative to this. tftp-root is then NEVER prepended to any file given for tftp retrival. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1862157 Title: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles Status in dnsmasq package in Ubuntu: New Bug description: dnsmasq does in all cases prepend "tftp_root" to tftp-files. tftp-root=/data/tftp dhcp-boot=grub/i386-pc/core.0 now have some config files for different subnets: dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1 dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1 dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de Now booting clients within subnet 172.18.1.0/24 will boot grub with: /data/tftp/grub/i386-pc/core.0 Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with: /data/tftp/pxelinux.0 And in subnet 172.18.7.0/24 clients will boot with: /data/tftp/var/lib/tftpboot/pxelinux.0 and return a "File not found" error. I'd expected: 172.18.1: grub/i386-pc/core.0 (file found within /data/tftp -- without exposing path) 172.18.2: pxelinux.0(file found within /data/tftp -- without exposing path) 172.18.3: /pxelinux.0 (file found within /) 172.18.7: /var/lib/tftpboot/pxelinux.0 (file found within /var/lib/tftpboot/pxelinux.0) or even better: some way to set tftp-root for every subnet-config and having only relative paths to access files regardless of giving absolute or relative paths. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Thu Feb 6 11:43:07 2020 InstallationDate: Installed on 2014-01-31 (2197 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago) mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1862157/+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 1862157] [NEW] dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles
Public bug reported: dnsmasq does in all cases prepend "tftp_root" to tftp-files. tftp-root=/data/tftp dhcp-boot=grub/i386-pc/core.0 now have some config files for different subnets: dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1 dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1 dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de Now booting clients within subnet 172.18.1.0/24 will boot grub with: /data/tftp/grub/i386-pc/core.0 Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with: /data/tftp/pxelinux.0 And in subnet 172.18.7.0/24 clients will boot with: /data/tftp/var/lib/tftpboot/pxelinux.0 and return a "File not found" error. I'd expected: 172.18.1: grub/i386-pc/core.0 (file found within /data/tftp -- without exposing path) 172.18.2: pxelinux.0(file found within /data/tftp -- without exposing path) 172.18.3: /pxelinux.0 (file found within /) 172.18.7: /var/lib/tftpboot/pxelinux.0 (file found within /var/lib/tftpboot/pxelinux.0) or even better: some way to set tftp-root for every subnet-config and having only relative paths to access files regardless of giving absolute or relative paths. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Thu Feb 6 11:43:07 2020 InstallationDate: Installed on 2014-01-31 (2197 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago) mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353 ** Affects: dnsmasq (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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1862157 Title: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles Status in dnsmasq package in Ubuntu: New Bug description: dnsmasq does in all cases prepend "tftp_root" to tftp-files. tftp-root=/data/tftp dhcp-boot=grub/i386-pc/core.0 now have some config files for different subnets: dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1 dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1 dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de Now booting clients within subnet 172.18.1.0/24 will boot grub with: /data/tftp/grub/i386-pc/core.0 Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with: /data/tftp/pxelinux.0 And in subnet 172.18.7.0/24 clients will boot with: /data/tftp/var/lib/tftpboot/pxelinux.0 and return a "File not found" error. I'd expected: 172.18.1: grub/i386-pc/core.0 (file found within /data/tftp -- without exposing path) 172.18.2: pxelinux.0(file found within /data/tftp -- without exposing path) 172.18.3: /pxelinux.0 (file found within /) 172.18.7: /var/lib/tftpboot/pxelinux.0 (file found within /var/lib/tftpboot/pxelinux.0) or even better: some way to set tftp-root for every subnet-config and having only relative paths to access files regardless of giving absolute or relative paths. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dnsmasq 2.79-1 ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18 Uname: Linux 4.15.0-87-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Thu Feb 6 11:43:07 2020 InstallationDate: Installed on 2014-01-31 (2197 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: dnsmasq UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago) mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595 mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1862157/+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 1856204] [NEW] If a printer is set to "AuthInfoRequested negotiate" cups asks password for user negotiate
Public bug reported: If a printer is set to "AuthInfoRequested negotiate" cups will ask for password for user "negotiate" instead to exaust an error because "negotiate" isn't a keyword. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:45:11 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856204 Title: If a printer is set to "AuthInfoRequested negotiate" cups asks password for user negotiate Status in cups package in Ubuntu: New Bug description: If a printer is set to "AuthInfoRequested negotiate" cups will ask for password for user "negotiate" instead to exaust an error because "negotiate" isn't a keyword. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:45:11 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None
[Touch-packages] [Bug 1856201] [NEW] AuthInfoRequired set for one Printer will set it for all printers
Public bug reported: If at least one printer is set to "AuthInfoRequested negotiate" this will be taken for all printers, even if these have set "AuthInfoRequested none". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:39:56 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856201 Title: AuthInfoRequired set for one Printer will set it for all printers Status in cups package in Ubuntu: New Bug description: If at least one printer is set to "AuthInfoRequested negotiate" this will be taken for all printers, even if these have set "AuthInfoRequested none". ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 16:39:56 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C554e: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
The loop isn't within cups, but within js running within the browser. Noting this I tried to switch to an other browser to get rid of this loop. But without success: any of the tested ones leads to this loop: - Firefox (stable, esr, nightly) - Chrome (stable, beta, unstable, waterfall) - Chromium (stable, waterfall) - Vivaldi (stable, snapshot) - Opera (stable, beta, snapshot) - otter-browser - lynx -> pages unusable -- did not test further. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: Incomplete Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Same for any page with any printer. CUPS seems to run an endless loop exausting it has done ok. But nothing done at all. Just looping. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: New Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd',
[Touch-packages] [Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages
Same for adding a new printer. -- 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/1856189 Title: Trying to delete a printer will fill up the filesystem with logmessages Status in cups package in Ubuntu: New Bug description: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep:
[Touch-packages] [Bug 1856189] [NEW] Trying to delete a printer will fill up the filesystem with logmessages
Public bug reported: Trying to delete a printer will fill up the filesystem with log messages ala localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok localhost - - [12/Dec/2019:14:30:09 +0100] "POST /admin/ HTTP/1.1" 401 156 CUPS-Delete-Printer successful-ok 150GiByte lines except of data and time the same as given above after trying to delete one printer. Found the same on two ubuntu installations. Both 19.10 eoan ermine. NB: the printer was not deleted at all! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CupsErrorLog: E [12/Dec/2019:14:25:02 +0100] [Job 2] Files have gone away. E [12/Dec/2019:14:26:12 +0100] [Client 188] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:26:45 +0100] [Client 83826] Unable to encrypt connection: A TLS fatal alert has been received. E [12/Dec/2019:14:27:26 +0100] [Client 351687] Unable to encrypt connection: A TLS fatal alert has been received. Date: Thu Dec 12 14:29:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor:
[Touch-packages] [Bug 1856187] [NEW] Cups wont print to smb-shared printer requiring user authentication via kerberos
Public bug reported: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary. That's not true: the printer requires authentication. Maybe a bug. This print server requires any user to be authenticated and have a kerberos ticket. This is true. The user has a kerberos ticket and this user is allowed to print. The users kerberos ticket cache is available in memory and in /tmp/krb5_.keytab. CUPS does not seem to take it into account. May be a bug too. Changing "AuthInfoRequired" from "none" to "username,password" allows cups to print. But this has to be done editing /etc/cups/printers.conf. The web printer configuration just does not allow to set anything else than "none". This is a bug. Documentation misses what "AuthInfoRequired" has to be set for if kerberos authentication will be used. This is a bug too! ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Thu Dec 12 13:54:01 2019 InstallationDate: Installed on 2019-09-09 (93 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for PDF: cups-pdf:/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/PDF.ppd', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: Permission denied grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-24-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1856187 Title: Cups wont print to smb-shared printer requiring user authentication via kerberos Status in cups package in Ubuntu: New Bug description: Setup: - Print server part of an AD domain. Print server requires authentication. - Ubuntu client with cups-server. The client is part of the AD domain. The client does not share printers (and never will). - User authenticated by AD within the AD domain. - Now user wants to print. Printer is set up: UUID urn:uuid:85b0f3b3-67a2-3385-7fd2-57ac93c0f837 AuthInfoRequired none Info KONICA MINOLTA C364e Location E017 MakeModel KONICA MINOLTA C364SeriesPS(P) DeviceURI smb:///drucker-muc PortMonitor tbcp State Idle StateTime 1576145797 ConfigTime 1576146371 Type 8401100 Accepting Yes Shared No JobSheets none none QuotaPeriod 0 PageLimit 0 KLimit 0 OpPolicy default ErrorPolicy retry-job Option print-quality 3 Since AuthInfoRequired is set to "none" cups thinks everyone can print and no authentication would be necessary.
[Touch-packages] [Bug 1854772] Re: /var/lib/dpkg/status has faulty entries
** Attachment added: "faulty /var/lib/dpkg/status"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+attachment/5309330/+files/status
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1854772
Title:
/var/lib/dpkg/status has faulty entries
Status in apt package in Ubuntu:
New
Bug description:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
field, value = line.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in
main(config)
File "/usr/bin/apt-listchanges", line 83, in main
status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
{'what': file, 'errmsg': str(ex)}) from ex
RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough
values to unpack (expected 2, got 1)
(Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit
installiert.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apt 1.9.4
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 2 16:00:56 2019
InstallationDate: Installed on 2019-09-09 (83 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+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 1854772] [NEW] /var/lib/dpkg/status has faulty entries
Public bug reported:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
field, value = line.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in
main(config)
File "/usr/bin/apt-listchanges", line 83, in main
status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
{'what': file, 'errmsg': str(ex)}) from ex
RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough
values to unpack (expected 2, got 1)
(Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit installiert.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apt 1.9.4
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 2 16:00:56 2019
InstallationDate: Installed on 2019-09-09 (83 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
--
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/1854772
Title:
/var/lib/dpkg/status has faulty entries
Status in apt package in Ubuntu:
New
Bug description:
Es wurden 1.109 kB in 0 s geholt (3.865 kB/s).
Traceback (most recent call last):
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in readfile
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 117, in
self.stanzas += [ControlStanza(x) for x in f.read().split('\n\n') if x]
File "/usr/share/apt-listchanges/DebianFiles.py", line 70, in __init__
field, value = line.split(':', 1)
ValueError: not enough values to unpack (expected 2, got 1)
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/usr/bin/apt-listchanges", line 280, in
main(config)
File "/usr/bin/apt-listchanges", line 83, in main
status.readfile('/var/lib/dpkg/status')
File "/usr/share/apt-listchanges/DebianFiles.py", line 120, in readfile
{'what': file, 'errmsg': str(ex)}) from ex
RuntimeError: Fehler beim Verarbeiten von »/var/lib/dpkg/status«: not enough
values to unpack (expected 2, got 1)
(Lese Datenbank ... 376829 Dateien und Verzeichnisse sind derzeit
installiert.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apt 1.9.4
ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
Uname: Linux 5.3.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Dec 2 16:00:56 2019
InstallationDate: Installed on 2019-09-09 (83 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1854772/+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 1854195] [NEW] pc wont resolve any names until /etc/resolv.conf is edited by hand
Public bug reported: In /etc/systemd/resolved.conf I've entered the nameserver to use: [Resolve] DNS=172.18.8.1 #FallbackDNS= Domains=fritz.box #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes In /etc/resolv.conf after rebooting: nameserver 127.0.0.53 options edns0 search fritz.box No names from anywhere are solved. This systemd-resolver just does nothing. It does not even forward any request to 172.18.8.1! As soon as I edit /etc/resolv.conf, replacing 127.0.0.53 with 172.18.8.1 it starts to work as it is expected to. Looks like systemd-resolved is broken by design. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 27 19:16:22 2019 InstallationDate: Installed on 2019-09-09 (79 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-23-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1854195 Title: pc wont resolve any names until /etc/resolv.conf is edited by hand Status in systemd package in Ubuntu: New Bug description: In /etc/systemd/resolved.conf I've entered the nameserver to use: [Resolve] DNS=172.18.8.1 #FallbackDNS= Domains=fritz.box #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes In /etc/resolv.conf after rebooting: nameserver 127.0.0.53 options edns0 search fritz.box No names from anywhere are solved. This systemd-resolver just does nothing. It does not even forward any request to 172.18.8.1! As soon as I edit /etc/resolv.conf, replacing 127.0.0.53 with 172.18.8.1 it starts to work as it is expected to. Looks like systemd- resolved is broken by design. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3.2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 27 19:16:22 2019 InstallationDate: Installed on 2019-09-09 (79 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-23-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc.
[Touch-packages] [Bug 788167] Re: CUPS cannot print to Kerberos-authenticated SMB print queue
Same for Ubuntu 19.10 with cups 2.2.12 -- 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/788167 Title: CUPS cannot print to Kerberos-authenticated SMB print queue Status in cups package in Ubuntu: Confirmed Status in Debian: Fix Released Bug description: Binary package hint: cups That was investigated on maverick (cups 1.4.4) and natty (cups 1.4.6). CUPS in Ubuntu cannot authenticate using Kerberos to an SMB print queue, such as one in an Active Directory. This is because the smb backend is being invoked as user lp, and this user cannot access the Kerberos credential cache of the user who submitted the job. When trying to print, the job is held for authentication, and a dialog prompting for username/password is being shown. On Windows (and possibly other OS), the user would not be prompted if he has a ticket in the Kerberos realm (ie, "logged on to the domain") he is trying to print to. The CUPS smb backend on Ubuntu is the smbspool binary provided by Samba. When run as a user, it will pick the Kerberos credential cache by itself and authenticate seamlessly. Otherwise, it will read the KRB5CCNAME environment variable and try to use that when possible. There is two possible solutions to that: - Invoke the smb backend as root and pass it the KRB5CCNAME environment variable pointing to the user's Kerberos credential cache. CUPS execute the backend as user lp if it is world-executable, which is currently the case on Ubuntu. User lp do not have the permission to read the user's credential cache, hence why the smb backend would need to be executed as root (by removing the world-executable bit). Also, CUPS does not currently set KRB5CCNAME before invoking the smb backend (see http://www.cups.org/str.php?L3847). - Execute smbspool as the user submitting the job. I presume we would have the same problem with other backend that would do Kerberos authentication, although I do not know of a specific one. I have only tested and investigated with the smb backend. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/788167/+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 1852474] [NEW] cups not printing if authentication required by server
Public bug reported: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1852474 Title: cups not printing if authentication required by server Status in cups package in Ubuntu: New Bug description: cups does not print if servers require authenticated users to print. No login-dialog is shown. Print jobs are on hold, waiting for legitimization. But no legitimization dialog will be shown. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Nov 13 19:23:18 2019 InstallationDate: Installed on 2019-09-09 (65 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for KONICA-MINOLTA-C364Series-OpenOffice-PPD: smb://srvmfg02-muc.bfs.de/drucker-muc device for Lexmark_MX310dn: implicitclass://Lexmark_MX310dn/ Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd', '/etc/cups/ppd/Lexmark_MX310dn.ppd'] failed with exit code 2: grep: /etc/cups/ppd/KONICA-MINOLTA-C364Series-OpenOffice-PPD.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_MX310dn.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-22-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None
[Touch-packages] [Bug 1852411] [NEW] systemd resolver not working
Public bug reported: resolv.conf holds after boot: nameserver 127.0.0.53 options edns0 [...] Trying to resolve google.com just leads to nothing. Same for any address you try to resolve. Systemd just does not forward to the given resolver address in /etc/systemd/resolved.conf: [Resolve] DNS=172.18.8.1 #FallbackDNS= Domains=bfs.de bfs.intern lab.bfs.de rodos.bfs.de #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes Copying the address given vor variable DNS in /etc/systemd/resolved.conf to nameserver in /etc/resolve.conf makes everything working immediately. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Nov 13 10:23:18 2019 InstallationDate: Installed on 2019-09-09 (64 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-19-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. mtime.conffile..etc.systemd.resolved.conf: 2019-09-24T10:52:27.095603 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1852411 Title: systemd resolver not working Status in systemd package in Ubuntu: New Bug description: resolv.conf holds after boot: nameserver 127.0.0.53 options edns0 [...] Trying to resolve google.com just leads to nothing. Same for any address you try to resolve. Systemd just does not forward to the given resolver address in /etc/systemd/resolved.conf: [Resolve] DNS=172.18.8.1 #FallbackDNS= Domains=bfs.de bfs.intern lab.bfs.de rodos.bfs.de #LLMNR=no #MulticastDNS=no #DNSSEC=no #DNSOverTLS=no #Cache=yes #DNSStubListener=yes #ReadEtcHosts=yes Copying the address given vor variable DNS in /etc/systemd/resolved.conf to nameserver in /etc/resolve.conf makes everything working immediately. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 242-7ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Wed Nov 13 10:23:18 2019 InstallationDate: Installed on 2019-09-09 (64 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: LANGUAGE=de_DE TERM=screen PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-19-generic root=UUID=f99c1b40-4de7-4f4c-9d3f-c32918aa952c ro rootflags=subvol=@ quiet splash SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2019 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/29/2019:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware
[Touch-packages] [Bug 1843886] [NEW] pam_env.so does not recursively read /etc/environment.d
Public bug reported: Ubuntu creates /etc/environment and directory /etc/environment.d. pam_env.so only reads /etc/environment, but not recursively /etc/environment.d/ You'll have to add any files created within /etc/environment.d/ as an additional line to your pam_env.so pam configuration. This is not stated anywhere and not documented accordingly. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 13 12:55:41 2019 InstallationDate: Installed on 2019-09-09 (3 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1843886 Title: pam_env.so does not recursively read /etc/environment.d Status in pam package in Ubuntu: New Bug description: Ubuntu creates /etc/environment and directory /etc/environment.d. pam_env.so only reads /etc/environment, but not recursively /etc/environment.d/ You'll have to add any files created within /etc/environment.d/ as an additional line to your pam_env.so pam configuration. This is not stated anywhere and not documented accordingly. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 13 12:55:41 2019 InstallationDate: Installed on 2019-09-09 (3 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: pam UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1843886/+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 1816361] Re: remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7
Older kernels do not matter. Same effect. Cant login remote. If I use an older sshd it works. If I use a self compiled sshd (same version) it works. On Mon, Feb 18, 2019 at 9:00 AM Thomas Schweikle <1816...@bugs.launchpad.net> wrote: > > This might be related to dhcp configuration not korrektly interpreted: > the dhcp-servers address is taken for the client address, which leads to > duplicate addresses: > > dhcp-server: 172.18.8.186 > dhcp-response: 172.18.8.111 > > clients takes 172.18.8.186 for his address instead of 172.18.8.111 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1816361 > > Title: > remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1816361/+subscriptions -- Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1816361 Title: remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7 Status in openssh package in Ubuntu: New Bug description: Since upgrading to openssh 7.2p2-4ubuntu2.7 it is impossible to login remote. It does not matter what password is set, if you are root or not. Login fails in all cases. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Feb 18 08:23:20 2019 InstallationDate: Installed on 2012-12-12 (2258 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2013-02-11 (2197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1816361/+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 1816361] Re: remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7
This might be related to dhcp configuration not korrektly interpreted: the dhcp-servers address is taken for the client address, which leads to duplicate addresses: dhcp-server: 172.18.8.186 dhcp-response: 172.18.8.111 clients takes 172.18.8.186 for his address instead of 172.18.8.111 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1816361 Title: remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7 Status in openssh package in Ubuntu: New Bug description: Since upgrading to openssh 7.2p2-4ubuntu2.7 it is impossible to login remote. It does not matter what password is set, if you are root or not. Login fails in all cases. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Feb 18 08:23:20 2019 InstallationDate: Installed on 2012-12-12 (2258 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2013-02-11 (2197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1816361/+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 1816361] [NEW] remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7
Public bug reported: Since upgrading to openssh 7.2p2-4ubuntu2.7 it is impossible to login remote. It does not matter what password is set, if you are root or not. Login fails in all cases. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Feb 18 08:23:20 2019 InstallationDate: Installed on 2012-12-12 (2258 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2013-02-11 (2197 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1816361 Title: remote ssh-login impossible with openssh 7.2p2-4ubuntu2.7 Status in openssh package in Ubuntu: New Bug description: Since upgrading to openssh 7.2p2-4ubuntu2.7 it is impossible to login remote. It does not matter what password is set, if you are root or not. Login fails in all cases. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Mon Feb 18 08:23:20 2019 InstallationDate: Installed on 2012-12-12 (2258 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to xenial on 2013-02-11 (2197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1816361/+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 1814473] [NEW] latest systemd, network-manager, kernel updates killed networking
Public bug reported: Latest network-manager, systemd, kernel-updates killed ethernet networking. It is impossible to have an address assigned. I can make sure hardware is ok, by booting into SystemRescueCD. Ethernet immediately is up and working. As soon as I boot into Ubuntu 18.10 networking with ethernet stops working at all. Even trying to set it up manually using "ip" or "ifconfig" does not help. Modules seem loaded, but not functional. Unsure if it is kernel, systemd, or network-manager related. >From network-manager I can activate WLAN. Thus in my humble opinion the driver or firmware was killed by installing the latest updates. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 3 21:52:57 2019 IfupdownConfig: # Local loopback auto lo iface lo inet loopback InstallationDate: Installed on 2011-10-19 (2664 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to cosmic on 2018-11-03 (92 days ago) mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1814473 Title: latest systemd, network-manager, kernel updates killed networking Status in network-manager package in Ubuntu: New Bug description: Latest network-manager, systemd, kernel-updates killed ethernet networking. It is impossible to have an address assigned. I can make sure hardware is ok, by booting into SystemRescueCD. Ethernet immediately is up and working. As soon as I boot into Ubuntu 18.10 networking with ethernet stops working at all. Even trying to set it up manually using "ip" or "ifconfig" does not help. Modules seem loaded, but not functional. Unsure if it is kernel, systemd, or network-manager related. From network-manager I can activate WLAN. Thus in my humble opinion the driver or firmware was killed by installing the latest updates. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.4-1ubuntu1.2 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Feb 3 21:52:57 2019 IfupdownConfig: # Local loopback auto lo iface lo inet loopback InstallationDate: Installed on 2011-10-19 (2664 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to cosmic on 2018-11-03 (92 days ago) mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1814473/+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 1812095] Re: console login loop after entering username followed by RETURN
Setting the password again you'll have a login, but you cant type in your password. After typing your login name followed by RETURN password is immediately left. Looks like the entered RETURN is kept and all subsequent calls see RETURN and just quit. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: New Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1812095] [NEW] console login loop after entering username followed by RETURN
Public bug reported: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: New Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1801538] Re: no sound after upgrading to ubuntu 18.10 from 18.04
*** This bug is a duplicate of bug 210472 *** https://bugs.launchpad.net/bugs/210472 Yes, that is it! systemctl stop timidity.service systemctl disable timidity.service solves the problem. On Sat, Nov 3, 2018 at 9:30 PM Cristian Aravena Romero wrote: > > *** This bug is a duplicate of bug 210472 *** > https://bugs.launchpad.net/bugs/210472 > > ** This bug has been marked a duplicate of bug 210472 >Timidity daemon doesn't play nice with pulse audio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1801538 > > Title: > no sound after upgrading to ubuntu 18.10 from 18.04 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+subscriptions -- Thomas -- 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/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) 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 cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801538] [NEW] no sound after upgrading to ubuntu 18.10 from 18.04
Public bug reported: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) 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 cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1801538 Title: no sound after upgrading to ubuntu 18.10 from 18.04 Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu 18.10 does not recognize sound devices. After upgrading there is only a dummy device known. All others are gone. In tune there is no sound output to nowhere. It does not mater it headphones are plugged or not while booting. It does not matter if any usb-sound device is plugged or not. The only device show for output in mixer is "Dummy device". ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 8931 F timidity /dev/snd/pcmC0D0p: timidity 8931 F...m timidity /dev/snd/seq:timidity 8931 F timidity /dev/snd/timer: timidity 8931 f timidity Date: Sat Nov 3 17:25:55 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) 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 cosmic on 2018-11-03 (0 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.sku: TravelMate P643-M_0681_2.15 dmi.product.version: V2.15 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1801538/+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 1801533] Re: lightdm does not start
This schouldn't happen. lightdm should only be started about 10 times, then disabled. BTW: no errors are readable on screen. Logs only show lightdm restarted by systemd after terminatating. Errors can be seen by disabling lightdm, then starting it from commandline. But this isn't helpful either: "Could not initialize screen. Terminating." -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] Re: lightdm does not start
This bug exists since 16.10 – we are at 18.10 now it is now two years with this monitor killing bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] Re: lightdm does not start
Same problem: it does not matter if upgraded from 18.04 or installed new with 18.10. lightdm might not allways be capable initializing graphics leeding to some loop together with systemd turning on backlight, turning it off again, then restarting. Backlight is turned on, then off about twice a second. After some time backlight electronics break down, killing the monitor. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1801533] [NEW] lightdm does not start
Public bug reported: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1801533 Title: lightdm does not start Status in lightdm package in Ubuntu: New Bug description: lightdm tries to initialize screen output, fails, tries again, fails until the backlight electronics break, killing the monitor. lightdm fails initializing screen. This turns on backlight, initializes graphics, then lightdm stops with an error message. systemd starts lightdm again. Lightdm tries to initialize graphics. This turns on backlight. Lightdm fails, exausts an error message, backlight turns off again. systemd starts lightdm, lightdm tries to initialize graphics. Turns on backlight. Exausts an error message. Backlight is turned off again. ... After doing so more than twice a second backlight breaks. Electronics broke down. Conclusion: at the moment Ubuntu 18.10 is capable of killing monitors by lightdm not able to initialize screens and breaking, then beeing restarted by systemd. Since this can kill hardware it is a no go! It is a bad bad bad bad bad bad bad bad bad bad bad bad bad bad bug! ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: lightdm 1.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Sat Nov 3 17:03:19 2018 InstallationDate: Installed on 2011-10-19 (2571 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1801533/+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 1796948] [NEW] cups gives back "filter failed" for all trials to print to any printer
Public bug reported: Any printing attempt to any printer is quitted with "filter failed" by cups. Even for test pages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18 Uname: Linux 4.15.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 9 20:21:26 2018 InstallationDate: Installed on 2011-10-19 (2546 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100 device for PDF: cups-pdf:/ device for Roger-Router-Fax: roger-cups:/ MachineType: Acer TravelMate P643-M Papersize: a4 PpdFiles: Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1 Roger-Router-Fax: roger fax printer, 1.0 PDF: Generic CUPS-PDF Printer Kyocera_FS-1300D: Kyocera FS-1300D (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic third-party-packages -- 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/1796948 Title: cups gives back "filter failed" for all trials to print to any printer Status in cups package in Ubuntu: New Bug description: Any printing attempt to any printer is quitted with "filter failed" by cups. Even for test pages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18 Uname: Linux 4.15.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 9 20:21:26 2018 InstallationDate: Installed on 2011-10-19 (2546 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100 device for PDF: cups-pdf:/ device for Roger-Router-Fax: roger-cups:/ MachineType: Acer TravelMate P643-M Papersize: a4 PpdFiles: Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1 Roger-Router-Fax: roger fax printer, 1.0 PDF: Generic CUPS-PDF Printer Kyocera_FS-1300D: Kyocera FS-1300D (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1796948/+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 1796946] [NEW] cups does not allow adding, deleting or changing printers
Public bug reported: Cups tells changing a printer the user would have to authenticate with username and password, but never asks for username and password in tune cups denys access to printer configurations and no changes are possible using the web interface. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18 Uname: Linux 4.15.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 9 20:12:12 2018 InstallationDate: Installed on 2011-10-19 (2546 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100 device for PDF: cups-pdf:/ device for Roger-Router-Fax: roger-cups:/ MachineType: Acer TravelMate P643-M Papersize: a4 PpdFiles: Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1 Roger-Router-Fax: roger fax printer, 1.0 PDF: Generic CUPS-PDF Printer Kyocera_FS-1300D: Kyocera FS-1300D (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic third-party-packages -- 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/1796946 Title: cups does not allow adding, deleting or changing printers Status in cups package in Ubuntu: New Bug description: Cups tells changing a printer the user would have to authenticate with username and password, but never asks for username and password in tune cups denys access to printer configurations and no changes are possible using the web interface. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-37.40-generic 4.15.18 Uname: Linux 4.15.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 9 20:12:12 2018 InstallationDate: Installed on 2011-10-19 (2546 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for Kyocera_FS-1300D: socket://kymi.fritz.box:9100 device for PDF: cups-pdf:/ device for Roger-Router-Fax: roger-cups:/ MachineType: Acer TravelMate P643-M Papersize: a4 PpdFiles: Kyocera_FS-1128MFP: Kyocera FS-1118MFP - CUPS+Gutenprint v5.2.8-pre1 Roger-Router-Fax: roger fax printer, 1.0 PDF: Generic CUPS-PDF Printer Kyocera_FS-1300D: Kyocera FS-1300D (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-37-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-10-02 (7 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.family: TravelMate P643-M dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer mtime.conffile..etc.cups.cupsd.conf: 2018-10-09T20:06:41.547549 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1796946/+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 1795856] [NEW] after upgrading lightdm configuration is missing
Public bug reported: After upgrading lightdm does not have a config any more: cat: /etc/lightdm/lightdm.conf: Datei oder Verzeichnis nicht gefunden In tune it does not start ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 3 12:42:36 2018 InstallationDate: Installed on 2011-10-19 (2540 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2018-10-02 (1 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1795856 Title: after upgrading lightdm configuration is missing Status in lightdm package in Ubuntu: New Bug description: After upgrading lightdm does not have a config any more: cat: /etc/lightdm/lightdm.conf: Datei oder Verzeichnis nicht gefunden In tune it does not start ... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 3 12:42:36 2018 InstallationDate: Installed on 2011-10-19 (2540 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: lightdm UpgradeStatus: Upgraded to bionic on 2018-10-02 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1795856/+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 1795852] [NEW] "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found."
Public bug reported: "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found." -> resolv.conf only holds two lines: --- snip nameserver 127.0.0.1 --- snap and "host google.com" leads to Host google.com not found: 5(REFUSED) dnsmasq is running, but does not know whom to query upstream, because "/etc/resolv.conf" only holds the local address. "/etc/resolv.conf" is created by "resolvconf". Systems address is assigned by dhclient. "/etc/dhcp/dhclient.conf" holds: --- snip option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; send host-name = gethostname(); request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers; timeout 300; --- snap There are three instances of dnsmasq started: --- snip 7272 ?S 0:00 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service --trust-anchor=.,19036,8,2,49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5 --trust-anchor=.,20326,8,2,e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d 7838 ?S 0:00 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper 7839 ?S 0:00 \_ /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper --- snap "/etc/network/interaces" holds: --- snip # Local loopback auto lo iface lo inet loopback --- snap What I'd expected after upgrading: working network config with a working "/etc/resolv.conf"! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 3 11:57:42 2018 InstallationDate: Installed on 2011-10-19 (2540 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) MachineType: Acer TravelMate P643-M ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic root=/dev/mapper/vg-root ro elevator=deadline splash acpi=force reboot=bios ipv6.disable=1 vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-10-02 (1 days ago) dmi.bios.date: 10/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.15 dmi.board.asset.tag: No Asset Tag dmi.board.name: TravelMate P643-M dmi.board.vendor: Acer dmi.board.version: V2.15 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.15 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.15:bd10/21/2013:svnAcer:pnTravelMateP643-M:pvrV2.15:rvnAcer:rnTravelMateP643-M:rvrV2.15:cvnAcer:ct9:cvrV2.15: dmi.product.name: TravelMate P643-M dmi.product.version: V2.15 dmi.sys.vendor: Acer ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1795852 Title: "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found." Status in systemd package in Ubuntu: New Bug description: "systemd-resolve --status" reports "Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found." -> resolv.conf only holds two lines: --- snip nameserver 127.0.0.1 --- snap and "host google.com" leads to Host google.com not found: 5(REFUSED) dnsmasq is running, but does not know whom to query upstream, because "/etc/resolv.conf" only holds the local address. "/etc/resolv.conf" is created by "resolvconf". Systems address is assigned by dhclient. "/etc/dhcp/dhclient.conf" holds: --- snip option rfc3442-classless-static-routes code 121 = array of unsigned integer 8; send host-name = gethostname(); request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search, host-name, dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers, netbios-name-servers, netbios-scope, interface-mtu, rfc3442-classless-static-routes, ntp-servers; timeout 300; --- snap There are three instances of dnsmasq started: --- snip 7272 ?S 0:00 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -r /run/dnsmasq/resolv.conf -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
The boot space problem is not resolved by purge-old-kernels, since this command does not remove old initrd from kernels not installed any more. purge-old-kernels shall remove any initrd from kernels it removes! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space Status in initramfs-tools: Confirmed Status in Ubuntu Software Center: Invalid Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1739478] [NEW] lightdm does not start any desktop environment
Public bug reported: Since latest updates lightdm does not start any desktop environment. After loging in a blank screen (if you had set a desktop background the desktop background) is shown. No window manager, no session manager gets started. To start a desktop environment you'll have to switch to a console (CTRL-ALT-F1). Login with your username and password. Give "sudo service lightdm stop". After lightdm is stopped you can start your desktop environment with "startx". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 Uname: Linux 4.13.16+ x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 20 21:29:50 2017 InstallationDate: Installed on 2011-10-19 (2254 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2017-08-03 (139 days ago) ** Affects: lightdm (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 lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1739478 Title: lightdm does not start any desktop environment Status in lightdm package in Ubuntu: New Bug description: Since latest updates lightdm does not start any desktop environment. After loging in a blank screen (if you had set a desktop background the desktop background) is shown. No window manager, no session manager gets started. To start a desktop environment you'll have to switch to a console (CTRL-ALT-F1). Login with your username and password. Give "sudo service lightdm stop". After lightdm is stopped you can start your desktop environment with "startx". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 Uname: Linux 4.13.16+ x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Dec 20 21:29:50 2017 InstallationDate: Installed on 2011-10-19 (2254 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) LightdmConfig: [SeatDefaults] greeter-session=lightdm-gtk-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2017-08-03 (139 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1739478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space
Ubuntu keeps to many old kernel-images and initrd within /boot. Space is exausted and it fails to delete old unused kernels before creating a new initrd failing building an initrd for the newly installed kernel. A workaround is to delete all old unused kernels and then try it again. It will succeed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/798414 Title: update-initramfs should produce a more helpful error message when there isn't enough free space Status in initramfs-tools: Confirmed Status in Ubuntu Software Center: Invalid Status in dpkg package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Binary package hint: initramfs-tools When installing a kernel, /boot may become full during execution of post-installation script typically when update-initramfs is creating or updating an initrd.img file. This is resulting in kernel installation error. For example: Setting up initramfs-tools (0.98.8ubuntu3) ... update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools ... update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic gzip: stdout: No space left on device E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic dpkg: error processing initramfs-tools (--configure): subprocess installed post-installation script returned error exit status 1 Ideal behavior: Give a more helpful error message when this unfortunate situation occurs so that user can fix the broken system and keep it going. Workaround: As the bug reporting system forwards user to this bug report, such instructions can be given here: https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/798414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1716069] [NEW] systemd breaks apparmor (<2.10.95-1). in turn mysql-server wont install
Public bug reported: mysql-server cant be installed, because systemd (233-8ubuntu1~ubuntu16.04.1) requires a newer version of apparmor than the installed version 2.10.95-0ubuntu2.7 this in tune breaks various packages depending on mysql-server, like gnu-cash or others. Possible solutions: - provide a newer apparmor package for ubuntu 16.04.1 - provide a mysql-server package not depending on apparmor - provide a systemd package working with apparmor 2.10.95-0ubuntu2.7 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1716069 Title: systemd breaks apparmor (<2.10.95-1). in turn mysql-server wont install Status in apparmor package in Ubuntu: New Bug description: mysql-server cant be installed, because systemd (233-8ubuntu1~ubuntu16.04.1) requires a newer version of apparmor than the installed version 2.10.95-0ubuntu2.7 this in tune breaks various packages depending on mysql-server, like gnu-cash or others. Possible solutions: - provide a newer apparmor package for ubuntu 16.04.1 - provide a mysql-server package not depending on apparmor - provide a systemd package working with apparmor 2.10.95-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1716069/+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 1708021] Re: package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
No I was not able to find anything except messages about deprecated entries in /etc/ssh/sshd_config and /etc/ssh/ssh_config Maybe this is the problem? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1708021 Title: package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in openssh package in Ubuntu: Incomplete Bug description: Package does not install completely, but seems to function afterwards. Maybe it is because sshd may be restarted even if forked daemons are running serving existing connections. Does the upgrading routine take these into account while upgrading? ProblemType: Package DistroRelease: Ubuntu 17.10 Package: openssh-server 1:7.5p1-5ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 22:34:24 2017 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2014-02-10 (1268 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: openssh Title: package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to artful on 2017-06-12 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1708021/+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 1708021] [NEW] package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Public bug reported: Package does not install completely, but seems to function afterwards. Maybe it is because sshd may be restarted even if forked daemons are running serving existing connections. Does the upgrading routine take these into account while upgrading? ProblemType: Package DistroRelease: Ubuntu 17.10 Package: openssh-server 1:7.5p1-5ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 22:34:24 2017 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2014-02-10 (1268 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: openssh Title: package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to artful on 2017-06-12 (50 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1708021 Title: package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Status in openssh package in Ubuntu: New Bug description: Package does not install completely, but seems to function afterwards. Maybe it is because sshd may be restarted even if forked daemons are running serving existing connections. Does the upgrading routine take these into account while upgrading? ProblemType: Package DistroRelease: Ubuntu 17.10 Package: openssh-server 1:7.5p1-5ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Tue Aug 1 22:34:24 2017 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2014-02-10 (1268 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5~beta1 SourcePackage: openssh Title: package openssh-server 1:7.5p1-5ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to artful on 2017-06-12 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1708021/+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 1579557] Re: lightdm will not start
Same here. "dpkg-reconfigure lightdm" does not help out. Lightdm seems to be started, but then is terminated because of "respawning to fast". lightdm log: [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.22.0, UID=0 PID=2079 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-lightdm-gtk-greeter.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/60-xubuntu.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf.d/10-xubuntu.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Monitoring logind for seats [+0.01s] DEBUG: New seat added from logind: seat0 [+0.01s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.01s] DEBUG: Seat seat0: Starting [+0.01s] DEBUG: Seat seat0: Creating greeter session [+0.01s] DEBUG: Seat seat0: Creating display server of type x [+0.02s] DEBUG: Using VT 7 [+0.02s] DEBUG: Seat seat0: Starting local X display on VT 7 [+0.02s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.02s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.02s] DEBUG: XServer 0: Launching X Server [+0.02s] DEBUG: Launching process 2087: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch [+0.02s] DEBUG: XServer 0: Waiting for ready signal from X server :0 [+0.02s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.02s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.02s] DEBUG: Loading users from org.freedesktop.Accounts [+0.73s] DEBUG: Got signal 10 from process 2087 [+0.73s] DEBUG: XServer 0: Got signal from X server :0 [+0.73s] DEBUG: XServer 0: Connecting to XServer :0 [+0.73s] DEBUG: Launching process 2215: /usr/share/lightdm_xrandr [+0.75s] DEBUG: Process 2215 exited with return value 1 [+0.75s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1 [+0.75s] DEBUG: Seat seat0: Stopping display server due to failed setup script [+0.75s] DEBUG: Sending signal 15 to process 2087 [+1.17s] DEBUG: Process 2087 exited with return value 0 [+1.17s] DEBUG: XServer 0: X server stopped [+1.17s] DEBUG: Releasing VT 7 [+1.17s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0 [+1.17s] DEBUG: Seat seat0: Display server stopped [+1.17s] DEBUG: Seat seat0: Stopping session [+1.17s] DEBUG: Seat seat0: Session stopped [+1.17s] DEBUG: Seat seat0: Stopping; greeter display server failed to start [+1.17s] DEBUG: Seat seat0: Stopping [+1.17s] DEBUG: Seat seat0: Stopped [+1.17s] DEBUG: Required seat has stopped [+1.17s] DEBUG: Stopping display manager [+1.17s] DEBUG: Display manager stopped [+1.17s] DEBUG: Stopping daemon [+1.17s] DEBUG: Exiting with return value 1 And x-0.log: X.Org X Server 1.19.3 Release Date: 2017-03-15 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-70-generic x86_64 Ubuntu Current Operating System: Linux nc404-muc 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash Build Date: 28 March 2017 06:16:52AM xorg-server 2:1.19.3-1ubuntu1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Tue May 23 16:25:05 2017 (==) Using system config directory "/usr/share/X11/xorg.conf.d" VMware: No 3D enabled (0,
[Touch-packages] [Bug 1666331] [NEW] dnsmasq may be started before all interfaces are avaliable
Public bug reported: dnsmasq may be started before all interfaces are available. In such cases dnsmasq may quit or never bind to upcomming interfaces. In both cases dns name resolution wont work. I could notice this together with dynamicaly created interfaces by - VMware Workstation - VBox-Interfaces - KVM-Interfaces restarting dnsmasq after these interfaces are started solves the problem, but until then dns-name-resolution wont work as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.1 Uname: Linux 4.9.11+ x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Feb 20 23:33:31 2017 InstallationDate: Installed on 2011-10-19 (1951 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dnsmasq.conf: 2014-03-15T19:27:33.287995 ** Affects: dnsmasq (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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1666331 Title: dnsmasq may be started before all interfaces are avaliable Status in dnsmasq package in Ubuntu: New Bug description: dnsmasq may be started before all interfaces are available. In such cases dnsmasq may quit or never bind to upcomming interfaces. In both cases dns name resolution wont work. I could notice this together with dynamicaly created interfaces by - VMware Workstation - VBox-Interfaces - KVM-Interfaces restarting dnsmasq after these interfaces are started solves the problem, but until then dns-name-resolution wont work as expected. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1ubuntu0.16.04.1 Uname: Linux 4.9.11+ x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Feb 20 23:33:31 2017 InstallationDate: Installed on 2011-10-19 (1951 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.dnsmasq.conf: 2014-03-15T19:27:33.287995 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1666331/+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 1666269] Re: "halt -p" reboots instead powering off system
System powers off if booted from Debian testing, Knoppix 7.7.1 or FreeBSD 11.0. It also powers off if booted from Ubuntu 14.04.5. But not if booted from Ubuntu 16.04.2 (on HD) or Ubuntu 16.10 (life-DVD). -- 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/1666269 Title: "halt -p" reboots instead powering off system Status in systemd package in Ubuntu: New Bug description: giving "halt -p" or "shutdown -p now" reboots system instead off powering off. I have tried some kernel commandline options already, but without success: - reboot=bios - acpi=noirq but none did help. System keeps rebooting on "poweroff", "halt -p" or "shutdown -p now" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu17 Uname: Linux 4.9.11+ x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Feb 20 18:02:37 2017 InstallationDate: Installed on 2011-10-19 (1950 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1666269/+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 1666269] [NEW] "halt -p" reboots instead powering off system
Public bug reported: giving "halt -p" or "shutdown -p now" reboots system instead off powering off. I have tried some kernel commandline options already, but without success: - reboot=bios - acpi=noirq but none did help. System keeps rebooting on "poweroff", "halt -p" or "shutdown -p now" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu17 Uname: Linux 4.9.11+ x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Feb 20 18:02:37 2017 InstallationDate: Installed on 2011-10-19 (1950 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug package-from-proposed 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/1666269 Title: "halt -p" reboots instead powering off system Status in systemd package in Ubuntu: New Bug description: giving "halt -p" or "shutdown -p now" reboots system instead off powering off. I have tried some kernel commandline options already, but without success: - reboot=bios - acpi=noirq but none did help. System keeps rebooting on "poweroff", "halt -p" or "shutdown -p now" ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu17 Uname: Linux 4.9.11+ x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Feb 20 18:02:37 2017 InstallationDate: Installed on 2011-10-19 (1950 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1666269/+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 1644626] [NEW] Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5
Public bug reported: After having managed to have a 1024x768 lightdm screen displayed begging to login, I've tried and being prompted with "You where logged in with cached credentials". Not really: I am logged in, but immediately thrown out again. It is impossible to work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 19:32:58 2016 InstallationDate: Installed on 2014-02-10 (1017 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) IpRoute: default via 10.160.0.1 dev eth1 10.160.0.0/16 dev eth1 proto kernel scope link src 10.160.2.45 169.254.0.0/16 dev eth0 scope link metric 1000 172.18.8.0/24 dev eth0 proto kernel scope link src 172.18.8.141 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago) ftp_proxy: http://proxy01-muc.bfs.de:8080/ http_proxy: http://proxy01-muc.bfs.de:8080/ nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Kabelnetzwerkverbindung 1 c6be5d5a-c232-41e9-ae61-28f7974f30a9 802-3-ethernet 1397215392 Fr 11 Apr 2014 13:23:12 CEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- eth1ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started none enabled enabled enabled enabled enabled no_proxy: 127.0.0.1, localhost ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1644626 Title: Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5 Status in network-manager package in Ubuntu: New Bug description: After having managed to have a 1024x768 lightdm screen displayed begging to login, I've tried and being prompted with "You where logged in with cached credentials". Not really: I am logged in, but immediately thrown out again. It is impossible to work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 19:32:58 2016 InstallationDate: Installed on 2014-02-10 (1017 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) IpRoute: default via 10.160.0.1 dev eth1 10.160.0.0/16 dev eth1 proto kernel scope link src 10.160.2.45 169.254.0.0/16 dev eth0 scope link metric 1000 172.18.8.0/24 dev eth0 proto kernel scope link src 172.18.8.141 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago) ftp_proxy: http://proxy01-muc.bfs.de:8080/ http_proxy: http://proxy01-muc.bfs.de:8080/ nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Kabelnetzwerkverbindung 1 c6be5d5a-c232-41e9-ae61-28f7974f30a9 802-3-ethernet 1397215392 Fr 11 Apr 2014 13:23:12 CEST yes 0
[Touch-packages] [Bug 1644624] [NEW] lightdm does not start after upgrade from 14.04.5 to 16.04.1
Public bug reported: After upgrading from 14.04.5 to 16.04.1 lightdm does not start. Only error I could find reported was: [+0.19s] DEBUG: Launching process 1927: /usr/share/lightdm_xrandr [+0.21s] DEBUG: Process 1927 exited with return value 1 [+0.21s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1 [+0.21s] DEBUG: Seat seat0: Stopping display server due to failed setup script [+0.21s] DEBUG: Sending signal 15 to process 1922 [+0.59s] DEBUG: Process 1922 exited with return value 0 Looking at /usr/share/lightdm_xrandr output: #!/bin/sh xrandr --output Virtual1 --primary --mode 1920x1200 # /usr/share/lightdm_xrandr xrandr: Failed to get size of gamma for output default warning: output Virtual1 not found; ignoring # xrandr --listproviders Providers: number : 0 # xrandr --listmonitors xrandr: Failed to get size of gamma for output default Monitors: 1 0: +*default 1920/508x1200/317+0+0 default Changing xrandr --output Virtual1 --primary --mode 1920x1200 to xrandr --output default --primary --mode 1920x1200 leads to display of 1024x768 on a monitor capable of 1920x1200. Doesn't look nice! It worked with 14.04.5 seamless. I'd never had to think of it until upgrading! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 19:19:53 2016 InstallationDate: Installed on 2014-02-10 (1017 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) LightdmConfig: [Seat:*] display-setup-script=/usr/share/lightdm_xrandr greeter-session=lightdm-gtk-greeter user-session=xubuntu ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1644624 Title: lightdm does not start after upgrade from 14.04.5 to 16.04.1 Status in lightdm package in Ubuntu: New Bug description: After upgrading from 14.04.5 to 16.04.1 lightdm does not start. Only error I could find reported was: [+0.19s] DEBUG: Launching process 1927: /usr/share/lightdm_xrandr [+0.21s] DEBUG: Process 1927 exited with return value 1 [+0.21s] DEBUG: Seat seat0: Exit status of /usr/share/lightdm_xrandr: 1 [+0.21s] DEBUG: Seat seat0: Stopping display server due to failed setup script [+0.21s] DEBUG: Sending signal 15 to process 1922 [+0.59s] DEBUG: Process 1922 exited with return value 0 Looking at /usr/share/lightdm_xrandr output: #!/bin/sh xrandr --output Virtual1 --primary --mode 1920x1200 # /usr/share/lightdm_xrandr xrandr: Failed to get size of gamma for output default warning: output Virtual1 not found; ignoring # xrandr --listproviders Providers: number : 0 # xrandr --listmonitors xrandr: Failed to get size of gamma for output default Monitors: 1 0: +*default 1920/508x1200/317+0+0 default Changing xrandr --output Virtual1 --primary --mode 1920x1200 to xrandr --output default --primary --mode 1920x1200 leads to display of 1024x768 on a monitor capable of 1920x1200. Doesn't look nice! It worked with 14.04.5 seamless. I'd never had to think of it until upgrading! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 19:19:53 2016 InstallationDate: Installed on 2014-02-10 (1017 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) LightdmConfig: [Seat:*] display-setup-script=/usr/share/lightdm_xrandr greeter-session=lightdm-gtk-greeter user-session=xubuntu ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1644624/+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 1638388] Re: NetworkManager wont start at system boot
The bug report was generated on a migrated system. -- 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/1638388 Title: NetworkManager wont start at system boot Status in network-manager package in Ubuntu: New Bug description: From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478034710 Die 01 Nov 2016 22:11:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638388/+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 1638391] Re: NetworkManager wont apply configuration for all users at boot
The bug report was generated on a migrated system. -- 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/1638391 Title: NetworkManager wont apply configuration for all users at boot Status in network-manager package in Ubuntu: New Bug description: NetworkManager seems to ignore flag "Use this configuration for all users". The networkconfiguration is applied only for the one user who created it, not globally and this configuration is not applied at system boot! To have the system initialize network you'll have to log on with the user whom created the network configuration. Connect automaticly with this network: yes All users can use this network: yes Device: enp4s0 MTU: automatic WakeOnLAN: ON IPv4: dhcp IPv6: dhcp Network configuration at boot: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if some user logs in: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if the user whom created the network configuration logs in: # ifconfig enp4s0Link encap:Ethernet Hardware Adresse 30:65:ec:34:10:2d inet Adresse:192.168.6.46 Bcast:192.168.6.255 Maske:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX-Pakete:11232 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:9933 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX-Bytes:8388681 (8.3 MB) TX-Bytes:2078949 (2.0 MB) Interrupt:17 loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) I am seeing this by some systems migrated from Ubuntu 14.04.5 to 16.04.1 and by some systems newly installed from DVD with 16.04.1 or 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:27:16 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478035610 Die 01 Nov 2016 22:26:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2
[Touch-packages] [Bug 1638391] [NEW] NetworkManager wont apply configuration for all users at boot
Public bug reported: NetworkManager seems to ignore flag "Use this configuration for all users". The networkconfiguration is applied only for the one user who created it, not globally and this configuration is not applied at system boot! To have the system initialize network you'll have to log on with the user whom created the network configuration. Connect automaticly with this network: yes All users can use this network: yes Device: enp4s0 MTU: automatic WakeOnLAN: ON IPv4: dhcp IPv6: dhcp Network configuration at boot: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if some user logs in: # ifconfig loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) Network configuration if the user whom created the network configuration logs in: # ifconfig enp4s0Link encap:Ethernet Hardware Adresse 30:65:ec:34:10:2d inet Adresse:192.168.6.46 Bcast:192.168.6.255 Maske:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metrik:1 RX-Pakete:11232 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:9933 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1000 RX-Bytes:8388681 (8.3 MB) TX-Bytes:2078949 (2.0 MB) Interrupt:17 loLink encap:Lokale Schleife inet Adresse:127.0.0.1 Maske:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metrik:1 RX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Fenster:0 TX-Pakete:4729 Fehler:0 Verloren:0 Überläufe:0 Träger:0 Kollisionen:0 Sendewarteschlangenlänge:1 RX-Bytes:431130 (431.1 KB) TX-Bytes:431130 (431.1 KB) I am seeing this by some systems migrated from Ubuntu 14.04.5 to 16.04.1 and by some systems newly installed from DVD with 16.04.1 or 16.04. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:27:16 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478035610 Die 01 Nov 2016 22:26:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638391 Title: NetworkManager wont apply configuration for all users at boot Status in network-manager package in
[Touch-packages] [Bug 1638388] [NEW] NetworkManager wont start at system boot
Public bug reported: >From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-09-08 (54 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-03-03T12:29:43.912070 mtime.conffile..etc.init.network-manager.conf: 2013-03-04T17:15:37.443693 nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH muc-ews e0d03730-1e06-4998-b508-157a5a2a2ad0 802-3-ethernet 1478034710 Die 01 Nov 2016 22:11:50 CET yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes enp4s0 activated /org/freedesktop/NetworkManager/ActiveConnection/0 CVJM 0eaf8330-35e8-4eae-a922-16f0547f5c87 802-11-wireless 0 never yes 0 no /org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638388 Title: NetworkManager wont start at system boot Status in network-manager package in Ubuntu: New Bug description: From time to time NetworkManager does not start at system boot. NetworkManager seems to be started, but being terminated immediately. Symptoms: * no network connection at system boot. * no network connection while logging in. * no network applet after logging in. NetworkManager isn't running after logging in. I have to execute "service NetworkManager restart". Problem: * since NetworkManager not running at system boot it is not possible to connect the system via ssh! You will need a console. Bad with headless servers: you are locked out of them after rebooting. Workaround: write a script trying to start NetworkManager every minute after reboot until it is running. Works so far, but it is a really bad hack! Seen this problem on systems migrated from Ubuntu 14.04.5 LTS to 16.04.1 LTS. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 Uname: Linux 4.8.6+ x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Nov 1 22:13:15 2016 InstallationDate: Installed on 2011-10-19 (1840 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.6.1 dev enp4s0 proto static metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 172.19.1.0/24 dev vmnet1 proto kernel scope link src 172.19.1.1 172.19.8.0/24 dev vmnet8 proto kernel scope link src 172.19.8.1 192.168.6.0/24 dev enp4s0 proto kernel scope link src 192.168.6.46 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true
[Touch-packages] [Bug 1630245] [NEW] after starting ubuntu 16.10 -- no keyboard, no mouse
Public bug reported: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in systemd package in Ubuntu: New Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1630245/+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 459730] Re: rsyslog doesn't create /dev/xconsole
/dev/xconsole isn't created if it isn't there. If /dev/xconsole exists
it is not taken to output logs as given in
/etc/rsyslog.d/50-default.conf.
Creating /dev/xconsole and changing user:group doesn't help. service
rsyslog restart doesn't have access to this pipe. It doesn't matter if
apparmore is active or not. The reported error is in all cases the same:
Jun 13 15:25:59 nc158-muc rsyslogd-2039: Could no open output pipe
'/dev/tty12': Permission denied [try http://www.rsyslog.com/e/2039 ]
Jun 13 15:25:59 nc158-muc rsyslogd-2039: Could no open output pipe
'/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
# ls -la /dev/tty
crw--w 1 root tty 4, 12 Jun 13 15:18 /dev/tty12
/dev/xconsole is destroyed every reboot.
If xconsole is installed /dev/xconsole should be created and used by
rsyslog. If /dev/tty12 is configured to printout all logs it should be
used by rsyslog if at least groups match!
# grep syslog /etc/group
tty:x:5:syslog
# ps axu | grep syslog
syslog5886 0.0 0.0 257916 1260 ?Ssl 15:25 0:00 rsyslogd
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Fix Released
Status in rsyslog package in Ubuntu:
Fix Released
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+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 1508470] Re: sshd wont start for 15.10
The problem is related to ignoring "noauto" in fstab. The system tries to mount a nonexisting fd using ufs and fails. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1508470 Title: sshd wont start for 15.10 Status in openssh package in Ubuntu: New Bug description: After upgrading to the latest available packages for Ubuntu 15.10 sshd will not start any more. The system aquires an address, but it does not start sshd. Result: no remote access. On servers this might be fatal, since it might be a headless one and without sshd running access is not possible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 Date: Wed Oct 21 15:41:42 2015 InstallationDate: Installed on 2012-12-12 (1042 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1508470/+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 1508470] [NEW] sshd wont start for 15.10
Public bug reported: After upgrading to the latest available packages for Ubuntu 15.10 sshd will not start any more. The system aquires an address, but it does not start sshd. Result: no remote access. On servers this might be fatal, since it might be a headless one and without sshd running access is not possible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 Date: Wed Oct 21 15:41:42 2015 InstallationDate: Installed on 2012-12-12 (1042 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1508470 Title: sshd wont start for 15.10 Status in openssh package in Ubuntu: New Bug description: After upgrading to the latest available packages for Ubuntu 15.10 sshd will not start any more. The system aquires an address, but it does not start sshd. Result: no remote access. On servers this might be fatal, since it might be a headless one and without sshd running access is not possible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 Date: Wed Oct 21 15:41:42 2015 InstallationDate: Installed on 2012-12-12 (1042 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1508470/+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 1508470] Re: sshd wont start for 15.10
PS: the bug is reported from a 14.04 system, for a 15.10 system. At the moment of writing, the 15.10 system is not accessible any more, because of sshd not running (or no open port for sshd. May be even a firewall problem). Seen it on: - 15.04 -- current, stable - 15.10 -- upcomming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1508470 Title: sshd wont start for 15.10 Status in openssh package in Ubuntu: New Bug description: After upgrading to the latest available packages for Ubuntu 15.10 sshd will not start any more. The system aquires an address, but it does not start sshd. Result: no remote access. On servers this might be fatal, since it might be a headless one and without sshd running access is not possible. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh (not installed) ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.16 Architecture: amd64 Date: Wed Oct 21 15:41:42 2015 InstallationDate: Installed on 2012-12-12 (1042 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2013-02-11 (981 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1508470/+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 1486988] [NEW] /etc/cgconfig.conf ignored - cgconfigd not working
Public bug reported: cgroup-lite installed, but daemon missing from cgroup-lite: # dpkg -l | grep cgroup ii cgmanager 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon ii cgmanager-utils 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon (utilities) ii cgroup-bin 0.38-1ubuntu2amd64 Tools to control and monitor control groups ii cgroup-lite 1.9 allLight-weight package to set up cgroups at system boot ii libcgmanager0:amd64 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon (client library) ii libcgmanager0:i386 0.24-0ubuntu7.3 i386 Central cgroup manager daemon (client library) ii libcgroup1 0.38-1ubuntu2amd64 Library to control and monitor control groups # dpkg -L cgroup-lite /. /usr /usr/share /usr/share/doc /usr/share/doc/cgroup-lite /usr/share/doc/cgroup-lite/copyright /usr/share/doc/cgroup-lite/changelog.gz /usr/bin /etc /etc/init /etc/init/cgroup-lite.conf /bin /bin/cgroups-mount /bin/cgroups-umount /usr/bin/cgroups-mount /usr/bin/cgroups-umount cgroup-bin and cgmanage -packages just give errors trying to use them: # cgm create memory CH method return sender=(null sender) - dest=(null destination) reply_serial=1 int32 -1 - cgroups unusable with Ubuntu 14.04 LTS?? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cgroup-lite 1.9 Uname: Linux 3.14.51+ x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 Date: Thu Aug 20 13:26:54 2015 InstallationDate: Installed on 2011-10-19 (1400 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: cgroup-lite UpgradeStatus: Upgraded to trusty on 2014-02-24 (541 days ago) ** Affects: cgroup-lite (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cgroup-lite in Ubuntu. https://bugs.launchpad.net/bugs/1486988 Title: /etc/cgconfig.conf ignored - cgconfigd not working Status in cgroup-lite package in Ubuntu: New Bug description: cgroup-lite installed, but daemon missing from cgroup-lite: # dpkg -l | grep cgroup ii cgmanager 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon ii cgmanager-utils 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon (utilities) ii cgroup-bin 0.38-1ubuntu2amd64 Tools to control and monitor control groups ii cgroup-lite 1.9 allLight-weight package to set up cgroups at system boot ii libcgmanager0:amd64 0.24-0ubuntu7.3 amd64 Central cgroup manager daemon (client library) ii libcgmanager0:i386 0.24-0ubuntu7.3 i386 Central cgroup manager daemon (client library) ii libcgroup1 0.38-1ubuntu2amd64 Library to control and monitor control groups # dpkg -L cgroup-lite /. /usr /usr/share /usr/share/doc /usr/share/doc/cgroup-lite /usr/share/doc/cgroup-lite/copyright /usr/share/doc/cgroup-lite/changelog.gz /usr/bin /etc /etc/init /etc/init/cgroup-lite.conf /bin /bin/cgroups-mount /bin/cgroups-umount /usr/bin/cgroups-mount /usr/bin/cgroups-umount cgroup-bin and cgmanage -packages just give errors trying to use them: # cgm create memory CH method return sender=(null sender) - dest=(null destination) reply_serial=1 int32 -1 - cgroups unusable with Ubuntu 14.04 LTS?? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cgroup-lite 1.9 Uname: Linux 3.14.51+ x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 Date: Thu Aug 20 13:26:54 2015 InstallationDate: Installed on 2011-10-19 (1400 days ago) InstallationMedia: Xubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) PackageArchitecture: all SourcePackage: cgroup-lite UpgradeStatus: Upgraded to trusty on 2014-02-24 (541 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgroup-lite/+bug/1486988/+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 1414925] [NEW] ntpd seems to add offsets instead of subtracting them
Public bug reported: ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New ** Affects: ntp (CentOS) Importance: Undecided Status: New ** Affects: ntp (Debian) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: runaway.log https://bugs.launchpad.net/bugs/1414925/+attachment/4306298/+files/runaway.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1414925 Title: ntpd seems to add offsets instead of subtracting them Status in ntp package in Ubuntu: New Status in ntp package in CentOS: New Status in ntp package in Debian: New Bug description: ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1414925/+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 1414925] Re: ntpd seems to add offsets instead of subtracting them
Seeing this behaviour on all distributions using ntp 4.2.6p5: - Ubuntu 14.04 - CentOS 6.5 - Orcale Linux 6.5 - Debian 7 Bug seems resolved in ntp 4.2.8 as available from http://www.ntp.org -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1414925 Title: ntpd seems to add offsets instead of subtracting them Status in ntp package in Ubuntu: New Status in ntp package in CentOS: New Status in ntp package in Debian: New Bug description: ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1414925/+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 1414925] Re: ntpd seems to add offsets instead of subtracting them
maybe it is a security problem if kerberos used: after a while your clock is of too much and you can't login any more. ** Also affects: ntp (CentOS) Importance: Undecided Status: New ** Also affects: ntp (Debian) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1414925 Title: ntpd seems to add offsets instead of subtracting them Status in ntp package in Ubuntu: New Status in ntp package in CentOS: New Status in ntp package in Debian: New Bug description: ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1414925/+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 1414925] Re: ntpd seems to add offsets instead of subtracting them
** No longer affects: ntp (CentOS) ** Bug watch added: CentOS Mantis #8140 http://bugs.centos.org/view.php?id=8140 ** Also affects: ntp (CentOS) via http://bugs.centos.org/view.php?id=8140 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1414925 Title: ntpd seems to add offsets instead of subtracting them Status in ntp package in Ubuntu: New Status in ntp package in CentOS: Unknown Status in ntp package in Debian: New Bug description: ntpd seems to add offsets instead of subtracting them from the running synchronized clock, leading to time running away fast in one direction -- forward if the offset is positive, -- backward if the offset is negative, until the offset reaches its maximum. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ntp 1:4.2.6.p5+dfsg-3ubuntu2.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Jan 27 08:25:55 2015 InstallationDate: Installed on 2014-02-10 (350 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) KernLog: NtpStatus: ntpq: read: Connection refused ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp UpgradeStatus: Upgraded to trusty on 2014-02-18 (342 days ago) modified.conffile..etc.ntp.conf: [modified] mtime.conffile..etc.ntp.conf: 2015-01-27T07:41:51.747605 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1414925/+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 697592] Re: unable to create socket on eth0 (210) for ::ffff:192.168.1.4#123
Fixed in a later release of ntpd ** Changed in: ntp (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/697592 Title: unable to create socket on eth0 (210) for :::192.168.1.4#123 Status in “ntp” package in Ubuntu: Fix Released Bug description: Binary package hint: ntp ntpd[738]: unable to create socket on eth0 (210) for :::192.168.1.4#123 ds ntpd[738]: failed to initialize interface for address :::192.168.1.4 ntpd[738]: bind() fd 22, family AF_INET6, port 123, scope 2, addr :::192.168.1.4, mcast=0 flags=0x11 fails: Invalid argument H? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ntp 1:4.2.4p8+dfsg-1ubuntu6 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic-pae 2.6.35.8 Uname: Linux 2.6.35-24-generic-pae i686 Architecture: i386 Date: Wed Jan 5 11:33:13 2011 InstallationMedia: Ubuntu-Server 10.10 Maverick Meerkat - Release i386 (20101007) NtpStatus: remote refid st t when poll reach delay offset jitter == 192.168.1.255 .BCST. 16 u- 6400.0000.000 0.001 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ntp mtime.conffile..etc.ntp.conf: 2011-01-04T17:58:09.340110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/697592/+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 1378723] Re: Err http://de.archive.ubuntu.com trusty/universe amd64 Packages - 503 Service Unavailable
Had to do with the way proxys where addressed. Fixed with newer versions of tools used for apt ** Changed in: apt (Ubuntu) Status: New = 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/1378723 Title: Err http://de.archive.ubuntu.com trusty/universe amd64 Packages - 503 Service Unavailable Status in “apt” package in Ubuntu: Fix Released Bug description: Err http://de.archive.ubuntu.com trusty/universe amd64 Packages 503 Service Unavailable this is for various different servers. I found files Source.gz and Source.bz2 at http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/, but not Source. apt tried to download http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source; only and never tried http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source.gz; or http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source.bz2; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.4.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Wed Oct 8 11:09:03 2014 InstallationDate: Installed on 2014-01-31 (249 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-01-31 (249 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1378723/+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 1306563] Re: /etc/environment ignored
** Changed in: network-manager (Ubuntu) Status: New = Fix Released -- 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/1306563 Title: /etc/environment ignored Status in “network-manager” package in Ubuntu: Fix Released Bug description: Assume /etc/environment holding PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games ftp_proxy=http://proxy:8080/ http_proxy=http://proxy:8080/ https_proxy=http://proxy:8080/ gopher_proxy=http://proxy:8080/ no_proxy=127.0.0.1, localhost Since /etc/environment seems to be ignored since yesterday (10th, Apr. 2014), and no other global proxy definition was enabled, it is impossible to define proxy variables early while booting the system. In tune various things fail later on, including updates, because there is no internet access without using a proxy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1306563/+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 1284599] Re: login ignoring /etc/environment
** Changed in: shadow (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1284599 Title: login ignoring /etc/environment Status in “shadow” package in Ubuntu: Fix Released Bug description: If global variables are set in /etc/environment these settings are ignored loging in. Assume /etc/environmet holding proxy informations: ftp_proxy=http://proxy:8080 http_proxy=http://proxy:8080 https_proxy=http://proxy:8080 I'd assume these information exported in an users shell: # export [...] export ftp_proxy=http://proxy:8080 export http_proxy=http://proxy:8080 export https_proxy=http://proxy:8080 Since short this isn't the case any more. Settings in /etc/environmet are just ignored (or read, but not exported). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: login 1:4.1.5.1-1ubuntu9 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Tue Feb 25 12:35:24 2014 InstallationDate: Installed on 2014-01-31 (25 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: shadow UpgradeStatus: Upgraded to trusty on 2014-01-31 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1284599/+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 1306562] Re: network manager discards upstream DNS
** Changed in: network-manager (Ubuntu) Status: New = Fix Released -- 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/1306562 Title: network manager discards upstream DNS Status in “network-manager” package in Ubuntu: Fix Released Bug description: if an interface is not configured in /etc/network/interfaces network-manager takes this interface. Then dhclient is started, assigning an address and route. For DNS dnsmasq is configured to listen on localhost, then resolv.conf is configured to use the localy running dns. The upstream dns servers address is silently discarded, breaking dns resolution. Moving network-manager out of control (by adding the interface to /etc/network/interfaces) removes dnsmasq, but makes the whole thing work again, because the upstream dns is now entered into /etc/resolv.conf. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 11 13:45:01 2014 InstallationDate: Installed on 2014-02-10 (59 days ago) InstallationMedia: Xubuntu 13.10 Saucy Salamander - Release amd64 (20131016) IpRoute: default via 172.18.8.2 dev eth0 169.254.0.0/16 dev eth0 scope link metric 1000 172.18.8.0/24 dev eth0 proto kernel scope link src 172.18.8.141 IwConfig: eth0 no wireless extensions. lono wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=de_DE TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to trusty on 2014-02-18 (52 days ago) ftp_proxy: http://is-muc.bfs.de:8080/ http_proxy: http://is-muc.bfs.de:8080/ nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kabelnetzwerkverbindung 1 c6be5d5a-c232-41e9-ae61-28f7974f30a9 802-3-ethernet1397215392 Fr 11 Apr 2014 13:23:12 CEST yes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunmanaged /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled no_proxy: 127.0.0.1, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1306562/+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 854908] Re: update-initramfs ignoring plymouth-text theme files
Fixed ** Changed in: initramfs-tools (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/854908 Title: update-initramfs ignoring plymouth-text theme files Status in “initramfs-tools” package in Ubuntu: Fix Released Bug description: update-initramfs -v -u doesn't pack /lib/plymouth/theme/ubuntu-text/ubuntu-text.plymouth into the initrd. Thus no text fallback if the framebuffer could not initialize, only a blank screen. For other themes it is the same: libs (/lib/plymouth/*.so) are packed into the initrd, necessary theme files and scripts are missing. I've seen this with initramfs from today for lucid: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION=Ubuntu 10.04.3 LTS ii libplymouth2 0.8.2-2ubuntu2.2 graphical boot animation and logger - shared libraries ii plymouth 0.8.2-2ubuntu2.2 graphical boot animation and logger - main package ii plymouth-label0.8.2-2ubuntu2.2 graphical boot animation and logger - label control ii plymouth-theme-ubuntu-text0.8.2-2ubuntu2.2 graphical boot animation and logger - ubuntu-logo theme ii plymouth-theme-xompu 0.1-4 Plymouth theme for the Xompu GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/854908/+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 1378723] [NEW] Err http://de.archive.ubuntu.com trusty/universe amd64 Packages - 503 Service Unavailable
Public bug reported: Err http://de.archive.ubuntu.com trusty/universe amd64 Packages 503 Service Unavailable this is for various different servers. I found files Source.gz and Source.bz2 at http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/, but not Source. apt tried to download http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source; only and never tried http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source.gz; or http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source.bz2; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.4.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Wed Oct 8 11:09:03 2014 InstallationDate: Installed on 2014-01-31 (249 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-01-31 (249 days ago) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1378723 Title: Err http://de.archive.ubuntu.com trusty/universe amd64 Packages - 503 Service Unavailable Status in “apt” package in Ubuntu: New Bug description: Err http://de.archive.ubuntu.com trusty/universe amd64 Packages 503 Service Unavailable this is for various different servers. I found files Source.gz and Source.bz2 at http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/, but not Source. apt tried to download http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source; only and never tried http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source.gz; or http://de.archive.ubuntu.com/ubuntu/dists/trusty/main/source/Source.bz2; ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.4.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 Date: Wed Oct 8 11:09:03 2014 InstallationDate: Installed on 2014-01-31 (249 days ago) InstallationMedia: Ubuntu-Server 13.10 Saucy Salamander - Release amd64 (20131016) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-01-31 (249 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1378723/+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
