[Touch-packages] [Bug 1856091] Re: Gnome freeze
If the cursor still moves then Xorg is working. The rest of the screen is from gnome-shell/mutter so that's where this bug should be assigned. ** Summary changed: - Xorg freeze + Gnome freeze ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Gnome freeze + [amdgpu] Gnome freeze ** Tags added: amdgpu -- 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/1856091 Title: [amdgpu] kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds. Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 21:05:05 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:0b36] InstallationDate: Installed on 2019-11-07 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=2e5c8ff6-67d0-4aa4-ae83-63a0b2838d04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1
It appears libsnapd-glib1 uses around 300 KB of disk space and has minimal dependencies: Depends: libc6 (>= 2.4), libglib2.0-0 (>= 2.46), libjson-glib-1.0-0 (>= 1.2.0), libsoup2.4-1 (>= 2.39.2) Is there something undesirable here or is it just a matter of preference? Generally speaking I agree software dependencies have become absurd in some cases. But more objectively I would like to understand if there is some specific issue here. ** Tags added: bionic ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856054 Title: pulseaudio now depends on libsnapd-glib1 Status in pulseaudio package in Ubuntu: Incomplete Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856092] Re: Xorg freeze
*** This bug is a duplicate of bug 1855938 *** https://bugs.launchpad.net/bugs/1855938 ** This bug has been marked a duplicate of bug 1855938 Screen freezes and only mouse moves -- 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/1856092 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Opening another bug that is related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938 Saw this happen twice when working with google-chrome but, I uninstalled google-chrome but was able to reproduce this while simply navigating between virtual desktops. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 11 13:33:22 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc] InstallationDate: Installed on 2019-10-23 (49 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 dmi.modalias: dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545: dmi.product.family: Legion Y545 dmi.product.name: 81Q6 dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545 dmi.product.version: Legion Y545 dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-12-10T19:15:33.343829 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1856092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
OK then. We can say the bug was fixed in some Ubuntu versions but this might turn out to be one of those bugs where we don't know exactly where so can't backport the fix to older releases. ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released ** No longer affects: linux-hwe (Ubuntu) -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-pack
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
# rsync --version
rsync version 3.1.3 protocol version 31
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
I found these two probably related bug reports:
https://bugzilla.samba.org/show_bug.cgi?id=13913
https://bugzilla.samba.org/show_bug.cgi?id=13109
I am hitting this kind of bug when rsyncing a maildir (36000 files).
** Bug watch added: Samba Bugzilla #13913
https://bugzilla.samba.org/show_bug.cgi?id=13913
** Bug watch added: Samba Bugzilla #13109
https://bugzilla.samba.org/show_bug.cgi?id=13109
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804280] Re: intermittent periods of packet loss and high latency
I can confirm same problem in 4.15.0-72-generic. *-network description: Wireless interface product: Wireless-AC 9260 vendor: Intel Corporation physical id: 0 bus info: pci@:05:00.0 logical name: wlp5s0 version: 29 -- 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/1804280 Title: intermittent periods of packet loss and high latency Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Intermittently and unpredictably, ping response times and packet loss will spike to unusable levels. Normal ping times are about .25 ms for other hosts on the local network, with essentially no packet loss. During the problematic periods (usually lasting 2-10 minutes), packet loss jumps to about 50% and ping response times on the packets that aren't dropped jump to between 250 and 750 ms. This behavior started when I upgraded from Kubuntu 16.04 to Kubuntu 18.04. Changing which host on the network I test this with has no effect (and during this, those other hosts are able to use the network without any problem). Replacing the cable changes nothing. Using a different Ethernet interface changes nothing. Replacing the switch changes nothing. This is almost certainly not a hardware problem. There is a chance that using wireless instead of Ethernet would fix the issue, but I have been avoiding that since the wired connection is much faster when Kubuntu is not malfunctioning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Uname: Linux 4.15.0-39-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: KDE Date: Tue Nov 20 12:48:05 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (711 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via [removed] dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 [removed]/24 dev enp0s31f6 proto kernel scope link src [removed] metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-08-19 (92 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s31f6 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 2e0d0ce3-8ee2-3c06-815d-eb9a42873b3b /org/freedesktop/NetworkManager/ActiveConnection/5 [removed] btdisconnected /org/freedesktop/NetworkManager/Devices/5 -- ---- wlp3s0 wifi disconnected /org/freedesktop/NetworkManager/Devices/4 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dan2053 F pulseaudio /dev/snd/pcmC1D0c: dan2053 F...m pulseaudio /dev/snd/controlC1: dan2053 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=4eadd7fe-e046-471d-b0ee-f1c85365411e IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-12-09 (712 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp metric 100 169.254.0.0/16 dev enp0s31f6 scope link metric 1000 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.42 metric 100 MachineType: Dell Inc. Precision Tower 3420 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.1 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=89b1b98c-8c19-4200-966b-190a0ca0 ro quiet splas
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.montemar.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. [Other Info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
** Changed in: systemd (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent from the dhcp address it provided, 10.10.0.75, then this configuration will result in the client being unable to reach anything through the router, because all its packets will have a source address of 10.10.0.5, which the router would drop/reject. [regression potential] this only affects dhcp routes provided by a dhcp server using the 'static' or 'classless' route dhcp options. Since this behavior is currently the default when a system doesn't add static address(es) to interfaces that also get dhcp addresses, this is likely not a change in behavior for the vast majority of systems. And any systems that do add static address(es) would usually be able to route through a gateway from either the dhcp-provided, or static, address. So the regression potential for this change should be low. [other info] Note that systemd in Eoan is being upgraded to upstream 242, so I am not adding this to Eoan now, as I don't want to disturb the merge. If needed after the merge, I'll add to Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1835581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : h
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Has anybody engaged with upstream, as suggested by david in comment #15?
Filing a bug with Debian would also help, as we are carrying the same
package with no ubuntu modifications.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
In what rsync version and ubuntu release did you see it, @stooneb?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
Status in rsync package in Ubuntu:
Confirmed
Bug description:
In the last few months my home directory backup stopped completing.
I've been able to reproduce the problem on a single subdirectory
although I had to add the --debug=all flag to reproduce it on that
smaller directory. Specifically, this command never completes:
rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
The html2 directory is a copy of
gnuradio-3.7.8.1/build/docs/doxygen/html .
When I strace the command, I see this:
write(1, "sender finished /tmp/html2/atsc_"..., 58sender finished
/tmp/html2/atsc__interleaver_8h__incl.md5
) = 58
write(1, "send_files(338, /tmp/html2/atsc_"..., 59send_files(338,
/tmp/html2/atsc__interleaver_8h__incl.png)
) = 59
open("html2/atsc__interleaver_8h__incl.png", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=264657, ...}) = 0
write(1, "html2/atsc__interleaver_8h__incl"...,
37html2/atsc__interleaver_8h__incl.png
) = 37
read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\n\253\0\0\2\233\10\6\0\0\0h\242\""...,
262144) = 262144
select(6, [5], [4], [5], {60, 0}) = 2 (in [5], out [4], left {59,
96})
read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
write(4,
"r\311\0\7\177\377\232\237\264\272e\300\300\240\316\264&\314\301\252*\37\256y\225g\373^\315j\370\350"...,
51574) = 51574
select(5, [], [4], [], {60, 0}) = 1 (out [4], left {59, 97})
write(4,
"\7\320\0\7\177\377\234|\7X\223Y\273\255c\27\25f\306\212\202\214#E\272\212t\1\225A\fU"...,
53259) = 53259
select(5, [], [4], [], {60, 0}
The select command times out over and over. I get the same behavior
when trying to back up my entire home directory but I don't need the
--debug=all flag in that case.
lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04
apt-cache policy rsync
rsync:
Installed: 3.1.0-2ubuntu0.1
Candidate: 3.1.0-2ubuntu0.1
Version table:
*** 3.1.0-2ubuntu0.1 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386
Packages
500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386
Packages
100 /var/lib/dpkg/status
3.1.0-2 0
500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: rsync 3.1.0-2ubuntu0.1
ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
Uname: Linux 3.13.0-74-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: i386
CurrentDesktop: KDE
Date: Wed Dec 23 09:44:17 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2010-09-18 (1922 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta i386 (20100901.1)
SourcePackage: rsync
UpgradeStatus: Upgraded to trusty on 2014-12-27 (361 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856092] [NEW] Xorg freeze
Public bug reported: Opening another bug that is related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938 Saw this happen twice when working with google-chrome but, I uninstalled google-chrome but was able to reproduce this while simply navigating between virtual desktops. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 11 13:33:22 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:3ffc] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU116M [GeForce GTX 1660 Mobile] [17aa:3ffc] InstallationDate: Installed on 2019-10-23 (49 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: LENOVO 81Q6 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=8155cfb7-305e-41c0-9d80-fdf15d29e196 ro acpi=force SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN33WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 dmi.modalias: dmi:bvnLENOVO:bvrBHCN33WW:bd10/10/2019:svnLENOVO:pn81Q6:pvrLegionY545:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545: dmi.product.family: Legion Y545 dmi.product.name: 81Q6 dmi.product.sku: LENOVO_MT_81Q6_BU_idea_FM_Legion Y545 dmi.product.version: Legion Y545 dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-12-10T19:15:33.343829 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan freeze possible-manual-nvidia-install 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/1856092 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Opening another bug that is related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855938 Saw this happen twice when working with google-chrome but, I uninstalled google-chrome but was able to reproduce this while simply navigating between virtual desktops. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.l
[Touch-packages] [Bug 1856091] Re: Xorg freeze
I extracted the following from /var/log/syslog: Dec 11 20:53:17 solidus kernel: [ 6767.461655] INFO: task Xorg:3261 blocked for more than 120 seconds. Dec 11 20:53:17 solidus kernel: [ 6767.462842] Tainted: G OE 5.3.0-24-generic #26-Ubuntu Dec 11 20:53:17 solidus kernel: [ 6767.463851] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Dec 11 20:53:17 solidus kernel: [ 6767.464887] XorgD0 3261 3259 0x0004 Dec 11 20:53:17 solidus kernel: [ 6767.465947] Call Trace: Dec 11 20:53:17 solidus kernel: [ 6767.466998] __schedule+0x2b9/0x6c0 Dec 11 20:53:17 solidus kernel: [ 6767.468054] schedule+0x42/0xb0 Dec 11 20:53:17 solidus kernel: [ 6767.469116] schedule_timeout+0x203/0x2f0 Dec 11 20:53:17 solidus kernel: [ 6767.470187] ? __wake_up_common_lock+0x8a/0xc0 Dec 11 20:53:17 solidus kernel: [ 6767.471259] dma_fence_default_wait+0x1a5/0x290 Dec 11 20:53:17 solidus kernel: [ 6767.472335] ? dma_fence_free+0x20/0x20 Dec 11 20:53:17 solidus kernel: [ 6767.473421] dma_fence_wait_timeout+0xe7/0xf0 Dec 11 20:53:17 solidus kernel: [ 6767.474572] gmc_v10_0_flush_gpu_tlb+0x163/0x1a0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.475709] amdgpu_gart_bind+0x67/0x90 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.476838] amdgpu_ttm_gart_bind+0x78/0xc0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.478014] amdgpu_ttm_alloc_gart+0x21c/0x2e0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.479189] ? ttm_bo_unreserve+0x60/0x60 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.480356] amdgpu_vm_sdma_map_table+0x2f/0x40 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.481562] amdgpu_vm_clear_bo+0x170/0x3c0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.482703] ? _cond_resched+0x19/0x30 Dec 11 20:53:17 solidus kernel: [ 6767.483838] ? mutex_lock+0x13/0x40 Dec 11 20:53:17 solidus kernel: [ 6767.485044] amdgpu_vm_update_ptes+0x292/0x750 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.486233] ? _cond_resched+0x19/0x30 Dec 11 20:53:17 solidus kernel: [ 6767.487403] ? __kmalloc+0x180/0x270 Dec 11 20:53:17 solidus kernel: [ 6767.488641] amdgpu_vm_bo_update_mapping+0xb3/0xe0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.489887] amdgpu_vm_bo_update+0x317/0x720 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.491125] amdgpu_gem_va_ioctl+0x502/0x530 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.492345] ? idr_remove+0x11/0x20 Dec 11 20:53:17 solidus kernel: [ 6767.493607] ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.494849] drm_ioctl_kernel+0xae/0xf0 [drm] Dec 11 20:53:17 solidus kernel: [ 6767.496088] ? native_flush_tlb_others+0xc7/0x130 Dec 11 20:53:17 solidus kernel: [ 6767.497322] drm_ioctl+0x234/0x3d0 [drm] Dec 11 20:53:17 solidus kernel: [ 6767.498599] ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.499909] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Dec 11 20:53:17 solidus kernel: [ 6767.501163] do_vfs_ioctl+0x407/0x670 Dec 11 20:53:17 solidus kernel: [ 6767.502416] ksys_ioctl+0x67/0x90 Dec 11 20:53:17 solidus kernel: [ 6767.503691] __x64_sys_ioctl+0x1a/0x20 Dec 11 20:53:17 solidus kernel: [ 6767.504958] do_syscall_64+0x5a/0x130 Dec 11 20:53:17 solidus kernel: [ 6767.506226] entry_SYSCALL_64_after_hwframe+0x44/0xa9 Dec 11 20:53:17 solidus kernel: [ 6767.507528] RIP: 0033:0x7efbfec8867b Dec 11 20:53:17 solidus kernel: [ 6767.508826] Code: Bad RIP value. Dec 11 20:53:17 solidus kernel: [ 6767.510110] RSP: 002b:7ffbaad8 EFLAGS: 0246 ORIG_RAX: 0010 Dec 11 20:53:17 solidus kernel: [ 6767.511432] RAX: ffda RBX: 7ffbab20 RCX: 7efbfec8867b Dec 11 20:53:17 solidus kernel: [ 6767.512768] RDX: 7ffbab20 RSI: c0286448 RDI: 000d Dec 11 20:53:17 solidus kernel: [ 6767.514122] RBP: c0286448 R08: 80010e80 R09: 000e Dec 11 20:53:17 solidus kernel: [ 6767.515475] R10: 0017 R11: 0246 R12: 565559a24f90 Dec 11 20:53:17 solidus kernel: [ 6767.516844] R13: 000d R14: 00dec000 R15: 56555785e800 -- 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/1856091 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: On this occasion (and there have been many before), X froze (with cursor still movable) while using Firefox. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 21:05:05 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVar
[Touch-packages] [Bug 1856091] [NEW] Xorg freeze
Public bug reported: On this occasion (and there have been many before), X froze (with cursor still movable) while using Firefox. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 21:05:05 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:0b36] InstallationDate: Installed on 2019-11-07 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=2e5c8ff6-67d0-4aa4-ae83-63a0b2838d04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSULTRA:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSULTRA:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ULTRA dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 eoan freeze 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/1856091 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: On this occasion (and there have been many before), X froze (with cursor still movable) while using Firefox. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 11 21:05:05 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Once a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:731f] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [1002:0b36] InstallationDate: Installed on 2019-11-07 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ULTRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=2e5c8ff6-67d0-4aa4-ae83-63a0b2838d04 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ULTRA dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Def
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
> It really looks like as if systemd-resolved looked for the configured nameservers, recognized itself and took the other one as upstream. it may, it depends entirely on your network configuration, which I don't know. > Will look for where to create ticket for upstream systemd tomorrow. or when I next have time for it... https://github.com/systemd/systemd/issues if you do open a bug, please note it here; it's quite possible upstream will agree and fix it. I'll switch this back to 'confirmed' while waiting to hear an opinion from upstream. ** Changed in: systemd (Ubuntu) Status: Incomplete => Confirmed -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Confirmed Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1852016] Re: Applications delayed on launch
Changed status from (incomplete) to (new) as I think my comments provide
details to replicate this bug. I assume people who upgrade from 19.04
already have appmenu-gtk2-module installed. However, this is a serious
problem for people who make a fresh install of 19.10 and attempt to use
a GTK2 application. A quick Google search suggests this impacts users of
a wide range of programs that have not yet made the jump to a modern
widgetset.
** Changed in: dbus (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1852016
Title:
Applications delayed on launch
Status in dbus package in Ubuntu:
New
Bug description:
Hello,
i am unsure if this is really a problem with dbus but my first
research showed it could be related to dbus.
1.)
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 19.10
Release: 19.10
Codename: eoan
Ubuntu Budgie on T460 with 256GB SSD and 16GB RAM
2.)
dbus:
Installed: 1.12.14-1ubuntu2
Candidate: 1.12.14-1ubuntu2
Version table:
*** 1.12.14-1ubuntu2 500
500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
3.) I've expected just "normal" loading applications
4.) Some applications are delayed at startup. The application will
take around 30s to launch, but afterwards it just runs fine. Affected
application I found so far are KeepassXC, Filezilla and OnlyOffice
Desktop-Editor. From strace I saw this applications are stopping (for
about 20-30s) at this point:
connect(12, {sa_family=AF_UNIX, sun_path="/run/user/1000/bus"}, 110) = 0
getpid()= 8165
geteuid() = 1000
getegid() = 1000
getpid()= 8165
geteuid() = 1000
getegid() = 1000
sendmsg(12, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\0",
iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=28, cmsg_level=SOL_SOCKET,
cmsg_type=SCM_CREDENTIALS, cmsg_data={pid=8165, uid=1000, gid=1000}}],
msg_controllen=32, msg_flags=0}, MSG_NOSIGNAL) = 1
sendto(12, "AUTH\r\n", 6, MSG_NOSIGNAL, NULL, 0) = 6
recvfrom(12, "REJECTED EXTERNAL\r\n", 4096, 0, NULL, NULL) = 19
sendto(12, "AUTH EXTERNAL 31303030\r\n", 24, MSG_NOSIGNAL, NULL, 0) = 24
recvfrom(12, "OK 7f079149c4e5e774135107445dc85"..., 4096, 0, NULL, NULL) = 37
sendto(12, "NEGOTIATE_UNIX_FD\r\n", 19, MSG_NOSIGNAL, NULL, 0) = 19
recvfrom(12, "AGREE_UNIX_FD\r\n", 4096, 0, NULL, NULL) = 15
sendto(12, "BEGIN\r\n", 7, MSG_NOSIGNAL, NULL, 0) = 7
write(15, "\1\0\0\0\0\0\0\0", 8)= 8
eventfd2(0, EFD_CLOEXEC|EFD_NONBLOCK) = 14
write(14, "\1\0\0\0\0\0\0\0", 8)= 8
write(15, "\1\0\0\0\0\0\0\0", 8)= 8
poll([{fd=14, events=POLLIN}], 1, 25000) = 1 ([{fd=14, revents=POLLIN}])
read(14, "\1\0\0\0\0\0\0\0", 16)= 8
poll([{fd=14, events=POLLIN}], 1, 25000
During my first research I found this following to topics related to the
issue:
https://askubuntu.com/questions/1184774/some-applications-on-ubuntu-19-10-very-slow-to-start
This Stackoverflow topic links to the archlinux forum:
https://bbs.archlinux.org/viewtopic.php?id=230036
I can confirm that running the delayed applications with "dbus-launch
--exit-with-session application" or by running it as root they are all
starting without any delay.
Thanks for your help! Let me know if you need any further information.
Best Regards,
Sebastian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1852016/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
> you haven't told resolved about any upstream nameservers ... As I said, my original resolv.conf just had two nameserver entries, the local one (127.0.0.53) and the upstream one. >From that, all the diagnose-calls we did during this thread seemed to show that systemd-resolved DID know the upstream DNS. It really looks like as if systemd-resolved looked for the configured nameservers, recognized itself and took the other one as upstream. See for example comment #15: "DNS Servers: 10.2.2.3" in "Global" section. Will look for where to create ticket for upstream systemd tomorrow. or when I next have time for it... -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855941] Re: hwdb rules for remapping keys are not taking effect in X session
To whom it may concern or in case if someone will find this issue through search engines - try to delete hwdb.bin and regenerate it again - here is what I did: ``` $ sudo rm /etc/udev/hwdb.bin $ sudo udevadm hwdb --update $ sudo udevadm control --reload-rules $ sudo udevadm trigger $ sudo systemctl stop systemd-udevd $ sudo systemctl start systemd-udevd ``` And reboot - it's mandatory because until I haven't rebooted my laptop `xev` showed old values. P.S. Sorry for disturbance. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1855941 Title: hwdb rules for remapping keys are not taking effect in X session Status in systemd package in Ubuntu: Invalid Bug description: Steps to reproduce: - add custom hwdb rules for remapping keys (see the attach of my `cat /etc/udev/hwdb.d/61-ThinkPad-X240-keyboard.hwdb" for example) - run: $ sudo udevadm hwdb --update && sudo udevadm control --reload-rules && sudo udevadm trigger - and reboot PC to make sure that changes have took place What should happen: - changes should take place at TTY and in GUI session as well What happens: - changes take place in TTY session only while in GUI session something overrides these udev-based hwdb rules Now, a little bit more details. Here is my /etc/udev/hwdb.d/61-ThinkPad-X240-keyboard.hwdb: ``` # ThinkPad X240: # - switch End and Insert keys (so that when Fn-Lock is enabled, End works without Fn). # - switch Home/End <> PgUp/PgDn evdev:atkbd:dmi:bvn*:bvr*:bd*:svnLENOVO:pn*:pvrThinkPadX240:* KEYBOARD_KEY_c7=pageup KEYBOARD_KEY_cf=insert KEYBOARD_KEY_c9=home KEYBOARD_KEY_d1=end KEYBOARD_KEY_d2=pagedown # http://fliplinux.com/udev-hwdb-numlock-0.html ``` TL;DR: it did work recently, but after packages' update it did stop to work in X session (but in TTY session it still works according to custom configuration). I'm ready to provide any other detailed information. I use Ubuntu MATE 18.04 with the latest updates. It took a lot of time for me to make that keyboard configuration work properly because without that text processing (such as coding) is unbearable. And it was really great when I did manage to make it finally work by turning a few contradictory HOWTOs and advises from here and there into working solution. Until the recent packages' update. The most interesting part is that `evtest' shows logs according to hwdb settings while `xev' doesn't. So I have my hwdb configuration working at any TTY but not during X session. I tried even to downgrade a few packages manually such as udev and systemd (because they have been updated as well) but it didn't make it to work again. $ sudo evtest /dev/input/by-path/platform-i8042-serio-0-event-kbd ===> [pressing PgUp above LeftArrow] Event: time 1576021876.063189, -- SYN_REPORT ^[[5~Event: time 1576021876.524882, type 4 (EV_MSC), code 4 (MSC_SCAN), value c9 Event: time 1576021876.524882, type 1 (EV_KEY), code 102 (KEY_HOME), value 1 Event: time 1576021876.524882, -- SYN_REPORT Event: time 1576021876.587770, type 4 (EV_MSC), code 4 (MSC_SCAN), value c9 Event: time 1576021876.587770, type 1 (EV_KEY), code 102 (KEY_HOME), value 0 Event: time 1576021876.587770, -- SYN_REPORT ^[[5~Event: time 1576021876.857851, type 4 (EV_MSC), code 4 (MSC_SCAN), value c9 Event: time 1576021876.857851, type 1 (EV_KEY), code 102 (KEY_HOME), value 1 Event: time 1576021876.857851, -- SYN_REPORT Event: time 1576021876.920816, type 4 (EV_MSC), code 4 (MSC_SCAN), value c9 Event: time 1576021876.920816, type 1 (EV_KEY), code 102 (KEY_HOME), value 0 Event: time 1576021876.920816, -- SYN_REPORT # Yes, it's registrating KEY_HOME as it should ===> [pressing PgDn above RightArrow] Event: time 1576021931.761434, -- SYN_REPORT ^[[6~Event: time 1576021931.880086, type 4 (EV_MSC), code 4 (MSC_SCAN), value d1 Event: time 1576021931.880086, type 1 (EV_KEY), code 107 (KEY_END), value 1 Event: time 1576021931.880086, -- SYN_REPORT Event: time 1576021931.926910, type 4 (EV_MSC), code 4 (MSC_SCAN), value d1 Event: time 1576021931.926910, type 1 (EV_KEY), code 107 (KEY_END), value 0 Event: time 1576021931.926910, -- SYN_REPORT ^[[6~Event: time 1576021932.037671, type 4 (EV_MSC), code 4 (MSC_SCAN), value d1 Event: time 1576021932.037671, type 1 (EV_KEY), code 107 (KEY_END), value 1 Event: time 1576021932.037671, -- SYN_REPORT Event: time 1576021932.092536, type 4 (EV_MSC), code 4 (MSC_SCAN), value d1 Event: time 1576021932.092536, type 1 (EV_KEY), cod
[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved
> although from comment #4 it sounds like it might be a regression
caused by a security fix.
it's not a security fix, it's a patch to get resolved working with specific
broken captive portals, from bug 1727237 and bug 1766969. It was proposed
upstream in this PR:
https://github.com/systemd/systemd/pull/8608
but was never accepted upstream, only added to Ubuntu. As this bug
shows, the patch does appear to actually still cause problems for people
even without DNSSEC on (that problem was fixed in Ubuntu separately with
bug 1796501).
Fixing dnsmasq is good, but at some point we'll need to properly fix
upstream to workaround buggy captive portals in a way that doesn't cause
other problems.
--
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/1785383
Title:
missing EDNS0 record confuses systemd-resolved
Status in systemd:
Fix Released
Status in dnsmasq package in Ubuntu:
Triaged
Status in systemd package in Ubuntu:
Triaged
Status in dnsmasq source package in Bionic:
Triaged
Status in systemd source package in Bionic:
New
Bug description:
[Impact]
dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to get confused by
this in certain circumstances; when using the stub resolver and requesting an
address for which there are no records, there can sometimes be a five
second hang in resolution.
[Fix]
This is fixed by upstream commit
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78
Not sure if it is worth cherry picking? I imagine the most likely
trigger will be dnsmasq on routers which are not likely to be running
Ubuntu, but maybe just in case.
I also think there are some logic issues in systemd-resolved, upstream
bug filed:
https://github.com/systemd/systemd/issues/9785
[Test Case]
Simple-ish test case:
---
IFACE=dummy0
SUBNET=10.0.0
ip link add $IFACE type dummy
ifconfig $IFACE ${SUBNET}.1/24
dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo
--host-record=test.test,${SUBNET}.1 &
dig -t a test.test @10.0.0.1 | grep EDNS
# should return "; EDNS ..."
dig -t test.test @10.0.0.1 | grep EDNS
# again, should return "; EDNS ..." but doesn't
---
To reproduce the systemd-resolved side of the problem
---
# as above, but
# now configure systemd-resolved to look at only 10.0.0.1, then
systemd-resolve --reset-server-features
# should exhibit five second delay then connect, assuming sshd is running :)
ssh test.test
---
[Discussion]
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dnsmasq-base 2.79-1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Sat Aug 4 11:33:56 2018
InstallationDate: Installed on 2018-05-31 (64 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: dnsmasq
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1785383/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685754] Re: gnome-terminal unduly forces umask=0022
i have the same problem in Ubuntu 19.10 :-(
with best
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1685754
Title:
gnome-terminal unduly forces umask=0022
Status in gedit:
Invalid
Status in gnome-session:
New
Status in GNOME Terminal:
Unknown
Status in Nautilus:
Confirmed
Status in dbus package in Ubuntu:
Confirmed
Status in gnome-terminal package in Ubuntu:
Confirmed
Bug description:
In order to set the default umask of my users to 027 or 007, I
followed the instructions provided in 'man pam_umask' :
In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).
Then, MOST graphical applications systematically run with the correct
umask.
In particular, when I press Alt-F2, run 'xterm sh' and type 'umask',
it systematically displays 0007.
But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask',
it systematically displays 0022.
That is BAD, and is a security issue.
Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each
'~/.bashrc', add following content :
UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)"
if [ "$UMASK" ]; then
umask "${UMASK#$USER:*,umask=}"
fi
In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged.
Thank you in advance for a quick correction.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/1685754/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
For openvpn + systemd-resolve:
With "up / down" openvpn config file commands you can wrap "systemd-
resolve --set-dns=XXX" and update the given DNS servers.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
> In my resolv.conf I have now both 127.0.0.53 and the upstream dns each in their own "nameserver"-line. if you haven't told resolved about any upstream nameservers, there is no point in pointing resolv.conf to it. > "telnet" is just a simple tool to connect to tcp/ip endpoints, in case you didn't know, a bit like netcat, but more generally available ;-) lol, yes we're all aware of what telnet is :) > Good to know so early in the thread... If you do open an upstream bug, I'll be happy to follow it and backport any fix if appropriate, but I really do suggest you just fix your network to use a domain name. -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libusbmuxd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Confirmed Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: usbmuxd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Confirmed Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libimobiledevice (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Confirmed Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libplist (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices Status in libimobiledevice package in Ubuntu: Confirmed Status in libplist package in Ubuntu: Confirmed Status in libusbmuxd package in Ubuntu: Confirmed Status in usbmuxd package in Ubuntu: Confirmed Bug description: iOS 13 devices require updated libimobiledevice, libusbmuxd and usbmuxd to work correctly. Without the updates, the device appears to be accessible but it's impossible to copy files to the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: network-manager (Ubuntu Bionic) Importance: Undecided => High -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: network-manager (Ubuntu Bionic) Assignee: Olivier Tilloy (osomon) => Till Kamppeter (till-kamppeter) -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
Setting 'bionic' from "Fix Released" to "Confirmed" since 2 different persons stated the problem still exist (supported with reproducer testing) -- 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
I guess we could have two variables CODENAME and ??? and then you can say Ubuntu %(CODENAME)s '%(???)s' or like Ubuntu %(CODENAME)s <<%(???)s>> -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
e.g. for the french: #. Description #: ../data/templates/Ubuntu.info.in:158 msgid "Cdrom with Ubuntu 12.04 'Precise Pangolin'" msgstr "CD contenant Ubuntu 12.04 « Precise Pangolin »" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856054] [NEW] pulseaudio now depends on libsnapd-glib1
Public bug reported: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856054 Title: pulseaudio now depends on libsnapd-glib1 Status in pulseaudio package in Ubuntu: New Bug description: The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has libsnapd-glib1 as a dependency. This is complete and utter nonsense. I do not want cascading dependencies that have no business being installed on the systems I manage. Please rectify this at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
An example of dns update after putting:
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
in the openvpn .config file:
Wed Dec 11 15:04:25 2019 /etc/openvpn/update-resolv-conf tun0 1500 1558
10.172.67.194 255.255.192.0 init
update-resolv-conf uses:
[ -x /sbin/resolvconf ] || exit 0
so I guess it needs a systemd-resolved.service integration instead.
** Changed in: openvpn (Ubuntu)
Importance: Undecided => Medium
** Changed in: openvpn (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to
[Touch-packages] [Bug 1856056] [NEW] libassuan: autopkgtest regression in -release on amd64
Public bug reported: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Affects: libassuan (Ubuntu) Importance: Undecided Status: New ** Affects: wine (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New ** Also affects: wine (Ubuntu) Importance: Undecided Status: New ** Summary changed: - autopkgtest regression in -release on amd64 + libassuan: autopkgtest regression in -release on amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libassuan in Ubuntu. https://bugs.launchpad.net/bugs/1856056 Title: libassuan: autopkgtest regression in -release on amd64 Status in glibc package in Ubuntu: New Status in libassuan package in Ubuntu: New Status in wine package in Ubuntu: New Bug description: libassuan's autopkgtest seems to have regressed in -release on amd64 autopkgtest /usr/bin/i686-w64-mingw32-ld: /usr/x86_64-w64-mingw32/lib/libgpg-error.a: error adding symbols: file format not recognized collect2: error: ld returned 1 exit status autopkgtest [18:27:28]: test win32: ---] win32FAIL non-zero exit status 1 This regression is preventing glibc and wine from migrating from -proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1856056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794478] Re: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it
** Changed in: network-manager (Ubuntu Bionic) Status: Fix Released => Confirmed ** 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/1794478 Title: Automatic ipv4 not assigned to bond interface is manual ipv6 is assigned to it Status in Ubuntu on IBM z Systems: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Confirmed Bug description: ---Problem Description--- Bond interface with automatic ipv4 mode and manual ipv6 mode fails to get automatic ipv4 assigned from dhcp server. ---uname output--- Linux NetworkTest 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:42:17 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- When user configures ipv4 as automatic and ipv6 as manual for bond interface automatic ipv4 is not getting assigned. Looks like dhcp client request for ipv4 is not done to dhcp server after maunal ipv6 is assigned quickly to bond interface This issue will not happen in below cases: 1)with ipv4 automatic and ipv6 manual configuration for ethernet or vlan interface. 2)with ipv4 automatic and ipv6 automatic configuration for bond interface 3)with ipv4 automatic and ipv6 disabled configuration for bond interface Configuration: Bond interface, ipv4 automatic mode and ipv6 automatic mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=63e54542-5135-47ac-a954-b861c3937be2 type=bond interface-name=test_bond permissions= timestamp=1537944121 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy dns-search= method=auto From /var/log/syslog, we can see ip got assigned: Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPDISCOVER on test_bond to 255.255.255.255 port 67 interval 3 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPREQUEST of 10.2.3.55 on test_bond to 255.255.255.255 port 67 (xid=0x5e04bf1e) Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPOFFER of 10.2.3.55 from 10.2.3.1 Sep 26 06:26:26 NetworkTest dhclient[8663]: DHCPACK of 10.2.3.55 from 10.2.3.1 root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 28: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet 10.2.3.55/24 brd 10.2.3.255 scope global dynamic noprefixroute test_bond valid_lft 353sec preferred_lft 353sec inet6 fe80::ff:feb3:b522/64 scope link valid_lft forever preferred_lft forever +++ Bond interface, ipv4 automatic mode and ipv6 manual mode root@NetworkTest:/etc/NetworkManager/system-connections# cat test_bond [connection] id=test_bond uuid=3efb153a-a6e4-48fb-aa04-f0b8cb549bab type=bond interface-name=test_bond permissions= timestamp=1537943300 [ethernet] mac-address-blacklist= [bond] downdelay=0 fail_over_mac=none miimon=100 mode=active-backup num_grat_arp=0 primary_reselect=always updelay=0 [ipv4] dns-search= method=auto [ipv6] addr-gen-mode=stable-privacy address1=fe81::32a5:bc5f:287f:8db8/64 dns-search= method=manual No automatic ip assigned to ipv4 and no requests to dhcp server seen in /var/log/syslog root@NetworkTest:/etc/NetworkManager/system-connections# ip a s test_bond 29: test_bond: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 02:00:00:b3:b5:22 brd ff:ff:ff:ff:ff:ff inet6 fe81::32a5:bc5f:287f:8db8/64 scope link noprefixroute valid_lft forever preferred_lft forever ==> Correct LP-Package need to be assigned...! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1794478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: Navit FTBFS - cmake fix needed to work with newer pango
This bug was fixed in the package navit - 0.5.3+dfsg.1-2ubuntu1 --- navit (0.5.3+dfsg.1-2ubuntu1) focal; urgency=medium * d/rules: until resolved in cmake append the harfbuzz include directory directly to fix FTBFS (LP: #1855993) -- Christian Ehrhardt Wed, 11 Dec 2019 12:03:05 +0100 ** Changed in: navit (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: Navit FTBFS - cmake fix needed to work with newer pango Status in cmake package in Ubuntu: Triaged Status in navit package in Ubuntu: Fix Released Status in pango1.0 package in Ubuntu: Won't Fix Bug description: ## Cmake ## A change in Pango [1] broke builds using GTK2 as the pango source will include hb.h but miss the proper include paths. A fix was brought up in [2] and should be added to cmake in Focal to allow things to build with the new pango. Focal currently is at cmake 3.15.4-1 and [3] is a backport of that change to the 3.15 series. Note: after that is resolved navit will need a no change rebuild to pick up libgpsd25 which got me initially to find this issue. [1]: https://gitlab.gnome.org/GNOME/pango/commit/a7b17aa2bad77c485943c860a20aedc2b2b115ff [2]: https://gitlab.kitware.com/cmake/cmake/issues/19531 [3]: https://gitlab.kitware.com/cmake/cmake/commit/e4b1b79abb2b6e1ad07d36d4734554972c9ce4a9 --- original report --- ## Navit ## In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
> but it will bypass resolved completely In my resolv.conf I have now both 127.0.0.53 and the upstream dns each in their own "nameserver"-line. Just as in comment #17, but in the meantime I added domain and search lines. > you want to telnet to your local host? I really wanted to demonstrate what happens if I attempt to connect to a bare link local inet6 address as returned by systemd-resolved in the situation where it falls back to resolving $(hostname) using info from local network devices. "telnet" is just a simple tool to connect to tcp/ip endpoints, in case you didn't know, a bit like netcat, but more generally available ;-) > anyway, Ubuntu isn't the right place to take this up Good to know so early in the thread... -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856045] [NEW] capabilities set with setcap are not honoured
Public bug reported: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 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: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libcap2 (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 libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1856045 Title: capabilities set with setcap are not honoured Status in libcap2 package in Ubuntu: New Bug description: Hi, In Ubuntu 19.10 I set capabilities as; setcap cap_net_admin,cap_sys_admin+ep /bin/ip getcap /bin/ip /bin/ip = cap_net_admin,cap_sys_admin+ep but; > ip addr add 20.20.20.20/32 dev lo RTNETLINK answers: Operation not permitted *exactly* the same works perfect on 18.04.3 LTS. BTW the set of a silly address on "lo" is just an example. Nothing works on Ubuntu 19.10 Regards, ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libcap2-bin 1:2.25-2 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: Wed Dec 11 15:27:00 2019 InstallationDate: Installed on 2019-12-09 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: libcap2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1856045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855747] Re: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop
I fixed this by getting my system to boot with the correct drivers, so I can't easily do any further testing, I'm afraid. I'll mark this as Incomplete. ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1855747 Title: systemd-udevd appears to be attempting to load Nvidia kernel modules in a tight loop Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Bug description: I'm seeing these lines repeated: ``` Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:47 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Dec 09 12:01:48 surprise systemd-udevd[731]: nvidia: Process '/usr/bin/nvidia-smi' failed with exit code 9. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Dec 09 12:01:49 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Dec 09 12:01:50 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. ``` My system has been up ~an hour: $ uptime 12:02:28 up 1:00, 1 user, load average: 4.52, 4.80, 5.50 and I've seen a lot of these: $ journalctl -u systemd-udevd.service -b0 | grep -c "exit code 9" 1333 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 243-3ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13 Uname: Linux 5.3.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: i3 CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Mon Dec 9 11:59:10 2019 InstallationDate: Installed on 2019-05-07 (215 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-25-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash resume=UUID=73909634-a75d-42c9-8f66-a69138690756 vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2019-11-15 (23 days ago) dmi.bios.date: 01/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.apport.crashdb.conf: [modified] modified.conffile..etc.udev.udev.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2019-11-25T16:40:26.261317 mtime.conffile..etc.udev.udev.conf: 2019-11-28T09:22:42.096686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1855747/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
> Ok, so adding it to /etc/resolv.conf is actually one of the supported ways. well, I wouldn't call it 'supported' as you're then responsible for managing the resolv.conf file, but it will bypass resolved completely (assuming you don't put 127.0.0.53 in the file, and you only use your upstream nameserver(s)). The normal glibc getaddrinfo() that uses the resolv.conf entries to find nameserver(s) to query is of course supported no matter what you have in the resolv.conf file, but that rarely has bugs. > try connecting to that address: > > avl@fpc:~$ telnet fe80::4687:fcff:fe9e:4ac7 22 > Trying fe80::4687:fcff:fe9e:4ac7... > telnet: Unable to connect to remote host: Invalid argument you want to telnet to your local host? anyway, Ubuntu isn't the right place to take this up - you should open an upstream bug to systemd if this is an issue for you. -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
Is the factual incorrectness of "All the ipv6 addresses it resolves for its own hostname are reachable locally" understood? They are *only* reachable, if the interface is provided along with the link local inet6-address, but that extra condition isn't met. -- 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/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Incomplete Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850032] Re: scanbd prevents HP printers to work correctly with HPLIP
** Also affects: hplip Importance: Undecided Status: New -- 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/1850032 Title: scanbd prevents HP printers to work correctly with HPLIP Status in HPLIP: New Status in cups package in Ubuntu: New Status in hplip package in Ubuntu: New Status in scanbd package in Ubuntu: New Bug description: scandb installs a new udev rule with /lib/udev/rules.d/99-saned.rules This rule changes the permissions for hplip command hp-check -r _from_: -- | PERMISSION | -- USB None Required- -OK Node:'/dev/bus/usb/006/004' Perm:' root lp rw- rw- rw- rw- r--' _to_: -- | PERMISSION | -- USB None Required- -OK Node:'/dev/bus/usb/006/004' Perm:' root saned rw- rw- rw- rw- r--' The CONSEQUENCE is, that the HP printer doesn't print anymore. For more details please refer to https://forum.ubuntuusers.de/post/9107204/ To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1850032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855782] Re: Typo in the documentation: "systen" -> "system"
** Bug watch added: bugzilla.gnome.org/ #786829 https://bugzilla.gnome.org/show_bug.cgi?id=786829 ** Also affects: dconf via https://bugzilla.gnome.org/show_bug.cgi?id=786829 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1855782 Title: Typo in the documentation: "systen" -> "system" Status in dconf: Unknown Status in d-conf package in Ubuntu: Confirmed Bug description: Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have it fixed. The "NAME" section of dconf7 manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html) says "dconf - A configuration systen". "systen" should be a typo for "system". To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1855782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856006] Re: The repository 'http://ppa.launchpad.net/blaimi/phpmyadmin-omnibus/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be don
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reading your report it appears you are mostly after support. This bug report can be converted to a question (aimed at support, bug reports are aimed and finding problems and fixing so subsequent users won't stumble with the same issue). The PPA you added to your eoan (19.10) system only supports bionic (18.04), thus adding it was your mistake. PPA's are 3rd party repositories, where it's your responsibility to ensure they were created by a responsible party, are still maintained and are safe for your system (now and into the future). You then move to a different dependency issue, which again is support related, and not a bug with software. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community- support/709 -- 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/1856006 Title: The repository 'http://ppa.launchpad.net/blaimi/phpmyadmin- omnibus/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Status in openssh package in Ubuntu: Invalid Bug description: The repository 'http://ppa.launchpad.net/blaimi/phpmyadmin-omnibus/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. openssh-sftp-server : Depends: openssh-client (= 1:8.0p1-6build1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1856006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855782] Re: Typo in the documentation: "systen" -> "system"
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: d-conf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to d-conf in Ubuntu. https://bugs.launchpad.net/bugs/1855782 Title: Typo in the documentation: "systen" -> "system" Status in dconf: Unknown Status in d-conf package in Ubuntu: Confirmed Bug description: Found on 14.04, 16.04, and 18.04. 19.04 and later distributions have it fixed. The "NAME" section of dconf7 manpage(http://manpages.ubuntu.com/manpages/bionic/man7/dconf.7.html) says "dconf - A configuration systen". "systen" should be a typo for "system". To manage notifications about this bug go to: https://bugs.launchpad.net/dconf/+bug/1855782/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850032] Re: scanbd prevents HP printers to work correctly with HPLIP
** Information type changed from Public Security to Public -- 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/1850032 Title: scanbd prevents HP printers to work correctly with HPLIP Status in cups package in Ubuntu: New Status in hplip package in Ubuntu: New Status in scanbd package in Ubuntu: New Bug description: scandb installs a new udev rule with /lib/udev/rules.d/99-saned.rules This rule changes the permissions for hplip command hp-check -r _from_: -- | PERMISSION | -- USB None Required- -OK Node:'/dev/bus/usb/006/004' Perm:' root lp rw- rw- rw- rw- r--' _to_: -- | PERMISSION | -- USB None Required- -OK Node:'/dev/bus/usb/006/004' Perm:' root saned rw- rw- rw- rw- r--' The CONSEQUENCE is, that the HP printer doesn't print anymore. For more details please refer to https://forum.ubuntuusers.de/post/9107204/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1850032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856006] Re: The repository 'http://ppa.launchpad.net/blaimi/phpmyadmin-omnibus/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be don
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: openssh (Ubuntu) Status: New => Invalid -- 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/1856006 Title: The repository 'http://ppa.launchpad.net/blaimi/phpmyadmin- omnibus/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Status in openssh package in Ubuntu: Invalid Bug description: The repository 'http://ppa.launchpad.net/blaimi/phpmyadmin-omnibus/ubuntu eoan Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. openssh-sftp-server : Depends: openssh-client (= 1:8.0p1-6build1) E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1856006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767302] Re: User is not added to kvm group when installing gnome-boxes
FYI: adduser kvm solves that problem nope. added myself and still no joy. -- 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/1767302 Title: User is not added to kvm group when installing gnome-boxes Status in gnome-boxes package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in gnome-boxes source package in Bionic: Triaged Status in qemu source package in Bionic: Won't Fix Status in systemd source package in Bionic: Invalid Status in gnome-boxes source package in Cosmic: Invalid Status in qemu source package in Cosmic: Invalid Status in systemd source package in Cosmic: Fix Released Status in gnome-boxes source package in Disco: Invalid Status in qemu source package in Disco: Invalid Status in systemd source package in Disco: Fix Released Bug description: Installing gnome-boxes does not add the user to the needed kvm group. This leads to the problem that it is impossible to start any system within gnome-boxes. Gnome-Boxes throwes the error: CPU mode 'custom' for x86_64 kvm domain on x86_64 host is not supported by hypervisor adduser kvm solves that problem but how should an average user know that. Gnome-Boxes is not usable as of now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1767302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850667] Re: cgroup v2 is not fully supported yet, proceeding with partial confinement
https://github.com/lxc/lxd/issues/6587 When Ubuntu Eoan is booted with systemd.unified_cgroup_hierarchy, LXD cannot run Ubuntu Eoan in its container, but a small change to lxd/lxd/container_lxc.go enables LXD to operate as usual. ** Bug watch added: LXD bug tracker #6587 https://github.com/lxc/lxd/issues/6587 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1850667 Title: cgroup v2 is not fully supported yet, proceeding with partial confinement Status in docker.io package in Ubuntu: New Status in lxc package in Ubuntu: New Status in lxcfs package in Ubuntu: New Status in lxd package in Ubuntu: New Status in snapd package in Ubuntu: In Progress Bug description: Systemd upstream switched the default cgroup hierarchy to unified with v243. This change is reverted by the Ubuntu systemd packages, but as unified is the way to go per upstream support should be added to all relevant Ubuntu packges (and snaps): https://github.com/systemd/systemd/blob/v243/NEWS#L56 * systemd now defaults to the "unified" cgroup hierarchy setup during build-time, i.e. -Ddefault-hierarchy=unified is now the build-time default. Previously, -Ddefault-hierarchy=hybrid was the default. This change reflects the fact that cgroupsv2 support has matured substantially in both systemd and in the kernel, and is clearly the way forward. Downstream production distributions might want to continue to use -Ddefault-hierarchy=hybrid (or even =legacy) for their builds as unfortunately the popular container managers have not caught up with the kernel API changes. Systemd is rebuilt using the new default and is available from the following PPA for testing: https://launchpad.net/~rbalint/+archive/ubuntu/systemd-unified-cgh The autopkgtest results against other packges are available here: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified-cgh/?format=plain https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal-rbalint-systemd-unified-cgh/?format=plain lxc autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz snapd autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/s/snapd/20191030_161354_94b26@/log.gz docker.io autopkgtest failing: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan-rbalint-systemd-unified- cgh/eoan/amd64/d/docker.io/20191030_155944_2331e@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1850667/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855596] Re: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF
Please find attached a sample PDF demonstrating the problem.
It was produced by pdflatex on this file:
%%
% -*- compile-command: "pdflatex t1-test && evince t1-test.pdf" -*-
\documentclass[12pt,a4paper]{article}
% \usepackage[utf8]{inputenc}
\usepackage[T1]{fontenc}
\begin{document}
Just a little test:
Try to select some text in evince!
\end{document}
%%
** Attachment added: "sample pdf"
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+attachment/5311733/+files/t1-test.pdf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1855596
Title:
NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with
certain PDF
Status in poppler package in Ubuntu:
Confirmed
Bug description:
When viewing a certain PDF (which I unfortunately can't share) using
evince, a see a crash in libpoppler90. It's a NULL pointer dereference
in TextSelectionPainter::hasGlyphLessFont(), because in this certain
PDF, for whatever reason, sel->word->getFontName(0) may return NULL.
Attached you'll find a proposed patch increasing the robustness in
this case.
Cheers,
Enrik
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855596] Re: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: poppler (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1855596 Title: NULL ptr dereference in TextSelectionPainter::hasGlyphLessFont() with certain PDF Status in poppler package in Ubuntu: Confirmed Bug description: When viewing a certain PDF (which I unfortunately can't share) using evince, a see a crash in libpoppler90. It's a NULL pointer dereference in TextSelectionPainter::hasGlyphLessFont(), because in this certain PDF, for whatever reason, sel->word->getFontName(0) may return NULL. Attached you'll find a proposed patch increasing the robustness in this case. Cheers, Enrik To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1855596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
** Description changed: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" - The only grub helping is + The only grub option helping is mem_sleep_default=shallow - but that is a bit of no brainer as it suspends to S2 preventing S3. The - same effect have + but that is a bit of no brainer since it suspends to S2 preventing S3. + The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. - The issue does not seem graphics related as X wakes up correctly - (initially; it may crash later), and as the problem is identical even + The issue does not seem graphics related since X wakes up correctly + (initially; it may crash later), and since the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub option helping is mem_sleep_default=shallow but that is a bit of no brainer since it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related since X wakes up correctly (initially; it may crash later), and since the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-
[Touch-packages] [Bug 1855993] Re: Navit FTBFS - cmake fix needed to work with newer pango
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/navit/+git/navit/+merge/376628 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: Navit FTBFS - cmake fix needed to work with newer pango Status in cmake package in Ubuntu: Triaged Status in navit package in Ubuntu: Triaged Status in pango1.0 package in Ubuntu: Won't Fix Bug description: ## Cmake ## A change in Pango [1] broke builds using GTK2 as the pango source will include hb.h but miss the proper include paths. A fix was brought up in [2] and should be added to cmake in Focal to allow things to build with the new pango. Focal currently is at cmake 3.15.4-1 and [3] is a backport of that change to the 3.15 series. Note: after that is resolved navit will need a no change rebuild to pick up libgpsd25 which got me initially to find this issue. [1]: https://gitlab.gnome.org/GNOME/pango/commit/a7b17aa2bad77c485943c860a20aedc2b2b115ff [2]: https://gitlab.kitware.com/cmake/cmake/issues/19531 [3]: https://gitlab.kitware.com/cmake/cmake/commit/e4b1b79abb2b6e1ad07d36d4734554972c9ce4a9 --- original report --- ## Navit ## In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: Navit FTBFS - cmake fix needed to work with newer pango
I'm preparing an interim fix for navit to get out of the way of this and less dependent on the cmake fix. We can revert that once cmake is up to date. But sooner or later this should probably be fixed in cmake either with a backport or a move to the 3.16 version that has the change anyway. ** Changed in: pango1.0 (Ubuntu) Status: New => Won't Fix ** Changed in: navit (Ubuntu) Status: New => Triaged ** Changed in: navit (Ubuntu) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: Navit FTBFS - cmake fix needed to work with newer pango Status in cmake package in Ubuntu: Triaged Status in navit package in Ubuntu: Triaged Status in pango1.0 package in Ubuntu: Won't Fix Bug description: ## Cmake ## A change in Pango [1] broke builds using GTK2 as the pango source will include hb.h but miss the proper include paths. A fix was brought up in [2] and should be added to cmake in Focal to allow things to build with the new pango. Focal currently is at cmake 3.15.4-1 and [3] is a backport of that change to the 3.15 series. Note: after that is resolved navit will need a no change rebuild to pick up libgpsd25 which got me initially to find this issue. [1]: https://gitlab.gnome.org/GNOME/pango/commit/a7b17aa2bad77c485943c860a20aedc2b2b115ff [2]: https://gitlab.kitware.com/cmake/cmake/issues/19531 [3]: https://gitlab.kitware.com/cmake/cmake/commit/e4b1b79abb2b6e1ad07d36d4734554972c9ce4a9 --- original report --- ## Navit ## In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: FTBFS in focal blocking gpsd transition for libgps25
** Also affects: cmake (Ubuntu) Importance: Undecided Status: New ** Changed in: cmake (Ubuntu) Assignee: (unassigned) => Rik Mills (rikmills) ** Changed in: cmake (Ubuntu) Status: New => Triaged ** Description changed: + A change in Pango [1] broke builds using GTK2 as the pango source will + include hb.h but miss the proper include paths. + + A fix was brought up in [2] and should be added to cmake in Focal to + allow things to build with the new pango. + + Focal currently is at cmake 3.15.4-1 and [3] is a backport of that + change to the 3.15 series. + + Note: after that is resolved navit will need a no change rebuild to pick + up libgpsd25 which got me initially to find this issue. + + [1]: https://gitlab.gnome.org/GNOME/pango/commit/a7b17aa2bad77c485943c860a20aedc2b2b115ff + [2]: https://gitlab.kitware.com/cmake/cmake/issues/19531 + [3]: https://gitlab.kitware.com/cmake/cmake/commit/e4b1b79abb2b6e1ad07d36d4734554972c9ce4a9 + + + --- original report --- + In file included from /usr/include/pango-1.0/pango/pango-font.h:25, - from /usr/include/pango-1.0/pango/pango-attributes.h:25, - from /usr/include/pango-1.0/pango/pango.h:25, - from /usr/include/gtk-2.0/gdk/gdktypes.h:37, - from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, - from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, - from /usr/include/gtk-2.0/gdk/gdk.h:32, - from /usr/include/gtk-2.0/gtk/gtk.h:32, - from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: + from /usr/include/pango-1.0/pango/pango-attributes.h:25, + from /usr/include/pango-1.0/pango/pango.h:25, + from /usr/include/gtk-2.0/gdk/gdktypes.h:37, + from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, + from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, + from /usr/include/gtk-2.0/gdk/gdk.h:32, + from /usr/include/gtk-2.0/gtk/gtk.h:32, + from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory -28 | #include - | ^~ + 28 | #include + | ^~ compilation terminated. - - In file included from /usr/include/pango-1.0/pango/pango-font.h:25, - from /usr/include/pango-1.0/pango/pango-attributes.h:25, - from /usr/include/pango-1.0/pango/pango.h:25, - from /usr/include/gtk-2.0/gdk/gdktypes.h:37, - from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, - from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, - from /usr/include/gtk-2.0/gdk/gdk.h:32, - from /usr/include/gtk-2.0/gtk/gtk.h:32, - from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: + from /usr/include/pango-1.0/pango/pango-attributes.h:25, + from /usr/include/pango-1.0/pango/pango.h:25, + from /usr/include/gtk-2.0/gdk/gdktypes.h:37, + from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, + from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, + from /usr/include/gtk-2.0/gdk/gdk.h:32, + from /usr/include/gtk-2.0/gtk/gtk.h:32, + from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory -28 | #include - | ^~ + 28 | #include + | ^~ compilation terminated. - These are from no change rebuilds needed for libgps25, but something else made them break. ** Description changed: + ## Cmake ## + A change in Pango [1] broke builds using GTK2 as the pango source will include hb.h but miss the proper include paths. A fix was brought up in [2] and should be added to cmake in Focal to allow things to build with the new pango. Focal currently is at cmake 3.15.4-1 and [3] is a backport of that change to the 3.15 series. Note: after that is resolved navit will need a no change rebuild to pick up libgpsd25 which got me initially to find this issue. [1]: https://gitlab.gnome.org/GNOME/pango/commit/a7b17aa2bad77c485943c860a20aedc2b2b115ff [2]: https://gitlab.kitware.com/cmake/cmake/issues/19531 [3]: https://gitlab.kitware.com/cmake/cmake/commit/e4b1b79abb2b6e1ad07d36d4734554972c9ce4a9 + --- original report --- - --- original report --- + ## Navit ## In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25,
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
Attaching the dumps of: cat /proc/acpi/wakeup > wakeup echo > /sys/power/pm_test sync && echo 1 > /sys/power/pm_trace && pm-suspend dmesg > dmesg. ** Attachment added: "wakeup" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311723/+files/wakeup -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
** Attachment added: "dmesg.platform" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311726/+files/dmesg.platform -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
** Attachment added: "dmesg.processors" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311727/+files/dmesg.processors -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
** Attachment added: "dmesg.core" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311728/+files/dmesg.core -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
cat /sys/kernel/debug/suspend_stats > suspend_stats ** Attachment added: "suspend_stats" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311729/+files/suspend_stats -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
** Attachment added: "dmesg.freezer" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311724/+files/dmesg.freezer -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
** Attachment added: "dmesg.devices" https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+attachment/5311725/+files/dmesg.devices -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume Status in pm-utils package in Ubuntu: New Bug description: System apparently correctly suspends (in various ways - from gnome menu, with pm-suspend on bash, with echo ... > /sys/power/pm_test) and resumes bringing up X, gnome, consoles, mouse, keyboard - but not the nvme SSD. Since I have the OS on that, no command relying on disk files is recognized, and I'm forced to hard power off by long press on power button. Usually at resume it is possible to switch to consoles (Ctrl-Alt-Fn), which display a lot of messages about i/o errors and failing journal writes. bash may be still alive on either X or consoles, but it will understand only internal commands and thus it is not of much help even for shutting down the system cleanly. Tried to add the following options in various combinations on the GRUB_CMDLINE_LINUX at no avail: acpiphp.disable=1 nvme_core.default_ps_max_latency_us=0 acpi_osi=! \"acpi_osi=Windows 2015\" The only grub helping is mem_sleep_default=shallow but that is a bit of no brainer as it suspends to S2 preventing S3. The same effect have echo s2idle > /sys/power/mem_sleep and echo freeze > /sys/power/state As for what is said in https://wiki.ubuntu.com/DebuggingKernelSuspend, I've tried pm-tracing but wasn't able to understand enough information from dmesg hash matches. As for debugging, all echos to /sys/power/pm_test resume correctly but the last, echo none, which causes the problem. The issue does not seem graphics related as X wakes up correctly (initially; it may crash later), and as the problem is identical even with no X (telinit 3). Hope all necessary debug information is automatically added, if not please ask. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 10 16:08:33 2019 InstallationDate: Installed on 2019-10-29 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 295990] Re: Keyboard layout reset after attaching USB keyboard
I experience this bug on Raspbian, but not Arch. I don't have an Ubuntu system, but here is an easy way to reproduce it in software, which may be helpful: $ setxkbmap us basic $ setxkbmap us dvorak $ sudo udevadm trigger $ aoeuaoeusdfasdfasdf You can see that half-way through typing the last line, the layout changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/295990 Title: Keyboard layout reset after attaching USB keyboard Status in xserver-xorg-input-evdev: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in xkeyboard-config package in Ubuntu: Invalid Bug description: Binary package hint: gnome-control-center I use a laptop with Ubuntu 8.10, and has configured two keyboard layouts. I use "USA" as the default layout and "Sweden" as an alternative layout, and use for changing layout. 1) Description: Ubuntu 8.10 Release: 8.10 2) gnome-control-center: Installed: 1:2.24.0.1-0ubuntu7.1 Candidate: 1:2.24.0.1-0ubuntu7.1 Version table: *** 1:2.24.0.1-0ubuntu7.1 0 500 http://se.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 1:2.24.0.1-0ubuntu7 0 500 http://se.archive.ubuntu.com intrepid/main Packages 3) When I plug in an USB keyboard it should still be possible to change between the default and alternative layout with or using the applet menu. The default and any alternative layout should user configurable, i.e. it should not restore system default values when an USB keyboard is attached. 4) When I plug in an USB keyboard after logging in to Ubuntu, it resets the keyboard layout (and probably other keyboard settings as well) to the system default layout which is stored in /etc/default/console-setup. To manage notifications about this bug go to: https://bugs.launchpad.net/evdev/+bug/295990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845046] Re: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected
Same issue here with Sony WH-1000XM3 and Ubuntu 19.10. When it connects automatically it connects with HSP and I'm not able to select A2DP in Bluez. However when I disconnect the headset using bluez and reconnect it as Audio Sink, it works properly. -- 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/1845046 Title: Bluetooth headphones/speaker default to low quality headset mode and fails to switch to A2DP when selected Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: FTBFS in focal blocking gpsd transition for libgps25
navit last time built fine in Eoan on 2019-09-10 Comparing the environments between late Eoan and Focal... The Eoan version of pango-coverage.h doesn't have the include that is failing me. ** Bug watch added: gitlab.kitware.com/cmake/cmake/issues #19531 https://gitlab.kitware.com/cmake/cmake/issues/19531 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: FTBFS in focal blocking gpsd transition for libgps25 Status in navit package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/navit/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: FTBFS in focal blocking gpsd transition for libgps25
#ubuntu-desktop was helpful: [11:29] cpaelzer, hey, it's https://gitlab.kitware.com/cmake/cmake/issues/19531 [11:29] RikMills, ^ [11:29] cpaelzer, we talked about it on friday on #ubuntu-release, we should backport that patch to cmake -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: FTBFS in focal blocking gpsd transition for libgps25 Status in navit package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/navit/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842643] Re: Update to 1.44
This is in Focal, lets close the bug pango1.0 | 1.44.7-1 | focal | source ** Changed in: pango1.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: Update to 1.44 Status in pango1.0 package in Ubuntu: Fix Released Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: FTBFS in focal blocking gpsd transition for libgps25
navit actually just naively includes and the error pups up much below that. It has #define GDK_ENABLE_BROKEN might that be related? Build dep is: libgtk2.0-dev Which brings in: libpango1.0-dev | 1.44.7-1 | focal | amd64, arm64, armhf, i386, ppc64el, s390x And that has the failing include: grep -Hn hb.h /usr/include/pango-1.0/pango/pango-coverage.h /usr/include/pango-1.0/pango/pango-coverage.h:28:#include The only occurrence of that is in: $ apt-file search 'hb.h' | grep -e '/hb\.h$' libharfbuzz-dev: /usr/include/harfbuzz/hb.h thunderbird-dev: /usr/include/thunderbird/harfbuzz/hb.h Odd, did it really want that one ...? ** Also affects: pango1.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: FTBFS in focal blocking gpsd transition for libgps25 Status in navit package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/navit/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855993] Re: FTBFS in focal blocking gpsd transition for libgps25
Added a pango1.0 task for awareness -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: FTBFS in focal blocking gpsd transition for libgps25 Status in navit package in Ubuntu: New Status in pango1.0 package in Ubuntu: New Bug description: In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/navit/+bug/1855993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
"realtime-scheduling = no" no change -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
there is sound after 18.10 (19.04, 19.10) -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1816429] Re: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card
it makes sense to wait for the next LTS version -- 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/1816429 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card Status in linux package in Ubuntu: Incomplete Status in linux-hwe package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: I'm having a sound problem ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: erkan 2121 F pulseaudio CurrentDesktop: Unity Date: Mon Feb 18 16:48:58 2019 InstallationDate: Installed on 2019-02-18 (0 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) SourcePackage: pulseaudio Symptom: audio Symptom_Card: bytcr-rt5651 - bytcr-rt5651 Title: [bytcr-rt5651 - bytcr-rt5651, playback] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-08 (2 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. Bus 001 Device 003: ID 1ea7:0066 Bus 001 Device 002: ID 6080:8060 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: I-Life Digital Technologies LLC ZED AIR TES Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=77349cb5-6380-4667-8fab-ff147aea5a2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.13 StagingDrivers: r8723bs Tags: bionic staging Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816429/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855297] Re: NetworkManager service fails to secure Ethernet connection when using kernel 5.4
Hmm, there are no dmesg attached. Can you please perform a kernel bisection? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855297 Title: NetworkManager service fails to secure Ethernet connection when using kernel 5.4 Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 network-manager: Installed: 1.20.4-2ubuntu2 Candidate: 1.20.4-2ubuntu2 Version table: *** 1.20.4-2ubuntu2 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status After going to kernel 5.4, from 5.3, I noticed the network systray roundel going 'round and 'round. On closer examination I could see that the Wi-fi had connected but the Ethernet connection was "obtaining IP address" --> fail --> back to "obtaining IP address" and continually going around and around. Doing a "service NetworkManager stop" and quickly following up with "service NetworkManager start" fixes the situation. However, if you leave any kind of a gap between the stop and start the issue described above starts up again. I also left a freshly booted system for quite a while and went back to it but the issue was still there, until the workaround described above was performed. Booting up in to kernel 5.3 the issue is not seen and all network interfaces connect as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 Uname: Linux 5.4.2-050402-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: KDE Date: Thu Dec 5 15:24:51 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-12-06 (729 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2019-11-13 (21 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu13 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2017-12-06 (734 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.20.4-2ubuntu3 PackageArchitecture: amd64 Tags: focal Uname: Linux 5.4.2-050402-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to focal on 2019-11-13 (26 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855628] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1855628 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1855628 Title: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: Whenever I wake the computer up from sleep, the computer no longer connects to the Internet without my having to go into Settings and turn Wi-Fi off and then back on again. Please address this issue. Thank you! network-manager: Installed: 1.10.6-2ubuntu1.2 Candidate: 1.10.6-2ubuntu1.2 Version table: *** 1.10.6-2ubuntu1.2 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.10.6-2ubuntu1.1 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages Description: Ubuntu 18.04.3 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Dec 8 19:51:31 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b wifi 1575852612 Sun 08 Dec 2019 07:50:12 PM EST yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- Wired connection 1 28634e82-4c1c-3a61-b152-3bd92aaa6992 ethernet 1575852610 Sun 08 Dec 2019 07:50:10 PM EST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/2 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 NETGEAR18 64704ba2-aba5-44de-ad4a-7d0de569815b /org/freedesktop/NetworkManager/ActiveConnection/1 enp4s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
https://git.launchpad.net/~ubuntu-audio- dev/pulseaudio/commit/?id=f9b05e494420e1951bf4d700c622f6760dedea18 ** Changed in: pulseaudio (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Committed Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Committed Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
** Description changed: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. + + --- + + WORKAROUND + + Comment out: + + load-module module-switch-on-port-available + load-module module-switch-on-connect + + from /etc/pulse/default.pa ** Changed in: pulseaudio (Ubuntu Focal) Status: Triaged => In Progress -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: In Progress Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: In Progress Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. --- WORKAROUND Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1856008] [NEW] issuse
Public bug reported: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed openssh-sftp-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed i will not installed the open ssh server ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1856008 Title: issuse Status in openssh package in Ubuntu: New Bug description: Check if you are using third party repositories. If so disable them, since they are a common source of problems. Furthermore run the following command in a Terminal: apt-get install -f Transaction failed: The package system is broken The following packages have unmet dependencies: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed openssh-sftp-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed i will not installed the open ssh server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1856008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
