[Touch-packages] [Bug 1831688] [NEW] Flickering triangles in OpenGL apps on Radeon KAVERI
Public bug reported: On (K)Ubuntu 18.04 I get strange triangles in almost all (I guess in all) apps using OpenGL. glxinfo | grep 'string\|version' prints the following: server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 GLX version: 1.4 Max core profile version: 4.5 Max compat profile version: 4.5 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: X.Org OpenGL renderer string: AMD KAVERI (DRM 2.50.0, 5.0.0-16-generic, LLVM 8.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.0-devel (git-73dda85 2019-06-04 bionic-oibaf-ppa) OpenGL core profile shading language version string: 4.50 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.0-devel (git-73dda85 2019-06-04 bionic-oibaf-ppa) OpenGL shading language version string: 4.50 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.2.0-devel (git-73dda85 2019-06-04 bionic-oibaf-ppa) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 lshw -C display: *-display description: VGA compatible controller product: Kaveri [Radeon R5 Graphics] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 1 bus info: pci@:00:01.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:43 memory:e000-efff memory:f000-f07f ioport:f000(size=256) memory:feb0-feb3 memory:c-d journalctl -p err -xb: Jun 04 15:51:49 alischa kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20181213/psargs-330) Jun 04 15:51:49 alischa kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.VGA.LCD._BCM, AE_NOT_FOUND (20181213/psparse-531) Jun 04 15:51:49 alischa kernel: ACPI Error: Evaluating _BCM failed (20181213/video-364) Note on oibaf-ppa: the same happens also with the standard repository packages and using this PPA was an attempt to fix the problem. I can reproduce this bug in Minecraft (see attached screenshot), Stellarium, and in Firefox with the page https://deck.gl/#/examples /core-layers/geojson-layer-paths I tried all combinations of graphics drivers. fbdev finally used software rendering (I think it was llvmpipe), which worked correct at the expense of a very low frame rate. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot showing this bug in Minecraft" https://bugs.launchpad.net/bugs/1831688/+attachment/5268862/+files/minecraft-gl-bug.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831688 Title: Flickering triangles in OpenGL apps on Radeon KAVERI Status in mesa package in Ubuntu: New Bug description: On (K)Ubuntu 18.04 I get strange triangles in almost all (I guess in all) apps using OpenGL. glxinfo | grep 'string\|version' prints the following: server glx vendor string: SGI server glx version string: 1.4 client glx vendor string: Mesa Project and SGI client glx version string: 1.4 GLX version: 1.4 Max core profile version: 4.5 Max compat profile version: 4.5 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: X.Org OpenGL renderer string: AMD KAVERI (DRM 2.50.0, 5.0.0-16-generic, LLVM 8.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 19.2.0-devel (git-73dda85 2019-06-04 bionic-oibaf-ppa) OpenGL core profile shading language version string: 4.50 OpenGL version string: 4.5 (Compatibility Profile) Mesa 19.2.0-devel (git-73dda85 2019-06-04 bionic-oibaf-ppa) OpenGL shading language version string: 4.50 OpenGL ES profile version string: OpenGL ES 3.2 Mesa 19.2.0-devel (git-73dda85 2019-06-04 bionic-oibaf-ppa) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 lshw -C display: *-display description: VGA compatible controller product: Kaveri [Radeon R5 Graphics] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 1 bus info: pci@:00:01.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:43 memory:e000-efff memory:f000-f07f ioport:f000(size=256) memory:feb0-feb3 memory:c-d journalctl -p err -xb: Jun 04 15:51:49 alischa kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.VGA.LCD._BCM.AFN7], AE_NOT_FOUND (20181213/psargs-330) Jun 04 15:51:49 alischa kernel: ACPI Error: Method parse/execution failed
[Touch-packages] [Bug 1746585] Re: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1746585 Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: Speakers and HDMI sound work fine, only headphones not working. I went through all of the steps on https://help.ubuntu.com/community/SoundTroubleshootingProcedure https://help.ubuntu.com/community/SoundTroubleshooting and https://wiki.ubuntu.com/DebuggingSoundProblems and submitted this report with ubuntu-bug -s audio Some possibly relevant information: This installation of Ubuntu was originally installed on a Dell Inspiron 15, but I cloned the partition onto an SSD that I installed on the Latitude 6420. It is the Latitude that is affected, the headphones work fine on the Inspiron. Let me know if any more information is required. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rviertel 2881 F...m pulseaudio /dev/snd/controlC0: rviertel 2881 F pulseaudio rviertel 4589 F alsamixer CurrentDesktop: Unity Date: Wed Jan 31 12:22:17 2018 InstallationDate: Installed on 2015-04-27 (1009 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rviertel 2881 F...m pulseaudio /dev/snd/controlC0: rviertel 2881 F pulseaudio rviertel 4589 F alsamixer /dev/snd/seq:timidity 1191 F timidity Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0K0DNP dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746585/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812143] Re: gsettings-desktop-schemas 3.31 breaks mutter 3.30
** Changed in: ukwm (Ubuntu) Assignee: (unassigned) => liuyi (liuyi-m) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1812143 Title: gsettings-desktop-schemas 3.31 breaks mutter 3.30 Status in gsettings-desktop-schemas package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in ukwm package in Ubuntu: Confirmed Bug description: We need to package mutter 3.31 and add a Breaks: mutter < 3.31 to gsettings-desktop-schemas. Running gsettings-desktop-schemas 3.31 with mutter 3.30 will result in gdm/gnome-shell being unable to start. Also, ukwm is a fork of mutter so the Kylin devs need to backport the relevant commits from mutter. The problematic gsettings commit was: https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/commit/c7eee129c I think the mutter commits can be found at https://gitlab.gnome.org/GNOME/mutter/merge_requests/133 We could easily add a dummy key with the old name but I'm thinking the way forward is just to package the newer mutter. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1812143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831599] Re: No display activity when coming out of powersave ("kernel BUG at mm/slub.c:296!")
It appears the 'amdgpu' kernel driver is crashing. That is part of the
kernel package 'linux'.
** Tags added: amdgpu
** Summary changed:
- No display activity when coming out of powersave ("kernel BUG at
mm/slub.c:296!")
+ [amdgpu] No display activity when coming out of powersave ("kernel BUG at
mm/slub.c:296!")
** Package changed: xorg (Ubuntu) => linux (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/1831599
Title:
[amdgpu] No display activity when coming out of powersave ("kernel BUG
at mm/slub.c:296!")
Status in linux package in Ubuntu:
New
Bug description:
Since a few weeks, my displays won't wake up from display powersave.
The machine stays responsive via SSH.
This first occurred on Ubuntu 18.04, and keeps happening on 18.10
(which I had updated to in the hopes of fixing the issue that way).
The only escape I've found from this state is via magic SysRq.
It can be triggered reliably by waiting for the screensaver to kick in
(e.g. overnight).
=
Note a kernel bug warning in CurrentDmesg.txt
=
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.3
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Tue Jun 4 13:40:47 2019
DistUpgraded: 2019-05-22 12:26:07,943 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: cosmic
DistroVariant: ubuntu
DkmsStatus:
spl, 0.7.9, 4.18.0-20-generic, x86_64: installed (WARNING! Diff between
built and installed module!) (WARNING! Diff between built and installed module!)
zfs, 0.7.9, 4.18.0-20-generic, x86_64: installed (WARNING! Diff between
built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!) (WARNING! Diff between built and installed
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff
between built and installed module!)
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX
470/480/570/570X/580/580X] [1002:67df] (rev ef) (prog-if 00 [VGA controller])
Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX
470/480/570/570X/580/580X] [1462:341b]
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic
root=ZFS=rpool/ROOT/ubuntu ro nouveau.modeset=0
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to cosmic on 2019-05-22 (13 days ago)
dmi.bios.date: 12/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1801
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A89GTD-PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
make.log:
DKMS make.log for zfs-0.7.9 for kernel 5.1.4-050104-generic (x86_64)
Do 23. Mai 18:51:15 CEST 2019
make: *** No targets specified and no makefile found. Stop.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831599/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help :
[Touch-packages] [Bug 1831655] Re: Xorg freeze
If the screen has frozen then the first thing to do is to check if something has crashed. So please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => xorg-server (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/1831655 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 14:29:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK106GL [Quadro K4000] [10de:097c] InstallationDate: Installed on 2019-05-25 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Precision T5610 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WN7Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/24/2014:svnDellInc.:pnPrecisionT5610:pvr01:rvnDellInc.:rn0WN7Y6:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T5610 dmi.product.sku: Precision T5610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1831655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396160] Re: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@75 → main → add_proc_info
** Summary changed: - /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info + recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@75 → main → add_proc_info -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1396160 Title: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@75 → main → add_proc_info Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Triaged Status in apport source package in Disco: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.14.7-0ubuntu10, the problem page at https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c contains more details. More Buckets: https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 Other reference: bug 1394919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1396160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831592] Re: ubuntu audio
Your attached AlsaInfo.txt seems to have the answer: Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - No So PulseAudio is not running. This may be due to your edits: modified.conffile..etc.pulse.default.pa: [modified] or it may be due to a crash. Please follow these instructions to check for a crash of pulseaudio: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment If you can't find any evidence of a crash then please try editing /etc/pulse/daemon.conf and add a line: realtime-scheduling = no Then reboot and tell us if the problem persists. ** Summary changed: - ubuntu audio + No sound. PulseAudio daemon is not running. -- 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/1831592 Title: No sound. PulseAudio daemon is not running. Status in pulseaudio package in Ubuntu: Incomplete Bug description: After installing cuda 10.1 updated in my ubuntu 18.04 version. I couldn't hear any sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 16:27:09 2019 InstallationDate: Installed on 2019-06-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z10PA-U8 Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3305:bd10/06/2016:svnASUSTeKCOMPUTERINC.:pnZ10PA-U8Series:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PA-U8Series:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: Z10PA-U8 Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-06-04T16:13:12.811810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1831592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound
Wait trying again, forgot something -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1831413 Title: alsa has to be reloaded afterlogin or else I don't get any sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound
I tried that just now, uninstalled timidity, did an apt update and dist- upgrade and even reboot after that. Still the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1831413 Title: alsa has to be reloaded afterlogin or else I don't get any sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound
OK yeah that's all it needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1831413 Title: alsa has to be reloaded afterlogin or else I don't get any sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831413] Re: alsa has to be reloaded afterlogin or else I don't get any sound
I tried that just now, uninstalled timidity, did an apt update and dist- upgrade and even reboot after that. Still the same. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1831413 Title: alsa has to be reloaded afterlogin or else I don't get any sound Status in alsa-driver package in Ubuntu: Incomplete Bug description: If I open Firefox or Chrome or any other app to play anything with sound, I get no sound, unless I run ~$ sudo alsa force-reload first. Before upgrading from Bionic to Disco I didn't have to do this. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-15.16-lowlatency 5.0.6 Uname: Linux 5.0.0-15-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timidity 2006 F timidity /dev/snd/pcmC0D0p: timidity 2006 F...m timidity /dev/snd/seq:timidity 2006 F timidity /dev/snd/timer: timidity 2006 f timidity Date: Sun Jun 2 20:12:03 2019 InstallationDate: Installed on 2016-12-19 (895 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B219P027 dmi.board.asset.tag: N/A dmi.board.name: ZBOX-CI320NANO series dmi.board.vendor: ZOTAC dmi.board.version: Rev.00 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB219P027:bd07/16/2015:svnMotherboardbyZOTAC:pnZBOX-CI320NANOseries:pvrRev.00:rvnZOTAC:rnZBOX-CI320NANOseries:rvrRev.00:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: N/A dmi.product.name: ZBOX-CI320NANO series dmi.product.sku: N/A dmi.product.version: Rev.00 dmi.sys.vendor: Motherboard by ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1831413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829450] Re: test_systemd_fsck_with_plymouth_failure passes but marked expected failure
This bug was fixed in the package systemd - 240-6ubuntu9 --- systemd (240-6ubuntu9) eoan; urgency=medium * Fix typpo in storage test. File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f28aa5fe4ab175b99b6ea702559c59ca473b4ca8 * Fix bashism File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be systemd (240-6ubuntu8) eoan; urgency=medium * Only restart resolved on changes in dhclient enter hook. This prevents spurious restarts of resolved on rebounds when the addresses did not change. (LP: #1805183) Author: Julian Andres Klode File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a * Wait for cryptsetup unit to start, before stopping. Patch from cascardo. Plus small refactor for readability. (LP: #1814373) File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b65aa350be7e61c65927fbc0921a750fcfaa51cd * Wait for systemctl is-system-running state. File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=776998f1f55c445b6e385cab69a4219c42d00838 systemd (240-6ubuntu7) eoan; urgency=medium * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE" This reverts commit 60407728a1a453104e3975ecfdf25a254dd7cc44. Files: - debian/patches/Add-check-to-switch-VTs-only-between-K_XLATE-or-K_UNICODE.patch - debian/patches/Move-verify_vc_kbmode-to-terminal-util.c-as-vt_verify_kbm.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=18029ab5ff436bfb3b401f24cd1e3a4cf2a1579c * Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints. Signed-off-by: Dimitri John Ledkov (LP: #1825378) Author: Dan Streetman Files: - debian/patches/network-wireguard-fixes-sending-wireguard-peer-setti.patch - debian/patches/network-wireguard-use-sd_netlink_message_append_sock.patch - debian/patches/sd-netlink-introduce-sd_netlink_message_append_socka.patch - debian/patches/test-network-add-more-checks-in-NetworkdNetDevTests..patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4046f515e40c4dc80d18d2303466737f1f451f11 * Remove expected failure from passing test. Signed-off-by: Dimitri John Ledkov (LP: #1829450) Author: Dan Streetman File: debian/tests/systemd-fsckd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c43b12037d08555dc1d26593307726d7c7992df0 * Fix false negative checking for running jobs after boot. Signed-off-by: Dimitri John Ledkov (LP: #1825997) Author: Dan Streetman File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=aeb01631efbaf3fe851dee15d496e0b66b5c347f * Cherrypick ask-password: prevent buffer overrow when reading from keyring. Signed-off-by: Dimitri John Ledkov (LP: #1814373) Author: Dan Streetman File: debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8 -- Dimitri John Ledkov Thu, 30 May 2019 21:45:50 +0100 ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => 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/1829450 Title: test_systemd_fsck_with_plymouth_failure passes but marked expected failure Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: Won't Fix Status in systemd source package in Eoan: Fix Released Bug description: [impact] this test case was marked as expected failure in the past to try to ignore failures, but it now passes and so causes autopkgtest failures. [test case] run autopkgtest and check for the 'test_systemd_fsck_with_plymouth_failure' test, e.g.: test_systemd_fsck_with_plymouth_failure (__main__.FsckdTest) Ensure that a failing plymouth doesn't prevent fsckd to reconnect/exit ... bash: line 1: 786 Killed /tmp/autopkgtest.84SCbj/build.1op/src/debian/tests/systemd-fsckd 2> >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stderr >&2) > >(tee -a /tmp/autopkgtest.84SCbj/systemd-fsckd-stdout) autopkgtest [16:47:57]: test process requested reboot with marker test_systemd_fsck_with_plymouth_failure:0
[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial
This bug was fixed in the package systemd - 240-6ubuntu9 --- systemd (240-6ubuntu9) eoan; urgency=medium * Fix typpo in storage test. File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f28aa5fe4ab175b99b6ea702559c59ca473b4ca8 * Fix bashism File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be systemd (240-6ubuntu8) eoan; urgency=medium * Only restart resolved on changes in dhclient enter hook. This prevents spurious restarts of resolved on rebounds when the addresses did not change. (LP: #1805183) Author: Julian Andres Klode File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a * Wait for cryptsetup unit to start, before stopping. Patch from cascardo. Plus small refactor for readability. (LP: #1814373) File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b65aa350be7e61c65927fbc0921a750fcfaa51cd * Wait for systemctl is-system-running state. File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=776998f1f55c445b6e385cab69a4219c42d00838 systemd (240-6ubuntu7) eoan; urgency=medium * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE" This reverts commit 60407728a1a453104e3975ecfdf25a254dd7cc44. Files: - debian/patches/Add-check-to-switch-VTs-only-between-K_XLATE-or-K_UNICODE.patch - debian/patches/Move-verify_vc_kbmode-to-terminal-util.c-as-vt_verify_kbm.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=18029ab5ff436bfb3b401f24cd1e3a4cf2a1579c * Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints. Signed-off-by: Dimitri John Ledkov (LP: #1825378) Author: Dan Streetman Files: - debian/patches/network-wireguard-fixes-sending-wireguard-peer-setti.patch - debian/patches/network-wireguard-use-sd_netlink_message_append_sock.patch - debian/patches/sd-netlink-introduce-sd_netlink_message_append_socka.patch - debian/patches/test-network-add-more-checks-in-NetworkdNetDevTests..patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4046f515e40c4dc80d18d2303466737f1f451f11 * Remove expected failure from passing test. Signed-off-by: Dimitri John Ledkov (LP: #1829450) Author: Dan Streetman File: debian/tests/systemd-fsckd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c43b12037d08555dc1d26593307726d7c7992df0 * Fix false negative checking for running jobs after boot. Signed-off-by: Dimitri John Ledkov (LP: #1825997) Author: Dan Streetman File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=aeb01631efbaf3fe851dee15d496e0b66b5c347f * Cherrypick ask-password: prevent buffer overrow when reading from keyring. Signed-off-by: Dimitri John Ledkov (LP: #1814373) Author: Dan Streetman File: debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8 -- Dimitri John Ledkov Thu, 30 May 2019 21:45:50 +0100 ** Changed in: systemd (Ubuntu) Status: Confirmed => 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/1805183 Title: systemd-resolved constantly restarts on Bionic upgraded from Xenial Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Confirmed Status in systemd source package in Cosmic: Confirmed Status in systemd source package in Disco: Confirmed Bug description: [Impact] Log noise due to needless restart of resolved on lease expiry, maybe loss of cached state? [Test case] (1) Append make_resolv_conf to the end of the file, so it gets executed (2) Execute the file with bash -x and different settings and ensure there are no restarts if the settings are the same, and that there are if settings change; for example: sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => no restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x debian/extra/dhclient-enter-resolved-hook => should restart sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash -x
[Touch-packages] [Bug 1825997] Re: boot-smoke fails due to running jobs
This bug was fixed in the package systemd - 240-6ubuntu9 --- systemd (240-6ubuntu9) eoan; urgency=medium * Fix typpo in storage test. File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f28aa5fe4ab175b99b6ea702559c59ca473b4ca8 * Fix bashism File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be systemd (240-6ubuntu8) eoan; urgency=medium * Only restart resolved on changes in dhclient enter hook. This prevents spurious restarts of resolved on rebounds when the addresses did not change. (LP: #1805183) Author: Julian Andres Klode File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a * Wait for cryptsetup unit to start, before stopping. Patch from cascardo. Plus small refactor for readability. (LP: #1814373) File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b65aa350be7e61c65927fbc0921a750fcfaa51cd * Wait for systemctl is-system-running state. File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=776998f1f55c445b6e385cab69a4219c42d00838 systemd (240-6ubuntu7) eoan; urgency=medium * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE" This reverts commit 60407728a1a453104e3975ecfdf25a254dd7cc44. Files: - debian/patches/Add-check-to-switch-VTs-only-between-K_XLATE-or-K_UNICODE.patch - debian/patches/Move-verify_vc_kbmode-to-terminal-util.c-as-vt_verify_kbm.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=18029ab5ff436bfb3b401f24cd1e3a4cf2a1579c * Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints. Signed-off-by: Dimitri John Ledkov (LP: #1825378) Author: Dan Streetman Files: - debian/patches/network-wireguard-fixes-sending-wireguard-peer-setti.patch - debian/patches/network-wireguard-use-sd_netlink_message_append_sock.patch - debian/patches/sd-netlink-introduce-sd_netlink_message_append_socka.patch - debian/patches/test-network-add-more-checks-in-NetworkdNetDevTests..patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4046f515e40c4dc80d18d2303466737f1f451f11 * Remove expected failure from passing test. Signed-off-by: Dimitri John Ledkov (LP: #1829450) Author: Dan Streetman File: debian/tests/systemd-fsckd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c43b12037d08555dc1d26593307726d7c7992df0 * Fix false negative checking for running jobs after boot. Signed-off-by: Dimitri John Ledkov (LP: #1825997) Author: Dan Streetman File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=aeb01631efbaf3fe851dee15d496e0b66b5c347f * Cherrypick ask-password: prevent buffer overrow when reading from keyring. Signed-off-by: Dimitri John Ledkov (LP: #1814373) Author: Dan Streetman File: debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8 -- Dimitri John Ledkov Thu, 30 May 2019 21:45:50 +0100 ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => 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/1825997 Title: boot-smoke fails due to running jobs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] boot-smoke test reboots 5 times and verifies systemd is fully started up after each boot, including checking if there are any running jobs (with list-jobs). However, this test makes the assumption that no further jobs will be started after systemd reaches 'running' (or 'degraded') state, which is a false assumption. [test case] see various boot-smoke failures in autopkgtest.ubuntu.com [regression potential] possible false-positive or false-negative autopkgtest results. [other info] Note: This patch is not required for debian, because debian's boot- smoke does not include the wait for systemctl is-system-running. The problem appears to be that systemd reaches 'running' (or 'degraded') state, and then other systemd services
[Touch-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
This bug was fixed in the package systemd - 240-6ubuntu9 --- systemd (240-6ubuntu9) eoan; urgency=medium * Fix typpo in storage test. File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f28aa5fe4ab175b99b6ea702559c59ca473b4ca8 * Fix bashism File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be systemd (240-6ubuntu8) eoan; urgency=medium * Only restart resolved on changes in dhclient enter hook. This prevents spurious restarts of resolved on rebounds when the addresses did not change. (LP: #1805183) Author: Julian Andres Klode File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a * Wait for cryptsetup unit to start, before stopping. Patch from cascardo. Plus small refactor for readability. (LP: #1814373) File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b65aa350be7e61c65927fbc0921a750fcfaa51cd * Wait for systemctl is-system-running state. File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=776998f1f55c445b6e385cab69a4219c42d00838 systemd (240-6ubuntu7) eoan; urgency=medium * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE" This reverts commit 60407728a1a453104e3975ecfdf25a254dd7cc44. Files: - debian/patches/Add-check-to-switch-VTs-only-between-K_XLATE-or-K_UNICODE.patch - debian/patches/Move-verify_vc_kbmode-to-terminal-util.c-as-vt_verify_kbm.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=18029ab5ff436bfb3b401f24cd1e3a4cf2a1579c * Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints. Signed-off-by: Dimitri John Ledkov (LP: #1825378) Author: Dan Streetman Files: - debian/patches/network-wireguard-fixes-sending-wireguard-peer-setti.patch - debian/patches/network-wireguard-use-sd_netlink_message_append_sock.patch - debian/patches/sd-netlink-introduce-sd_netlink_message_append_socka.patch - debian/patches/test-network-add-more-checks-in-NetworkdNetDevTests..patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4046f515e40c4dc80d18d2303466737f1f451f11 * Remove expected failure from passing test. Signed-off-by: Dimitri John Ledkov (LP: #1829450) Author: Dan Streetman File: debian/tests/systemd-fsckd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c43b12037d08555dc1d26593307726d7c7992df0 * Fix false negative checking for running jobs after boot. Signed-off-by: Dimitri John Ledkov (LP: #1825997) Author: Dan Streetman File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=aeb01631efbaf3fe851dee15d496e0b66b5c347f * Cherrypick ask-password: prevent buffer overrow when reading from keyring. Signed-off-by: Dimitri John Ledkov (LP: #1814373) Author: Dan Streetman File: debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8 -- Dimitri John Ledkov Thu, 30 May 2019 21:45:50 +0100 ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Committed Status in linux source package in Disco: New Status in systemd source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Fix Released Status in systemd package in Debian: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload:
[Touch-packages] [Bug 1825378] Re: systemd-networkd doesn't set wireguard peer endpoint
This bug was fixed in the package systemd - 240-6ubuntu9 --- systemd (240-6ubuntu9) eoan; urgency=medium * Fix typpo in storage test. File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f28aa5fe4ab175b99b6ea702559c59ca473b4ca8 * Fix bashism File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be systemd (240-6ubuntu8) eoan; urgency=medium * Only restart resolved on changes in dhclient enter hook. This prevents spurious restarts of resolved on rebounds when the addresses did not change. (LP: #1805183) Author: Julian Andres Klode File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a * Wait for cryptsetup unit to start, before stopping. Patch from cascardo. Plus small refactor for readability. (LP: #1814373) File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b65aa350be7e61c65927fbc0921a750fcfaa51cd * Wait for systemctl is-system-running state. File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=776998f1f55c445b6e385cab69a4219c42d00838 systemd (240-6ubuntu7) eoan; urgency=medium * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE" This reverts commit 60407728a1a453104e3975ecfdf25a254dd7cc44. Files: - debian/patches/Add-check-to-switch-VTs-only-between-K_XLATE-or-K_UNICODE.patch - debian/patches/Move-verify_vc_kbmode-to-terminal-util.c-as-vt_verify_kbm.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=18029ab5ff436bfb3b401f24cd1e3a4cf2a1579c * Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints. Signed-off-by: Dimitri John Ledkov (LP: #1825378) Author: Dan Streetman Files: - debian/patches/network-wireguard-fixes-sending-wireguard-peer-setti.patch - debian/patches/network-wireguard-use-sd_netlink_message_append_sock.patch - debian/patches/sd-netlink-introduce-sd_netlink_message_append_socka.patch - debian/patches/test-network-add-more-checks-in-NetworkdNetDevTests..patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4046f515e40c4dc80d18d2303466737f1f451f11 * Remove expected failure from passing test. Signed-off-by: Dimitri John Ledkov (LP: #1829450) Author: Dan Streetman File: debian/tests/systemd-fsckd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c43b12037d08555dc1d26593307726d7c7992df0 * Fix false negative checking for running jobs after boot. Signed-off-by: Dimitri John Ledkov (LP: #1825997) Author: Dan Streetman File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=aeb01631efbaf3fe851dee15d496e0b66b5c347f * Cherrypick ask-password: prevent buffer overrow when reading from keyring. Signed-off-by: Dimitri John Ledkov (LP: #1814373) Author: Dan Streetman File: debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8 -- Dimitri John Ledkov Thu, 30 May 2019 21:45:50 +0100 ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => 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/1825378 Title: systemd-networkd doesn't set wireguard peer endpoint Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Cosmic: Invalid Status in systemd source package in Disco: Fix Committed Status in systemd source package in Eoan: Fix Released Bug description: [impact] systemd does not set endpoints for wireguard interfaces correctly. This makes wireguard unusable. [test case] install a disco or eoan system and set up a wireguard interface: $ sudo add-apt-repository ppa:wireguard/wireguard $ sudo apt install wireguard ...(this does a lot of stuff)... create a file as below; There is no need to setup remote server to reproduce this issue, but PublicKey/PrivateKey should be valid one (used instructions from https://www.linode.com/docs/networking/vpn /set-up-wireguard-vpn-on-ubuntu/#configure-wireguard-server): $ cat /etc/systemd/network/wg0.netdev [NetDev] Name=wg0 Kind=wireguard [WireGuard] PrivateKey=uMuCbguKYdKanRYMbDSriIdgxGxJR57Us1zEy8wRc1M= ListenPort=51820 [WireGuardPeer] PublicKey=ZRyl+kvb6o2/6Da5YLum6GnSrzDj3J002+2kmK5CnS4= AllowedIPs=10.0.0.0/8
[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen
This bug was fixed in the package systemd - 240-6ubuntu9 --- systemd (240-6ubuntu9) eoan; urgency=medium * Fix typpo in storage test. File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f28aa5fe4ab175b99b6ea702559c59ca473b4ca8 * Fix bashism File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=0725c1169ddde4f41cacba7af3e546704e2206be systemd (240-6ubuntu8) eoan; urgency=medium * Only restart resolved on changes in dhclient enter hook. This prevents spurious restarts of resolved on rebounds when the addresses did not change. (LP: #1805183) Author: Julian Andres Klode File: debian/extra/dhclient-enter-resolved-hook https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=258893bae8cbb12670e4807636fe8f7e9fb5407a * Wait for cryptsetup unit to start, before stopping. Patch from cascardo. Plus small refactor for readability. (LP: #1814373) File: debian/tests/storage https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b65aa350be7e61c65927fbc0921a750fcfaa51cd * Wait for systemctl is-system-running state. File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=776998f1f55c445b6e385cab69a4219c42d00838 systemd (240-6ubuntu7) eoan; urgency=medium * Revert "Add check to switch VTs only between K_XLATE or K_UNICODE" This reverts commit 60407728a1a453104e3975ecfdf25a254dd7cc44. Files: - debian/patches/Add-check-to-switch-VTs-only-between-K_XLATE-or-K_UNICODE.patch - debian/patches/Move-verify_vc_kbmode-to-terminal-util.c-as-vt_verify_kbm.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=18029ab5ff436bfb3b401f24cd1e3a4cf2a1579c * Cherrypick missing systemd-stable patches to unbreak wireguard peer endpoints. Signed-off-by: Dimitri John Ledkov (LP: #1825378) Author: Dan Streetman Files: - debian/patches/network-wireguard-fixes-sending-wireguard-peer-setti.patch - debian/patches/network-wireguard-use-sd_netlink_message_append_sock.patch - debian/patches/sd-netlink-introduce-sd_netlink_message_append_socka.patch - debian/patches/test-network-add-more-checks-in-NetworkdNetDevTests..patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4046f515e40c4dc80d18d2303466737f1f451f11 * Remove expected failure from passing test. Signed-off-by: Dimitri John Ledkov (LP: #1829450) Author: Dan Streetman File: debian/tests/systemd-fsckd https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c43b12037d08555dc1d26593307726d7c7992df0 * Fix false negative checking for running jobs after boot. Signed-off-by: Dimitri John Ledkov (LP: #1825997) Author: Dan Streetman File: debian/tests/boot-smoke https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=aeb01631efbaf3fe851dee15d496e0b66b5c347f * Cherrypick ask-password: prevent buffer overrow when reading from keyring. Signed-off-by: Dimitri John Ledkov (LP: #1814373) Author: Dan Streetman File: debian/patches/ask-password-prevent-buffer-overrow-when-reading-fro.patch https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6d6e9cbd4fc6e018031a4762e88f2c3aa19e24e8 -- Dimitri John Ledkov Thu, 30 May 2019 21:45:50 +0100 ** 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/1803993 Title: Password appears on the VT1 screen Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Bug description: [Impact] * The keyboard on the graphical login screen started on VT1 may stop working and or keypresses including passwords are leaked to the terminal console running 'behind' the graphical login screen or environment. [Test Case] * Reboot after installing the fixed systemd package. * Install sysdig * Start sysdig on a remote connection or on a terminal console: $ sudo sysdig evt.type=ioctl | grep request=4B4 * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in
[Touch-packages] [Bug 1829077] Re: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4
** Summary changed: - disco 19.04 doesn't shutdown + disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4 -- 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/1829077 Title: disco 19.04 doesn't shutdown on an Asrock 970 Extreme 4 Status in systemd package in Ubuntu: Confirmed Bug description: I have a fresh install of Ubuntu 19.04 GNOME 64 bits. When I choose "Power Off", it closes the session screen but then it displays the red dots who scroll under Ubuntu logo and it never stop completely. I can listen the hard disk containing my home directory which stops (the system is on a SSD). Each time, I have to switch off the computer. I can start it again without any problem. The command "sudo shutdown now" give the same result. This computer had not this problem with the previous version of Ubuntu. Proc : AMD Fx 8320 Motherboard : Asrock 970 Extreme 4 graphic card : Radeon 6850 Ram : 8Go Ubuntu 19.04 is the only OS on the SSD system drive /home is on a second hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1829077/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
** Changed in: qtbase-opensource-src (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src package in Debian: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
As the error is happening in ubuntu core 16 on i386, I couldn't install the apport snap due to is is not available for this arch (just for amd64). So I installed classic and generated the report from there, but I am not sure this information is the one you want. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME)
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
** No longer affects: qttools-opensource-src (Ubuntu) ** No longer affects: tightvnc (Ubuntu) ** Also affects: qtbase-opensource-src (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src package in Debian: Unknown Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831490] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1831490/+attachment/5268850/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM)
[Touch-packages] [Bug 1831490] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1831490/+attachment/5268849/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM)
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
Hello bugproxy, or anyone else affected,
Accepted lvm2 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu3.18.10.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, without details of
your testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: lvm2 (Ubuntu Cosmic)
Status: New => Fix Committed
** Tags added: verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
In Progress
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
New
Status in lvm2 source package in Bionic:
New
Status in lvm2 source package in Cosmic:
Fix Committed
Status in lvm2 source package in Disco:
Fix Committed
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831490] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1831490/+attachment/5268848/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1831490 Title: kernel is out of memory and killed during a kernel sys_write operation Status in apparmor package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM)
[Touch-packages] [Bug 1831490] Re: kernel is out of memory and killed during a kernel sys_write operation
apport information ** Tags added: apport-collected uec-images ** Description changed: This error is being reproduced on i386 arch when using the pc-kernel snap from beta or candidate. > sudo snap install test-snapd-tools > dmesg [15131.806107] audit: type=1400 audit(1559585825.240:93): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="snap-update-ns.test-snapd-tools" pid=18240 comm="apparmor_parser" [15131.871610] vmap allocation for size 73728 failed: use vmalloc= to increase size. [15131.871614] vmalloc: allocation failure: 68481 bytes [15131.871616] apparmor_parser: page allocation failure: order:0, mode:0x24000c2 [15131.871619] CPU: 0 PID: 18242 Comm: apparmor_parser Not tainted 4.4.0-150-generic #176-Ubuntu [15131.871620] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 [15131.871622] c1b15967 5ed07e43 0286 cfee9e00 c13c12ef c1a1ce6c 0001 cfee9e30 [15131.871625] c11821b6 c1a1b220 f40ba700 024000c2 cfee9e44 c1a1ce6c cfee9e18 [15131.871629] 5ed07e43 00010b81 cfee9e60 c11ba86f 024000c2 c1a1ce6c [15131.871632] Call Trace: [15131.871637] [] dump_stack+0x58/0x79 [15131.871640] [] warn_alloc_failed+0xd6/0x110 [15131.871643] [] __vmalloc_node_range+0x1ef/0x210 [15131.871645] [] __vmalloc_node+0x66/0x70 [15131.871648] [] ? __aa_kvmalloc+0x28/0x60 [15131.871650] [] vmalloc+0x38/0x40 [15131.871652] [] ? __aa_kvmalloc+0x28/0x60 [15131.871654] [] __aa_kvmalloc+0x28/0x60 [15131.871656] [] aa_simple_write_to_buffer+0x34/0x90 [15131.871658] [] policy_update+0x73/0x230 [15131.871660] [] ? security_file_permission+0x3e/0xd0 [15131.871662] [] profile_replace+0x98/0xe0 [15131.871664] [] ? policy_update+0x230/0x230 [15131.871666] [] __vfs_write+0x22/0x50 [15131.871668] [] vfs_write+0x8c/0x1b0 [15131.871669] [] SyS_write+0x51/0xb0 [15131.871672] [] do_fast_syscall_32+0x9f/0x190 [15131.871675] [] sysenter_past_esp+0x3d/0x61 [15131.871676] Mem-Info: [15131.871679] active_anon:16802 inactive_anon:2068 isolated_anon:0 active_file:84472 inactive_file:25195 isolated_file:0 unevictable:0 dirty:34 writeback:0 unstable:0 slab_reclaimable:7222 slab_unreclaimable:14030 mapped:8431 shmem:5785 pagetables:204 bounce:0 free:289381 free_pcp:659 free_cma:0 [15131.871685] DMA free:8848kB min:788kB low:984kB high:1180kB active_anon:636kB inactive_anon:0kB active_file:2720kB inactive_file:800kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15992kB managed:15916kB mlocked:0kB dirty:0kB writeback:0kB mapped:472kB shmem:308kB slab_reclaimable:484kB slab_unreclaimable:424kB kernel_stack:8kB pagetables:4kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871686] lowmem_reserve[]: 0 834 1942 1942 [15131.871692] Normal free:364440kB min:42432kB low:53040kB high:63648kB active_anon:30164kB inactive_anon:2776kB active_file:158404kB inactive_file:32020kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:897016kB managed:862444kB mlocked:0kB dirty:116kB writeback:0kB mapped:11176kB shmem:6332kB slab_reclaimable:28404kB slab_unreclaimable:55696kB kernel_stack:1040kB pagetables:348kB unstable:0kB bounce:0kB free_pcp:1336kB local_pcp:676kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871693] lowmem_reserve[]: 0 0 8863 8863 [15131.871698] HighMem free:784236kB min:512kB low:14600kB high:28688kB active_anon:36408kB inactive_anon:5496kB active_file:176764kB inactive_file:67960kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:1134472kB managed:1134472kB mlocked:0kB dirty:20kB writeback:0kB mapped:22076kB shmem:16500kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:464kB unstable:0kB bounce:0kB free_pcp:1300kB local_pcp:680kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [15131.871699] lowmem_reserve[]: 0 0 0 0 [15131.871701] DMA: 12*4kB (UME) 10*8kB (UME) 7*16kB (ME) 5*32kB (UM) 2*64kB (U) 3*128kB (UM) 3*256kB (UM) 4*512kB (UME) 3*1024kB (ME) 1*2048kB (M) 0*4096kB = 8848kB [15131.871711] Normal: 87*4kB (UME) 106*8kB (UME) 168*16kB (UME) 195*32kB (UME) 135*64kB (UME) 161*128kB (ME) 120*256kB (ME) 61*512kB (UME) 25*1024kB (ME) 6*2048kB (M) 55*4096kB (M) = 364492kB [15131.871720] HighMem: 131*4kB (UM) 835*8kB (UM) 302*16kB (UM) 119*32kB (UM) 95*64kB (UM) 50*128kB (UM) 67*256kB (UM) 55*512kB (UM) 52*1024kB (M) 23*2048kB (UM) 149*4096kB (M) = 784292kB [15131.871729] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB [15131.871730] 115450 total pagecache pages [15131.871731] 0 pages in swap cache [15131.871733] Swap cache stats: add 0, delete 0, find 0/0 [15131.871734] Free swap = 0kB
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
You are right, bug is fixed in Ubuntu 18.10 (cosmic) and 19.04 (disco). I can type text in Kate even without XKB. ** Tags added: cosmic ** Tags removed: cosmic ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: New Status in qttools-opensource-src package in Ubuntu: New Status in tightvnc package in Ubuntu: New Status in qtbase-opensource-src package in Debian: Unknown Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
Hello bugproxy, or anyone else affected,
Accepted lvm2 into disco-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lvm2/2.02.176-4.1ubuntu4.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: lvm2 (Ubuntu Disco)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
In Progress
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
New
Status in lvm2 source package in Bionic:
New
Status in lvm2 source package in Cosmic:
New
Status in lvm2 source package in Disco:
Fix Committed
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831498] Proposed package upload rejected
An upload of mesa to disco-proposed has been rejected from the upload queue for the following reason: "Comet Lake support was dropped without explanation.". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1831498 Title: radeonsi: GTK elements become invisible in some applications (GIMP, LibreOffice) Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: New Status in mesa source package in Disco: New Bug description: [impact] imported from https://bugs.freedesktop.org/show_bug.cgi?id=110355 : "I am currently experiencing some issues with GTK elements (GtkMenuItem, GtkMenu) becoming invisible with GIMP and LibreOffice. I am currently using radeonsi+glamor and I'm on Arch Linux (x86_64). My hardware is a Ryzen 5 2400G APU with vega graphics." [test case] test that GIMP/Libreoffice work fine on AMD Vega/Raven [regression potential] the fix/workaround is already in mesa 19.0.4, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1831498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831655] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1831655 Title: Xorg freeze Status in xorg package in Ubuntu: Incomplete Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 14:29:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK106GL [Quadro K4000] [10de:097c] InstallationDate: Installed on 2019-05-25 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Precision T5610 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WN7Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/24/2014:svnDellInc.:pnPrecisionT5610:pvr01:rvnDellInc.:rn0WN7Y6:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T5610 dmi.product.sku: Precision T5610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1831655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650740] Re: dhclient depends on fstab 16.04LTS
*** This bug is a duplicate of bug 1632405 *** https://bugs.launchpad.net/bugs/1632405 ** This bug has been marked a duplicate of bug 1632405 virt-customize enters infinite loop: dhclient-script: cannot open /etc/fstab -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1650740 Title: dhclient depends on fstab 16.04LTS Status in isc-dhcp package in Ubuntu: Confirmed Bug description: As noted here: https://bugs.launchpad.net/ubuntu/+source/libguestfs/+bug/1632405 dhclient-script attempts to read fstab and if not available is unable to continue; while a workaround has been provided in the upstream for the dependent (and fairly critical) package, which will hopefully make it into the 16.04 repos soon, the bug does seem to be in dhclient- script, and presumably is easily fixable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1650740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1089013] Re: clvm startup script requires cman
** Tags removed: sts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1089013 Title: clvm startup script requires cman Status in lvm2 package in Ubuntu: Fix Released Status in lvm2 source package in Precise: Triaged Status in lvm2 source package in Trusty: Won't Fix Status in lvm2 source package in Wily: Won't Fix Status in lvm2 source package in Xenial: Fix Released Bug description: while clvm in precise can support corosync, init script won't start because issues a cman status command ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: clvm 2.02.66-4ubuntu7.1 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Tue Dec 11 18:09:36 2012 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) ProcEnviron: TERM=screen LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.clvm: [modified] mtime.conffile..etc.default.clvm: 2012-12-11T16:45:40.149014 [Impact] * clvm daemon cannot start using provided init scripts [Test Case] * Install clvm package * Configure corosync * service clvm start - Fails to start due to cman dependency [Regression Potential] * None, already broken, though there is risk of other bugs being uncovered since this hasn't worked in quite awhile. [Other Info] * This is a change to the debian provided init script for clvm. Upstream debian still has the redhat-cluster package which contains the cman tool, as such this change is applicable to Ubuntu only since the redhat clustering suite is not available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1089013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831655] [NEW] Xorg freeze
Public bug reported: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 14:29:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK106GL [Quadro K4000] [10de:097c] InstallationDate: Installed on 2019-05-25 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Precision T5610 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WN7Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/24/2014:svnDellInc.:pnPrecisionT5610:pvr01:rvnDellInc.:rn0WN7Y6:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T5610 dmi.product.sku: Precision T5610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1831655 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: NA ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 14:29:47 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GK106GL [Quadro K4000] [10de:11fa] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GK106GL [Quadro K4000] [10de:097c] InstallationDate: Installed on 2019-05-25 (10 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. Precision T5610 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0WN7Y6 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/24/2014:svnDellInc.:pnPrecisionT5610:pvr01:rvnDellInc.:rn0WN7Y6:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T5610 dmi.product.sku: Precision T5610 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1831655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
ok. bug may be closed, i locate problem. dhcp don't get lease on discovery if where is a valid lease. After release current lease systemd dhcp discover request was answered. -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
here is two tcpdumps of dhcp ports root@gwd:~# tcpdump -vv -i enp3s0 -n port 67 and port 68 tcpdump: listening on enp3s0, link-type EN10MB (Ethernet), capture size 262144 bytes SYSTEMD [NOT WORKED] 19:58:01.261864 IP (tos 0xc0, ttl 64, id 0, offset 0, flags [none], proto UDP (17), length 300) 0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from c8:d3:a3:50:02:33, length 272, xid 0x495060a3, secs 1539, Flags [none] (0x) Client-Ethernet-Address c8:d3:a3:50:02:33 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Discover Client-ID Option 61, length 7: ether c8:d3:a3:50:02:33 Parameter-Request Option 55, length 8: Subnet-Mask, Default-Gateway, Hostname, Domain-Name Domain-Name-Server, MTU, Static-Route, Classless-Static-Route MSZ Option 57, length 2: 576 Hostname Option 12, length 3: "gwd" DHCLIENT [WORKED] 20:02:33.187353 IP (tos 0x10, ttl 128, id 0, offset 0, flags [none], proto UDP (17), length 328) 0.0.0.0.68 > 255.255.255.255.67: [udp sum ok] BOOTP/DHCP, Request from c8:d3:a3:50:02:33, length 300, xid 0x5986fc7c, Flags [none] (0x) Client-Ethernet-Address c8:d3:a3:50:02:33 Vendor-rfc1048 Extensions Magic Cookie 0x63825363 DHCP-Message Option 53, length 1: Request Requested-IP Option 50, length 4: 213.141.128.50 Hostname Option 12, length 3: "gwd" Parameter-Request Option 55, length 13: Subnet-Mask, BR, Time-Zone, Default-Gateway Domain-Name, Domain-Name-Server, Option 119, Hostname Netbios-Name-Server, Netbios-Scope, MTU, Classless-Static-Route NTP -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
The Debian bug is marked as fixed in Qt 5.11. Can you please check if this bug is present in Disco (which has 5.12)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: New Status in qttools-opensource-src package in Ubuntu: New Status in tightvnc package in Ubuntu: New Status in qtbase-opensource-src package in Debian: Unknown Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
netif.tar http://paste.ubuntu.com/p/DvPcmNs6Jb/ -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
here is debug log http://paste.ubuntu.com/p/mTxRb5s4Qc/ -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831644] [NEW] Automatically connects to wifi though already connected to wired; plus even if previously explicitly disconnected from wifi
Public bug reported: I have a wifi network to which sometimes I connected and stored the password. I am connected to the wired ethernet network. Expected: shouldn't ever connect to any available wifi while I'm connected to wired. Observed: sometimes, randomly, it automatically connects to the wifi despite the fact I'm already connected to wired. As a result, I am then connected to both. Also, it does so at a completely random time: I've been here for hours, the wifi has been available for hours, I've been connected to the wired network all the time, nothing special has happened, I haven't restarted the commputer or logged out and in or anyhthing (I don't know if the wifi has become unavailable for a very short interval of time and then available again, it's unlikely and it wouldn't in any way justify the behavior), yet for some reason, NOW my computer decides to connect to the wifi (which it shouldn't anyway for any reason). ADDITIONALLY: After that, I explicitly manually disconnect from that wifi network. When I do this, I expect that the setting to automatically reconnect to this wifi network when available is turned off (otherwise, every time you disconnect from a network, it would reconnect immediately). I'm pretty sure this used to work. But then, the same as described above happened AGAIN: that is, I was connected to the wired network (had been for hours), and suddenly it automatically connected to the same wifi network as above (again, been available forever), which it shouldn't even if it was set to automatically connect whern available (given it's connected to wired), but it isn't even more nonsensical given that I had previously manually disconnected from it so it should not be set to reconnect automatically. This has started happening recently. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 4 18:35:11 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-11 (2061 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.37 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-20T16:52:59.722501 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/1 Wired connection 1 662a0c09-71a8-4101-9236-ebcc1696d69a /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1831644 Title: Automatically connects to wifi though already connected to wired; plus even if previously explicitly disconnected from wifi Status in network-manager package in Ubuntu: New Bug description: I have a wifi network to which sometimes I connected and stored the password. I am connected to the wired ethernet network. Expected: shouldn't ever connect to any available wifi while I'm connected to wired. Observed: sometimes, randomly, it automatically connects to the wifi despite the fact I'm already connected to wired. As a result, I am then connected to both. Also, it does so at a completely random time: I've been here for hours, the wifi has been available for hours, I've been connected to the wired network all the time, nothing special has happened, I haven't restarted the commputer or logged out and in or anyhthing (I don't know if the wifi has become unavailable for a very
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Eoan: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396160] Re: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.14.7-0ubuntu10, the problem page at https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c contains more details. More Buckets: https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 - + https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 Other reference: bug 1394919 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1396160 Title: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info Status in apport package in Ubuntu: Fix Released Status in apport source package in Bionic: Triaged Status in apport source package in Disco: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with version 2.14.7-0ubuntu10, the problem page at https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c contains more details. More Buckets: https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 Other reference: bug 1394919 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1396160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831523] Re: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info
*** This bug is a duplicate of bug 1396160 *** https://bugs.launchpad.net/bugs/1396160 ** This bug has been marked a duplicate of bug 1396160 /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1831523 Title: recoverable_problem (PermissionError) /usr/share/apport/recoverable_problem@78 → main → add_proc_info Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.10-0ubuntu23, the problem page at https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1831523/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831592] Re: ubuntu audio
Thank you for your bug report, could you add your "journalctl -b 0" log to the bug? ** 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/1831592 Title: ubuntu audio Status in pulseaudio package in Ubuntu: Incomplete Bug description: After installing cuda 10.1 updated in my ubuntu 18.04 version. I couldn't hear any sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 16:27:09 2019 InstallationDate: Installed on 2019-06-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z10PA-U8 Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3305:bd10/06/2016:svnASUSTeKCOMPUTERINC.:pnZ10PA-U8Series:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PA-U8Series:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: Z10PA-U8 Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-06-04T16:13:12.811810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1831592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
Seems to be related to https://bugreports.qt.io/browse/QTBUG-44938 ** Bug watch added: Debian Bug tracker #814959 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814959 ** Also affects: qtbase-opensource-src (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814959 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: New Status in qttools-opensource-src package in Ubuntu: New Status in tightvnc package in Ubuntu: New Status in qtbase-opensource-src package in Debian: Unknown Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
here is lease gained from dhclient
dhcp-lease-time present
lease {
interface "enp3s0.2";
fixed-address 213.141.128.50;
option subnet-mask 255.255.224.0;
option routers 213.141.159.252;
option dhcp-lease-time 7200;
option dhcp-message-type 5;
option domain-name-servers 212.1.224.6,212.1.244.6;
option dhcp-server-identifier 212.1.254.199;
option vendor-encapsulated-options "http://acs.netbynet.ru;;
renew 2 2019/06/04 16:09:10;
rebind 2 2019/06/04 17:06:44;
expire 2 2019/06/04 17:21:44;
}
--
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/1831470
Title:
systemd dhcp don't work on vlan
Status in systemd package in Ubuntu:
New
Bug description:
root@gwd:~# uname -a
Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64
x86_64 x86_64 GNU/Linux
root@gwd:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.2 LTS
Release:18.04
Codename: bionic
root@gwd:~# cat /etc/systemd/network/enp3s0.network
[Match]
Name=enp3s0
[Link]
MACAddress=C8:D3:A3:50:02:33
[Network]
VLAN=enp3s0.2
root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev
[NetDev]
Name=enp3s0.2
Kind=vlan
[VLAN]
Id=2
root@gwd:~# cat /etc/systemd/network/enp3s0.2.network
[Match]
Name=enp3s0.2
[Network]
DHCP=ipv4
[DHCP]
UseRoutes=true
-
No ip on enp3s0.2 after boot!
dhclient enp3s0.2 works fine, i create systemd service for it as temporary
workaround
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Despite some build failures for i386 and s390 which I believe are not related to the scope of the change I have successfully verified it for amd64. apt-cache policy cups-daemon cups: Installed: 2.1.3-4ubuntu0.9 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:13:19:56 +] [Job 1] Job completed. D [04/Jun/2019:13:20:27 +] [Job 1] Removing from history. PreserveJobHistory No: I [04/Jun/2019:13:22:32 +] [Job 2] Job completed. D [04/Jun/2019:13:22:32 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:13:23:41 +] [Job 3] Job completed. -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831258] Re: journalctl --list-boots does not recognize boots in a container
Filed issue with lxcfs at https://github.com/lxc/lxcfs/issues/285 ** Bug watch added: LXCFS bug tracker #285 https://github.com/lxc/lxcfs/issues/285 -- 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/1831258 Title: journalctl --list-boots does not recognize boots in a container Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in lxd source package in Bionic: New Status in systemd source package in Bionic: Invalid Status in lxd source package in Eoan: New Status in systemd source package in Eoan: Invalid Bug description: $ lxc launch ubuntu-daily:eoan devel1 $ sleep 10 # wait for boot $ lxc exec devel1 /bin/bash root@devel1:~# cat /proc/uptime 183.00 173.00 root@devel1:~# cat /etc/cloud/build.info build_name: server serial: 20190531 root@devel1:~# lsb_release -sc eoan root@devel1:~# journalctl --no-pager --list-boots 0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 2019-05-31 15:06:10 UTC root@devel1:~# reboot root@devel1:~# $ lxc exec devel1 /bin/bash ## verify the reboot happened root@devel1:~# cat /proc/uptime 12.00 6.00 ## but journalctl only shows the same boot it did before. root@devel1:~# journalctl --no-pager --list-boots 0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 2019-05-31 15:09:10 UTC ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Fri May 31 15:06:24 2019 MachineType: LENOVO 20KGS3Y900 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=25df9069-80c7-46f4-a47c-305613c2cb6b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS3Y900 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KGS3Y900:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS3Y900:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS3Y900 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1831258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Changed in: cups (Ubuntu Disco) Assignee: Dariusz Gadomski (dgadomski) => (unassigned) ** Description changed: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. - 4. Set PreserveJobHistory to Yes. Repeat 2-3. - 5. Set PreserveJobHistory to No. Repeat 2-3. + 4. Set PreserveJobHistory to No. Repeat 2-3. + 5. Set PreserveJobHistory to Yes. Repeat 2-3. + Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. + No: Job is removed right after processing. Yes: Job is never removed. - No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. + No: Job is removed right after processing. Yes: Job is never removed. - No: Job is removed right after processing. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to No. Repeat 2-3. 5. Set PreserveJobHistory to Yes. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. No: Job is removed right after processing. Yes: Job is never removed. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. No: Job is removed right after processing. Yes: Job is never removed. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead
[Touch-packages] [Bug 1831258] Re: journalctl --list-boots does not recognize boots in a container
Several people tried to namespace this but this is really tied to a physical machine so it's kinda tricky to fake. -- 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/1831258 Title: journalctl --list-boots does not recognize boots in a container Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in lxd source package in Bionic: New Status in systemd source package in Bionic: Invalid Status in lxd source package in Eoan: New Status in systemd source package in Eoan: Invalid Bug description: $ lxc launch ubuntu-daily:eoan devel1 $ sleep 10 # wait for boot $ lxc exec devel1 /bin/bash root@devel1:~# cat /proc/uptime 183.00 173.00 root@devel1:~# cat /etc/cloud/build.info build_name: server serial: 20190531 root@devel1:~# lsb_release -sc eoan root@devel1:~# journalctl --no-pager --list-boots 0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 2019-05-31 15:06:10 UTC root@devel1:~# reboot root@devel1:~# $ lxc exec devel1 /bin/bash ## verify the reboot happened root@devel1:~# cat /proc/uptime 12.00 6.00 ## but journalctl only shows the same boot it did before. root@devel1:~# journalctl --no-pager --list-boots 0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 2019-05-31 15:09:10 UTC ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Fri May 31 15:06:24 2019 MachineType: LENOVO 20KGS3Y900 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=25df9069-80c7-46f4-a47c-305613c2cb6b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS3Y900 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KGS3Y900:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS3Y900:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS3Y900 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1831258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831258] Re: journalctl --list-boots does not recognize boots in a container
Hahahhahaha So yeah because the _host_ bootid is in use =) and you didn't reboot the host. Specifically, everything in systemd reads /proc/sys/kernel/random/boot_id and that appears to be the same as on the host. Maybe lxc/lxd should fake that file and generate new "boot_id" each time container is started. ** Also affects: lxd (Ubuntu) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => Invalid ** Changed in: systemd (Ubuntu Eoan) 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/1831258 Title: journalctl --list-boots does not recognize boots in a container Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in lxd source package in Bionic: New Status in systemd source package in Bionic: Invalid Status in lxd source package in Eoan: New Status in systemd source package in Eoan: Invalid Bug description: $ lxc launch ubuntu-daily:eoan devel1 $ sleep 10 # wait for boot $ lxc exec devel1 /bin/bash root@devel1:~# cat /proc/uptime 183.00 173.00 root@devel1:~# cat /etc/cloud/build.info build_name: server serial: 20190531 root@devel1:~# lsb_release -sc eoan root@devel1:~# journalctl --no-pager --list-boots 0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 2019-05-31 15:06:10 UTC root@devel1:~# reboot root@devel1:~# $ lxc exec devel1 /bin/bash ## verify the reboot happened root@devel1:~# cat /proc/uptime 12.00 6.00 ## but journalctl only shows the same boot it did before. root@devel1:~# journalctl --no-pager --list-boots 0 4ecd6fb081964b75b1ddc09baf1be3d9 Fri 2019-05-31 14:58:48 UTC—Fri 2019-05-31 15:09:10 UTC ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: systemd 240-6ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 Date: Fri May 31 15:06:24 2019 MachineType: LENOVO 20KGS3Y900 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-50-generic root=UUID=25df9069-80c7-46f4-a47c-305613c2cb6b ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET63W (1.38 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS3Y900 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET63W(1.38):bd04/20/2019:svnLENOVO:pn20KGS3Y900:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS3Y900:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS3Y900 dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1831258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831459] Re: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Xenial) Status: New => In Progress -- 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/1831459 Title: 'storage' test needs to wait for systemd-cryptsetup to be active before stopping it Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: Fix Released Bug description: [impact] test case fails because it does not wait for the service to become active before stopping it, resulting in failure to rmmod the scsi_debug module because it's still in use. [test case] check 'storage' test results for systemd in autopkgtest logs, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/ppc64el/s/systemd/20190601_160043_a5281@/log.gz [regression potential] low; test case fix only. [other info] detected and reported by @cascardo in bug 1814373 comment 4 and 5, but separate (non-test) systemd bugfix uploaded for that bug so opening this bug to track fixing the test case. larger fixes/improvements to 'storage' testcase in bug 1829347, but those rejected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831459/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
@ddstreet We don't use systemd-resolver here. It's fairly trivial to set up a VPN service; the openconnect 'make check' uses ocserv automatically, for example. You shouldn't have difficulty reproducing this locally. -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
yes full config. Many cables unplugged because router not fully functional enp3s0 connected to swithch in Tagged port, configured only with Vlan 2. ClientIdentifier=mac not helped my problem looks similar to https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779721 -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830022] Re: DirtyCleanInterval should be 0 by default
The problem there doesn't seem common enough to justify being rls tracked, would still be nice to be fixed and it looks like it's being worked without need of special handling, tagging rls-ee-notfixing ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Tags removed: rls-ee-incoming ** Tags added: rls-ee-notfixing -- 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/1830022 Title: DirtyCleanInterval should be 0 by default Status in cups package in Ubuntu: Confirmed Bug description: Please consider changing DirtyCleanInterval value to 0 as default. Otherwise if cupsd crashes due to (e.g. OOM killer) under a heavy workload even hundreds of jobs may be lost. This concern is backed up by a real-life scenario and leaves the client sending thousands of jobs unaware that many of them are lost during a crash. After cupsd gets restarted it rewinds it's job counter to the last cached and continues unaware about the jobs accepted and lost. Having DirtyCleanInterval set to 0 will cause some performance impact, but not significant under lighter workloads and a completely justified price for reliability under heavy workloads. Test scenario: 1. sudo apt install printer-driver-cups-pdf 2. while [ 1 ]; do lp -d PDF somepdf.pdf; done; 3. # on other terminal kill -9 $(pidof cupsd) 4. Note last job number and wait for cupsd to be restarted by systemd. 5. Once accepting jobs is resumend the job counter is rewound. Expected behavior: Accepted jobs are queued for processing. Actual behavior: Some accepted jobs are lost. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1830022/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
We are not going to do cosmic/n-m changes at this point, best to upgrade to Disco if you need that issue resolved ** Changed in: network-manager (Ubuntu Bionic) Assignee: Olivier Tilloy (osomon) => Till Kamppeter (till-kamppeter) ** Changed in: network-manager (Ubuntu Cosmic) Status: New => Won't Fix -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828102] Re: Regression in ModemManager
** Changed in: modemmanager (Ubuntu Cosmic) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) ** Changed in: modemmanager (Ubuntu Disco) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1828102 Title: Regression in ModemManager Status in modemmanager package in Ubuntu: Fix Released Status in modemmanager source package in Cosmic: In Progress Status in modemmanager source package in Disco: In Progress Status in modemmanager source package in Eoan: Fix Released Bug description: [Impact] [Test case] [Regression potential] The patch is tiny, fixing an obvious overlook, and it only affects CDMA broadband modems, so the risk of a regression is very low. [Original description] ModemManager disconnects after ~30 sec caused by a typo in 1.8 see https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615 and https://gitlab.freedesktop.org/mobile-broadband/ModemManager/issues/119 for details needs a SRU for cosmic and dingo patch attached yechiel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1828102/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
@dwmw2 and/or @till-kamppeter, can you verify the systemd upload for this bug for b and c? -- 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/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: New Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Committed Status in network-manager source package in Cosmic: Won't Fix Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
Is that the full networkd config? Slightly confused why enp3s0 is degraded. Does it have a cable plugged in? Could you tar up and share /run/systemd/netif ? Does adding below [DHCP] ClientIdentifier=mac to the enp3s0.2.network help? -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830121] Re: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch
I've discovered the problem was caused by -tt in the ssh options, which I picked up from somewhere as a step in debugging a prior issue. It works as expected once -tt is removed. Thanks anyway. -- 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/1830121 Title: rsync --rsync-path="sudo rsync" over ssh via pki fails due to protocol mismatch Status in Ubuntu MATE: Invalid Status in rsync package in Ubuntu: Incomplete Bug description: rsync with remote sudo fails over ssh on Ubuntu Mate 18.04.2 rsync version 3.1.2 protocol version 31 - same on local and remote OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 - same on local and remote I have checked for spurious output from .bashrc using $ ssh user@host /bin/true > out.dat which results in $ ls -l *.dat -rw-rw-r-- 1 user user 0 May 22 23:33 out.dat -- The [redacted] command is rsync -AEavvvogt --rsync-path="sudo rsync" --debug=CONNECT -e "ssh -i /home/xxx/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null" --exclude-from=/home/xxx/backup.exclude --delete --link-dest=../$lastdt /etc $dest/$dt; -- The [redacted] output is opening connection using: ssh -i /home/user/.ssh/id_rsa -tt -v -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -l user xxx "sudo rsync" --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 (20 args) OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to xxx [192.168.1.120] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /home/user/.ssh/id_rsa type 0 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug1: Authenticating to xxx:22 as 'user' debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: xxx Warning: Permanently added 'xxx,192.168.1.120' (ECDSA) to the list of known hosts. debug1: rekey after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after 134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info: server-sig-algs= debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Offering public key: RSA SHA256:xxx /home/user/.ssh/id_rsa debug1: Server accepts key: xxx debug1: Authentication succeeded (publickey). Authenticated to xxx ([192.168.1.120]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: pledge: network debug1: client_input_global_request: rtype hostkeys...@openssh.com want_reply 0 debug1: tty_make_modes: no fd or tio debug1: Sending environment. debug1: Sending env LANG = en_GB.UTF-8 debug1: Sending command: sudo rsync --server -vvvlogDtpAre.iLsfxC --delete --link-dest ../20190506_021137 . /home/backups/xxx/20190522_232738 protocol version mismatch -- is your shell clean? (see the rsync man page for an explanation) rsync error: protocol incompatibility (code 2) at compat.c(178) [sender=3.1.2] [sender] _exit_cleanup(code=2, file=compat.c, line=178): about to call exit(2) /etc/sudoers contains userALL= NOPASSWD:/usr/bin/rsync ...which I have tried placing above (as is the default) and below lines beginning %admin and %sudo and the space in "ALL= NOPASSWD..." doesn't seem to make any difference I followed the instructions at https://www.digitalocean.com/community/tutorials/how-to-copy-files-with-rsync-over-ssh https://askubuntu.com/questions/719439/using-rsync-with-sudo-on-the-destination-machine - which worked on 16.04, so I wonder if there may be a bug, although grateful for any other suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1830121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Patch added: "lp1556302-eoan.debdiff" https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+attachment/5268785/+files/lp1556302-eoan.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Eoan: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
make it through crontab and redirect output root@gwd:~# cat /root/networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp2s0 ether carrier configured 3 enp3s0 ether degradedconfigured 4 wg0 none routableconfigured 5 br-mgmt ether routableconfigured 6 br-lan ether no-carrier configuring 7 enp3s0.2 ether degradedconfiguring 7 links listed. root@gwd:~# cat /root/journal-systemd -- Logs begin at Sun 2018-01-28 18:58:18 MSK, end at Tue 2019-06-04 16:06:01 MSK. -- Jun 04 16:02:15 gwd systemd[1]: Starting Network Service... Jun 04 16:02:15 gwd systemd-networkd[635]: br-lan: netdev ready Jun 04 16:02:15 gwd systemd-networkd[635]: br-mgmt: netdev ready Jun 04 16:02:15 gwd systemd-networkd[635]: wg0: netdev ready Jun 04 16:02:15 gwd systemd-networkd[635]: Enumeration completed Jun 04 16:02:15 gwd systemd[1]: Started Network Service. Jun 04 16:02:15 gwd systemd-networkd[635]: enp2s0: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: br-mgmt: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: lo: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: br-lan: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: wg0: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: br-mgmt: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: lo: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: br-lan: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: wg0: Link is not managed by us Jun 04 16:02:15 gwd systemd-networkd[635]: enp3s0.2: netdev ready Jun 04 16:02:15 gwd systemd-networkd[635]: enp3s0: IPv6 successfully enabled Jun 04 16:02:15 gwd systemd-networkd[635]: enp2s0: IPv6 successfully disabled Jun 04 16:02:18 gwd systemd-networkd[635]: enp3s0: Gained carrier Jun 04 16:02:18 gwd systemd-networkd[635]: enp3s0.2: Gained carrier Jun 04 16:02:18 gwd systemd-networkd[635]: br-lan: IPv6 successfully enabled Jun 04 16:02:18 gwd systemd-networkd[635]: br-mgmt: IPv6 successfully enabled Jun 04 16:02:18 gwd systemd-networkd[635]: wg0: IPv6 successfully disabled Jun 04 16:02:18 gwd systemd-networkd[635]: wg0: Gained carrier Jun 04 16:02:18 gwd systemd-networkd[635]: wg0: Configured Jun 04 16:02:18 gwd systemd-networkd[635]: lo: Link is not managed by us Jun 04 16:02:19 gwd systemd-networkd[635]: enp2s0: Gained carrier Jun 04 16:02:19 gwd systemd-networkd[635]: enp2s0: Configured Jun 04 16:02:19 gwd systemd-networkd[635]: br-mgmt: Gained carrier Jun 04 16:02:20 gwd systemd-networkd[635]: enp3s0: Gained IPv6LL Jun 04 16:02:20 gwd systemd-networkd[635]: enp3s0: Configured Jun 04 16:02:20 gwd systemd-networkd[635]: enp3s0.2: Gained IPv6LL Jun 04 16:02:20 gwd systemd-networkd[635]: br-mgmt: Gained IPv6LL Jun 04 16:02:20 gwd systemd-networkd[635]: br-mgmt: Configured -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556302] Re: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default
** Also affects: sudo (Ubuntu Eoan) Importance: Medium Assignee: Ubuntu Security Team (ubuntu-security) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1556302 Title: Ubuntu patch to add HOME to env_keep makes custom commands vulnerable by default Status in sudo package in Ubuntu: Confirmed Status in sudo source package in Eoan: Confirmed Bug description: I wanted to allow certain users to execute a python script as another user, so I created the following sudoers config: Defaults env_reset source_user ALL=(target_user) NOPASSWD: /home/target_user/bin/script.py This results in a highly insecure Python environment because the source user can set HOME and override any Python package by putting files in $HOME/.local/lib/python*/site-packages/. This should be a safe configuration because the default behaviour (as specified in the man page) is that env_reset will replace HOME with the target user's home directory. The "env_reset" option even has special behaviour for bash which has its own potential environment vulnerabilities. However there is an Ubuntu-specific patch in the package (keep_home_by_default.patch) that makes sudo preserve HOME by default, which negates the correct behaviour of "env_reset". It should not be necessary to explicitly specify the "always_set_home" option in order to negate this patch. The patch should be removed and the default /etc/sudoers should explicitly add HOME to "env_keep" for the "allow admins to run any command as root" entries, to get the desired behaviour without creating security issues for other sudoers commands. Note: for quick reference to anyone coming to this bug, this behavior (of sudo keeping the calling user's $HOME) can be disabled by running 'sudo visudo' and adding this line: Defaultsalways_set_home To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1556302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1818527] Re: Stub resolver cache is corrupted
This bug also affects MaaS when commissioning is done with Bionic 18.04 and an external proxy is set. Commissioning fails at the step inside the script when trying to install packages for the test itself. Error message: Temporary failure resolving -- 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/1818527 Title: Stub resolver cache is corrupted Status in systemd package in Ubuntu: Confirmed Bug description: It seems that when systemd-resolve cache an non-existent CNAME record for a domain, any attempt to resolve A record for the same domain fail. systemd version the issue has been seen with Installed: 237-3ubuntu10.13 Used distribution Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic Expected behaviour you didn't see Return A record for a domain when it exists. Unexpected behaviour you saw Resolution failed. Steps to reproduce the problem Whait for 1 minutes (github.com TTL for A record) Try to resolv github.com CNAME record dig CNAME github.com This will return an empty result. Then try to resolve github.com A record dig A github.com. This will now return empty result unless you restart systemd-resolved or wait for cache expiration. At the same time using another DNS will resolve correctly dig A github.com @8.8.8.8. Exemple : Wait for 1 minutes to let cache expire, then run dig CNAME github.com dig A github.com # no result dig A github.com @8.8.8.8 # ;; ANSWER SECTION: # github.com. 59 IN A 192.30.253.113 # github.com. 59 IN A 192.30.253.112 PS: Don't forget to restart systemd-resolve, before trying to post an answer. This bug was first reported in github https://github.com/systemd/systemd/issues/11789 but systemd version in ubuntu is too old. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831599] [NEW] No display activity when coming out of powersave ("kernel BUG at mm/slub.c:296!")
Public bug reported: Since a few weeks, my displays won't wake up from display powersave. The machine stays responsive via SSH. This first occurred on Ubuntu 18.04, and keeps happening on 18.10 (which I had updated to in the hopes of fixing the issue that way). The only escape I've found from this state is via magic SysRq. It can be triggered reliably by waiting for the screensaver to kick in (e.g. overnight). = Note a kernel bug warning in CurrentDmesg.txt = ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jun 4 13:40:47 2019 DistUpgraded: 2019-05-22 12:26:07,943 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: spl, 0.7.9, 4.18.0-20-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) zfs, 0.7.9, 4.18.0-20-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Ellesmere [Radeon RX 470/480/570/570X/580/580X] [1462:341b] MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=ZFS=rpool/ROOT/ubuntu ro nouveau.modeset=0 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to cosmic on 2019-05-22 (13 days ago) dmi.bios.date: 12/23/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A89GTD-PRO dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd12/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer make.log: DKMS make.log for zfs-0.7.9 for kernel 5.1.4-050104-generic (x86_64) Do 23. Mai 18:51:15 CEST 2019 make: *** No targets specified and no makefile found. Stop. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze third-party-packages ubuntu ** Description changed: Since a few weeks, my machine won't wake up from display powersave. This first occurred on Ubuntu 18.04, and keeps happening on 19.04 (which I had updated to in the hopes of fixing the issue that way). The only escape I've found from this state is via magic SysRq. It can be triggered reliably by waiting for the screensaver to kick in (e.g. overnight). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Tue Jun 4 13:40:47 2019 DistUpgraded: 2019-05-22 12:26:07,943 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: - spl,
[Touch-packages] [Bug 1831592] Re: ubuntu audio
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1831592 Title: ubuntu audio Status in pulseaudio package in Ubuntu: New Bug description: After installing cuda 10.1 updated in my ubuntu 18.04 version. I couldn't hear any sound. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Tue Jun 4 16:27:09 2019 InstallationDate: Installed on 2019-06-04 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3305 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z10PA-U8 Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3305:bd10/06/2016:svnASUSTeKCOMPUTERINC.:pnZ10PA-U8Series:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ10PA-U8Series:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct17:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: Z10PA-U8 Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-06-04T16:13:12.811810 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1831592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
The kernel part will be fixed in 5.3, and will be backported to linux- oem-osp1 later ** Also affects: linux-oem-osp1 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Triaged Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: New Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Confirmed Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
Please attach output from networkd on boot prior to / without the extra dhclient unit if you can. $ networkctl | pastebinit $ journalctl -b -u systemd-networkd | pastebinit -- 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/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: New Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
HI Sebastien, Sure. Here is a zip file that it's very easy to use to reproduce the defect. The defect s not in the bsdtar, it's in libarchive. However, since bsdtar depends on libarchive, this can be used to demonstrate the problem as someone reports in the GitHub issue report: https://github.com/libarchive/libarchive/issues/822 If you try to extract the content with bsdtar: # bsdtar -vxf example.zip You will see and error, and if you look to the result in the filesystem, that 'ABCD_1234' and 'empty' are created as files instead of directories. If you try the same operation using unzip in other directory (or after cleaning the previous operation): # unzip example.zip You will see the right result (ABCD_1234 and empty directories). Thanks for take care of this, Alejandro ** Attachment added: "example.zip" https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories Status in libarchive package in Ubuntu: New Bug description: The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is the only version that presents the problem. This version has a known problem when reading file entries in ZIP files, where it incorrectly identifies directories and files entries. It has been confirmed that the previous and following versions (3.3.1+) do not have this problem and the library handles the ZIP files correctly. Is it possible to include a newer version of libarchive (3.3.1+) in Bionic? This problem is seriously affecting some of our systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
One important note here, The defect is only present in version 3.2.2 (Bionic official version now). Previous and next version do work properly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories Status in libarchive package in Ubuntu: New Bug description: The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is the only version that presents the problem. This version has a known problem when reading file entries in ZIP files, where it incorrectly identifies directories and files entries. It has been confirmed that the previous and following versions (3.3.1+) do not have this problem and the library handles the ZIP files correctly. Is it possible to include a newer version of libarchive (3.3.1+) in Bionic? This problem is seriously affecting some of our systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830169] Re: lvm udev rule fails to call systemd-run
** Description changed:
- In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
-ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
+ [Impact]
+ Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
+
+ [Test case]
+ Not available. But since it's just a path fix, it should not be a problem.
+
+ [Regression potential]
+ Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
+
+ [Other info]
+ In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
+ ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1830169
Title:
lvm udev rule fails to call systemd-run
Status in Ubuntu on IBM z Systems:
In Progress
Status in lvm2 package in Ubuntu:
Fix Released
Status in lvm2 source package in Xenial:
New
Status in lvm2 source package in Bionic:
New
Status in lvm2 source package in Cosmic:
New
Status in lvm2 source package in Disco:
New
Status in lvm2 source package in Eoan:
Fix Released
Bug description:
[Impact]
Judging from the rule, this probably means that volumes do not disappear when
the physical volume disappears.
[Test case]
Not available. But since it's just a path fix, it should not be a problem.
[Regression potential]
Removal might now actually work correctly, but it's not entirely clear how
that could cause a regression.
[Other info]
In /lib/udev/rules.d/69-lvm-metad.rules file, it calls /bin/systemd-run
command during removal ---
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
But /bin/systemd-run is not found, in fact systemd-run is in /usr/bin
/systemd-run.
xx:~$ cat /etc/issue
Ubuntu 18.04.2 LTS \n \l
xx:~$ ls /bin/systemd-run
ls: cannot access '/bin/systemd-run': No such file or directory
xx:~$ ls /usr/bin/systemd-run
/usr/bin/systemd-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1830169/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Verified for cosmic: apt-cache policy cups-daemon cups-daemon: Installed: 2.2.8-5ubuntu1.4 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:09:12:13 +] [Job 1] Job completed. D [04/Jun/2019:09:12:44 +] [Job 1] Removing from history. PreserveJobHistory No: I [04/Jun/2019:09:13:03 +] [Job 2] Job completed. D [04/Jun/2019:09:13:03 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:09:13:30 +] [Job 3] Job completed. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to Yes. Repeat 2-3. 5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Verified for disco: apt-cache policy cups-daemon cups-daemon: Installed: 2.2.10-4ubuntu2 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:09:03:14 +] [Job 1] Job completed. D [04/Jun/2019:09:03:45 +] [Job 2] Removing from history. PreserveJobHistory No: I [04/Jun/2019:09:04:06 +] [Job 2] Job completed. D [04/Jun/2019:09:04:06 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:09:04:50 +] [Job 3] Job completed. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- 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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Fix Committed Status in cups source package in Bionic: Fix Committed Status in cups source package in Cosmic: Fix Committed Status in cups source package in Disco: Fix Committed Bug description: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] 1. Set PreserveJobHistory to 30. Set LogLevel to debug. 2. Schedule a job for printing. 3. Check the error_log. 4. Set PreserveJobHistory to Yes. Repeat 2-3. 5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): 30: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is removed right after processing. Actual results (for PreserveJobHistory values): 30: Job is immediately removed from history. Yes: Job is never removed. No: Job is removed right after processing. [Regression Potential] * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Verified for bionic. apt-cache policy cups-daemon cups-daemon: Installed: 2.2.7-1ubuntu2.6 lp -d PDF /usr/share/cups/data/default.pdf PreserveJobHistory 30: I [04/Jun/2019:08:52:25 +] [Job 1] Job completed D [04/Jun/2019:08:52:56 +] [Job 1] Removing from history. PreserveJobHistory No: I [04/Jun/2019:08:53:58 +] [Job 2] Job completed. D [04/Jun/2019:08:53:58 +] [Job 2] Removing from history. PreserveJobHistory Yes: I [04/Jun/2019:08:54:55 +] [Job 5] Job completed. (...) ** Description changed: [Impact] - The documentation allows the following types of arguments for the PreserveJobHistory parameter: + The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds - - The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . + + The value in seconds is treated in the same as 'No' resulting in + immediate removing of jobs from history, while it is supposed to save it + for . [Test Case] - * Set PreserveJobHistory to 300. - * Schedule a job for printing. - * Check the error_log. + 1. Set PreserveJobHistory to 300. + 2. Schedule a job for printing. + 3. Check the error_log. + 4. Set PreserveJobHistory to Yes. Repeat 2-3. + 5. Set PreserveJobHistory to No. Repeat 2-3. + - Expected result: - Job is save for at least 300 seconds. + Expected result (for PreserveJobHistory values): + 300: Job is save for at least 300 seconds. + Yes: Job is never removed. + No: Job is removed right after processing. - Actual results: - Job is immediately removed from history. + + Actual results (for PreserveJobHistory values): + 300: Job is immediately removed from history. + Yes: Job is never removed. + No: Job is removed right after processing. [Regression Potential] - * With the fix the jobs will be saved longer than before, so in tight + * With the fix the jobs will be saved longer than before, so in tight conditions (low disk space) and heavy workload it may affect memory/disk space consumption and lead to running out of free space in worst case. [Other Info] - - * Original bug description: + + * Original bug description: 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: Installed: 2.1.3-4ubuntu0.3 Candidate: 2.1.3-4ubuntu0.3 Version table: *** 2.1.3-4ubuntu0.3 500 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf PreserveJobFiles Yes PreserveJobFiles No PreserveJobFiles seconds Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... ** Description changed: [Impact] The documentation allows the following types of arguments for the PreserveJobHistory parameter: PreserveJobHistory Yes PreserveJobHistory No PreserveJobHistory seconds The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . [Test Case] - 1. Set PreserveJobHistory to 300. + 1. Set PreserveJobHistory to 30. 2. Schedule a job for printing. 3. Check the error_log. - 4. Set PreserveJobHistory to Yes. Repeat 2-3. - 5. Set PreserveJobHistory to No. Repeat 2-3. - + 4. Set PreserveJobHistory to Yes. Repeat 2-3. + 5. Set PreserveJobHistory to No. Repeat 2-3. Expected result (for PreserveJobHistory values): - 300: Job is save for at least 300 seconds. + 300: Job is save for at least 30 seconds. Yes: Job is never removed. No: Job is
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
Could you add your "journalctl -b 0" log to the bug?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
** Changed in: libdrm (Ubuntu)
Status: New => Incomplete
** Changed in: libdrm (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
you have proposed enabled for a reason? Looks like the upgrade is
incomplete, libdrm didn't cause your issues but something else, likely
mesa
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
New
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
