[Touch-packages] [Bug 1331856] Re: apparmor-utils don't work when defining a variable on
Still exists in Ubuntu Bionic Beaver (18.04).
apparmor-utils 2.12-4ubuntu5.1 amd64
# aa-logprof
ERROR: Values added to a non-existing variable @{HOMEDIRS}: /srv/ in
tunables/home.d/ubuntu
--
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/1331856
Title:
apparmor-utils don't work when defining a variable on
Status in AppArmor:
Triaged
Status in apparmor package in Ubuntu:
Confirmed
Bug description:
When a variable is set in tunables/home.d/ the apparmor-utils programs
don't work and return this error messages:
root@ws24:~# aa-logprof
Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in
apparmor.loadincludes()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4643, in
loadincludes
load_include(fi)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 4520, in
load_include
incdata = parse_profile_data(data, incfile, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2839, in
parse_profile_data
store_list_var(profile_data[profile]['lvar'], list_var, value,
var_operation)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3279, in
store_list_var
raise AppArmorException(_('Values added to a non-existing variable: %s')
% list_var)
apparmor.common.AppArmorException: 'Values added to a non-existing variable:
@{HOMEDIRS}'
root@ws24:~#
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1331856/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829540] Re: [HDA-Intel - HDA Intel PCH, playback] 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/1829540 Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all Status in alsa-driver package in Ubuntu: Expired Bug description: After computer returns from being locked, after I type my password, the option of where to hear the sounds from the computer appears, selecting speaker, still I can not hear any sound from the computer!! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio CurrentDesktop: Unity Date: Fri May 17 17:07:11 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-02-15 (91 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 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: luciana2245 F...m pulseaudio /dev/snd/controlC0: luciana2245 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0C77WG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd07/23/2018:svnDellInc.:pnInspiron15-3573:pvr1.4.0:rvnDellInc.:rn0C77WG:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3573 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830441] Re: libkrb5-3 1.16.2 can crash client programs
[Expired for krb5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: krb5 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1830441 Title: libkrb5-3 1.16.2 can crash client programs Status in krb5 package in Ubuntu: Expired Bug description: Ubuntu Release: 18.04.2 LTS Package: libkrb5-3 1.16.2 The libkrb5-3 package (MIT Kerberos library) shipped with Ubuntu 18.04.2 has a known bug which can cause a program using the library to crash when using MEMORY ccaches. This was introduced as a regression in version 1.16.2 of the MIT kerberos library, and fixed in 1.16.3. Regression ticket: https://krbdev.mit.edu/rt/Ticket/Display.html?id=8771 Release notes for 1.16.3 (see "Fix a regression"): https://web.mit.edu/kerberos/krb5-1.16/ Can the libkrb5-3 package be updated to version 1.16.3 for the Ubuntu 18.04 release series? We have software (not part of Ubuntu) that uses MEMORY ccaches extensively and it is impacted by this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1830441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815649] Re: Vim on Ubuntu Disc 19.04 does not work
[Expired for vim (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vim (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1815649 Title: Vim on Ubuntu Disc 19.04 does not work Status in vim package in Ubuntu: Expired Bug description: Hi guys The Vim on Ubuntu Disk 19.04 comes installed by default, but so far does not work. It is stated that it is installed by the Ubuntu software, but by the terminal says it is not installed as can be seen in the attached image. Command 'vim' not found, but can be installed with: Awaiting arrangements and correction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1815649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837580] Re: memlock is not set
systemd user fighting PAM for limits is from my POV certainly a systemd bug. ** Package changed: pam (Ubuntu) => systemd (Ubuntu) ** Also affects: systemd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919528 Importance: Unknown Status: Unknown -- 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/1837580 Title: memlock is not set Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: I discovered this in relation to jack, which installs /etc/security/limits.d/audio.conf, containing: @audio - rtprio 95 @audio - memlockunlimited For a user in the audio group: $ulimit -l -r max locked memory (kbytes, -l) 65536 real-time priority (-r) 95 So jack (run as user via qjackctl) reports: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) but does not report that it cannot set real-time priority, which it does if run by a user not in the audio group. I also tried putting the line in /etc/security/limits.conf, and trying a number rather than "unlimited", but it didn't help. Also reported independently here: https://askubuntu.com/questions/1142943/ulimit-unlimited-cannot-set ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules:amd64 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-lowlatency 5.0.8 Uname: Linux 5.0.0-20-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 15:07:52 2019 InstallationDate: Installed on 2016-10-25 (1000 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pam UpgradeStatus: Upgraded to disco on 2019-07-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837580] Re: memlock is not set
"https://bugzilla.redhat.com/show_bug.cgi?id=1364332 tl;dr it’s expected behavior since /etc/security/limits.* is not used by systemd, and further the behavior of pam_limits with group-based limits can’t be reproduced in systemd." https://bugs.debian.org/919528#10 ** Bug watch added: Red Hat Bugzilla #1364332 https://bugzilla.redhat.com/show_bug.cgi?id=1364332 ** Bug watch added: Debian Bug tracker #919528 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919528 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1837580 Title: memlock is not set Status in systemd package in Ubuntu: New Status in systemd package in Debian: Unknown Bug description: I discovered this in relation to jack, which installs /etc/security/limits.d/audio.conf, containing: @audio - rtprio 95 @audio - memlockunlimited For a user in the audio group: $ulimit -l -r max locked memory (kbytes, -l) 65536 real-time priority (-r) 95 So jack (run as user via qjackctl) reports: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) but does not report that it cannot set real-time priority, which it does if run by a user not in the audio group. I also tried putting the line in /etc/security/limits.conf, and trying a number rather than "unlimited", but it didn't help. Also reported independently here: https://askubuntu.com/questions/1142943/ulimit-unlimited-cannot-set ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules:amd64 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-lowlatency 5.0.8 Uname: Linux 5.0.0-20-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 15:07:52 2019 InstallationDate: Installed on 2016-10-25 (1000 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pam UpgradeStatus: Upgraded to disco on 2019-07-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
I checked Dell XPS 13 9370 with Ubuntu 18.04.2 and xkb-data 2.23.1-1ubuntu1.18.04.1. It also needs to apply https://github.com/systemd/systemd/commit/8cc9fefe2e3e0b0d2c235e8b26abc82c4106c5f6 to systemd or the airplane mode will always be enabled when keeping pressing WiFi hotkey. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
** Changed in: pulseaudio (Ubuntu Disco) Importance: Undecided => High -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1827842] Re: pulseaudio should not load module-x11-bell in gnome-shell
** Changed in: pulseaudio (Ubuntu Disco) Importance: Undecided => Low -- 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/1827842 Title: pulseaudio should not load module-x11-bell in gnome-shell Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: * Impact The package force load a bell sound which can conflicts with the user configuration * Test case - Enable a login sound in session - Login into a GNOME/Ubuntu session -> the configured sound should be played * Regression potential Try other desktop environments to make sure their login sound behaviour isn't changed, it shouldn't since the customization dropped was specific to the Ubuntu sound theme --- The package `pulseaudio` installs a startup script in `/etc/xdg/autostart/pulseaudio.desktop`, which itself runs `/usr/bin/start-pulseaudio-x11`, which loads a number of x11 related modules in `pulseaudio`. One of these modules is `module-x11-bell`, which makes `pulseaudio` play a sound each time a system bell is emitted (usually by terminal applications, such as bash or vim). This is redundant with gnome-shell, which is also able to handle the system bell (through the gsetting key `org.gnome.desktop.sound event-sounds`). The gnome system bell is directly configurable by the user (Settings > Sound), so it should be preferred over pulseaudio's own system bell. I suggest to patch the `/usr/bin/start-pulseaudio-x11`, to avoid loading `start-pulseaudio-x11` if it detects it is running in Gnome Shell (e.g. if GNOME_SHELL_SESSION_MODE is set). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1827842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
For PulseAudio changes, feel free to commit them to git immediately, just don't tag them: https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu- bionic They will then be included in whatever version we manage to successfully release next. -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
** Tags added: oem-priority -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837683] Re: Xorg freeze
When the problem is happening, does the kernel log show any problems? (run: dmesg) ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - Xorg freeze + Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed ** Changed in: xorg-server (Ubuntu) Importance: Undecided => High -- 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/1837683 Title: Screen stops updating after about 8 hours - (EE) modeset(0): present flip failed Status in xorg-server package in Ubuntu: Incomplete Bug description: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~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/1837683/+subscriptions -- Mailing list: https://launchpad.net/~touch-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)
** Tags added: originate-from-1837165 somerville -- 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 HWE Next: New 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 1837683] [NEW] Xorg freeze
Public bug reported: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1047-oem root=UUID=77efb06b-1ce6-4749-a131-67f57aa8b21b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0KTW76 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd03/29/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn0KTW76:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~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 freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1837683 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: environment: - XPS-13-938 - connect 5G ac wifi - disabled suspend in power setting - disabled blank screen in power setting steps: - play 4k video by chrome on youtube[1] overnight symptom: - after about 8 hours, the screen is black and keyboard and mouse can not wake up screen. - the audio of 4K video is still playing, I can hear that when screen is black. - magic key still work, so I can reboot system by magic key. - a repeat error message in syslog: " Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (WW) modeset(0): Page flip failed: Invalid argument Jul 24 01:25:49 u-XPS-13-9380 /usr/lib/gdm3/gdm-x-session[2217]: (EE) modeset(0): present flip failed " [1] https://www.youtube.com/watch?v=pkKBXH2qc_I=11701s ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-1047.52-oem 4.15.18 Uname: Linux 4.15.0-1047-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 09:47:59 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08af] InstallationDate: Installed on 2019-07-20 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine:
[Touch-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** This bug is no longer a duplicate of bug 1818862 Totem player hangs when seeking video due to [gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.] -- 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/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed. Status in Libva: Unknown Status in Mesa: Unknown Status in Totem: Unknown Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f36d74be6ec6814d0d81897848945dfb17739b84 https://errors.ubuntu.com/problem/21e6ce32534f56195547dcde1e33d883f2a01957 https://errors.ubuntu.com/problem/a0da0313b3f76e479f1052b60522e4c2ec2f1de6 https://github.com/intel/intel-vaapi-driver/issues/448 (or 451) https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa) https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k, forward and back. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1821525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
** Changed in: totem (Ubuntu) Status: Invalid => Confirmed ** Description changed: + https://errors.ubuntu.com/problem/f36d74be6ec6814d0d81897848945dfb17739b84 + https://errors.ubuntu.com/problem/21e6ce32534f56195547dcde1e33d883f2a01957 + https://errors.ubuntu.com/problem/a0da0313b3f76e479f1052b60522e4c2ec2f1de6 + https://github.com/intel/intel-vaapi-driver/issues/451 https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa) https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k, forward and back. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Bug watch added: github.com/intel/intel-vaapi-driver/issues #451 https://github.com/intel/intel-vaapi-driver/issues/451 ** Also affects: libva via https://github.com/intel/intel-vaapi-driver/issues/451 Importance: Unknown Status: Unknown ** Also affects: mesa via https://bugs.freedesktop.org/show_bug.cgi?id=110232 Importance: Unknown Status: Unknown ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/issues/315 Importance: Unknown Status: Unknown ** Changed in: intel-vaapi-driver (Ubuntu) Importance: Undecided => Medium ** Bug watch added: github.com/intel/intel-vaapi-driver/issues #448 https://github.com/intel/intel-vaapi-driver/issues/448 ** Changed in: libva Remote watch: github.com/intel/intel-vaapi-driver/issues #451 => github.com/intel/intel-vaapi-driver/issues #448 ** Description changed: https://errors.ubuntu.com/problem/f36d74be6ec6814d0d81897848945dfb17739b84 https://errors.ubuntu.com/problem/21e6ce32534f56195547dcde1e33d883f2a01957 https://errors.ubuntu.com/problem/a0da0313b3f76e479f1052b60522e4c2ec2f1de6 - https://github.com/intel/intel-vaapi-driver/issues/451 + https://github.com/intel/intel-vaapi-driver/issues/448 (or 451) https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa) https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k, forward and back. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02
[Touch-packages] [Bug 1821525] Re: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: intel-vaapi-driver (Ubuntu) Status: New => Confirmed -- 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/1821525 Title: totem assert failure: totem: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: Assertion `0' failed. Status in Libva: Unknown Status in Mesa: Unknown Status in Totem: Unknown Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/f36d74be6ec6814d0d81897848945dfb17739b84 https://errors.ubuntu.com/problem/21e6ce32534f56195547dcde1e33d883f2a01957 https://errors.ubuntu.com/problem/a0da0313b3f76e479f1052b60522e4c2ec2f1de6 https://github.com/intel/intel-vaapi-driver/issues/448 (or 451) https://bugzilla.freedesktop.org/show_bug.cgi?id=110232 (No Mesa) https://gitlab.gnome.org/GNOME/totem/issues/315 (No totem) --- Watching movie 4k, forward and back. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: totem 3.32.0-1ubuntu1 Uname: Linux 5.0.4-050004-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AssertionMessage: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. CurrentDesktop: ubuntu:GNOME Date: Sun Mar 24 11:18:37 2019 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-02 (111 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=es_CL:es PATH=(custom, no user) LANG=es_CL.UTF-8 Signal: 6 SourcePackage: totem StacktraceTop: __assert_fail_base (fmt=0x7f06f2ac2d6a , assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=) at assert.c:92 __GI___assert_fail (assertion=0x7f06b2cbcba4 "0", file=0x7f06b29b1cd0 "gen9_mfd.c", line=649, function=0x7f06b29b23e0 "gen9_hcpd_get_reference_picture_frame_id") at assert.c:101 ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so vaEndPicture () from /usr/lib/x86_64-linux-gnu/libva.so.2 Title: totem assert failure: totem: gen9_mfd.c:649: gen9_hcpd_get_reference_picture_frame_id: La declaración `0' no se cumple. UpgradeStatus: Upgraded to disco on 2018-12-02 (111 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1821525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
@sebastien or anyone else in the sponsor-team, Please review my debdiff for bionic in the #19 and if possible, please enqueue it. thx. -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
** No longer affects: systemd (Ubuntu) ** No longer affects: systemd (Ubuntu Eoan) ** No longer affects: systemd (Ubuntu Disco) ** No longer affects: systemd (Ubuntu Bionic) ** No longer affects: systemd (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Invalid Status in linux source package in Disco: Invalid Status in linux source package in Eoan: Invalid Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change
** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dan Streetman (ddstreet) -- 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/1831787 Title: Bogus routes after DHCP lease change Status in netplan: Invalid Status in systemd package in Ubuntu: Triaged Bug description: Netplan config: network: version: 2 renderer: networkd ethernets: eno4: dhcp4: no eno1np0: dhcp4: no addresses: - 172.16.0.2/24 bridges: br0: dhcp4: yes interfaces: - eno4 On initial boot, machine got 10.0.15.109 IP address: May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 10.0.15.109/23 via 10.0.15.253 At one point, DHCP server reserver this IP address and client eventually picked up new IP address: May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address 10.0.15.128/23 via 10.0.15.253 This resulted in IP addresses: # ip -o a 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever preferred_lft forever 1: loinet6 ::1/128 scope host \ valid_lft forever preferred_lft forever 2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\ valid_lft forever preferred_lft forever 2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \ valid_lft forever preferred_lft forever 6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\ valid_lft 503sec preferred_lft 503sec 6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \ valid_lft forever preferred_lft forever So far, everything is fine. But, the routes on the machine are bogus: # ip r default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 routes with src 10.0.15.109 should have been removed when lease was renewed. I'm not sure if this is a bug in netplan or systemd. This is 18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI
** Tags removed: ddstreet-next systemd ** Changed in: systemd (Ubuntu Eoan) Assignee: Dan Streetman (ddstreet) => (unassigned) -- 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/1831296 Title: __main__.SeccompTest is failing on Ubuntu CI Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Eoan: Fix Committed Bug description: Since https://github.com/systemd/systemd/pull/12430 was merged and libsecomp was updated the test has been failing on Ubuntu CI: https://github.com/systemd/systemd/issues/12709. By analogy with https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c, the test should look for either "killed" or "dumped". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Tags removed: ddstreet-next -- 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 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** Description changed: [Impact] - * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the + * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd-resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. + + [Other Info] + + Note that systemd in Eoan is being upgraded to upstream 242, so I am not + adding this to Eoan now, as I don't want to disturb the merge. If needed + after the merge, I'll add to Eoan. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
** Description changed: + [impact] + + restarting systemd-networkd drops carrier on all bond slaves, + temporarily interrupting networking over the bond. + + [test case] + + on a bionic system with 2 interfaces that can be put into a bond, create + config files such as: + + root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev + [NetDev] + Name=bond0 + Kind=bond + + root@lp1833671:~# cat /etc/systemd/network/20-ens8.network + [Match] + Name=ens8 + + [Network] + Bond=bond0 + + root@lp1833671:~# cat /etc/systemd/network/20-ens9.network + [Match] + Name=ens9 + + [Network] + Bond=bond0 + + root@lp1833671:~# cat /etc/systemd/network/30-bond0.network + [Match] + Name=bond0 + + [Network] + Address=1.2.3.4/32 + + + restart networkd, or reboot, and verify the bond is up: + + root@lp1833671:~# ip a + 3: ens8: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 + link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff + 4: ens9: mtu 1500 qdisc fq_codel master bond0 state UP group default qlen 1000 + link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff + 5: bond0: mtu 1500 qdisc noqueue state UP group default qlen 1000 + link/ether 42:30:62:cc:36:2b brd ff:ff:ff:ff:ff:ff + inet 1.2.3.4/32 scope global bond0 +valid_lft forever preferred_lft forever + inet6 fe80::4030:62ff:fecc:362b/64 scope link +valid_lft forever preferred_lft forever + + + restart networkd and check /var/log/syslog: + + root@lp1833671:~# systemctl restart systemd-networkd + root@lp1833671:~# cat /var/log/syslog + ... + Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Lost carrier + Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Lost carrier + Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens9: Gained carrier + Jul 23 21:08:07 lp1833671 systemd-networkd[1805]: ens8: Gained carrier + + [regression potential] + + this changes how bond slaves are managed, so regressions could affect + any configurations using bonding. + + [other info] + + the patch is already included in d, and ifupdown manages networking in + x, so this is needed only for b. + + [original description] + Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 -- 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: [impact] restarting systemd-networkd drops carrier on all bond slaves, temporarily interrupting networking over the bond. [test case] on a bionic system with 2 interfaces that can be put into a bond, create config files such as: root@lp1833671:~# cat /etc/systemd/network/10-bond0.netdev [NetDev] Name=bond0 Kind=bond root@lp1833671:~# cat /etc/systemd/network/20-ens8.network [Match] Name=ens8 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/20-ens9.network [Match] Name=ens9 [Network] Bond=bond0 root@lp1833671:~# cat /etc/systemd/network/30-bond0.network [Match] Name=bond0 [Network]
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
** Description changed: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h - On the dhcp client system, use networkd config such as: - $ cat /etc/systemd/network/80-ens8.network + $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 - Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 - inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 -valid_lft forever preferred_lft forever - inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 -valid_lft 3580sec preferred_lft 3580sec + inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 + valid_lft forever preferred_lft forever + inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 + valid_lft 3580sec preferred_lft 3580sec $ ip r - default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 - 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 - 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 + default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 + 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 + 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 - 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 - + 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 - inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 -valid_lft forever preferred_lft forever - inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 -valid_lft 3585sec preferred_lft 3585sec + inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 + valid_lft forever preferred_lft forever + inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 + valid_lft 3585sec preferred_lft 3585sec $ ip r - default via 10.10.0.1 dev ens8 proto dhcp metric 1024 - 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 + default via 10.10.0.1 dev ens8 proto dhcp metric 1024 + 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp-provided address: $ ip r get 1.1.1.1 - 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 + 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 - - If the router, 10.10.0.1, only will forward traffic sent from the dhcp address it provided, 10.10.0.75, then this configuration will result in the client being unable to reach anything through the router, because all its packets will have a source address of 10.10.0.5, which the router would drop/reject. + If the router, 10.10.0.1, only will forward traffic sent from the dhcp + address it provided, 10.10.0.75, then this configuration will result in + the client being unable to reach anything through the router, because + all its packets will have a source address of 10.10.0.5, which the + router would drop/reject. [regression potential] this only affects dhcp routes provided by a dhcp server using the 'static' or 'classless' route dhcp options. Since this behavior is currently the default when a system doesn't add static address(es) to interfaces that also get dhcp addresses, this is likely not a change in behavior for the vast
[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
You won't be getting it fixed unless someone tells me what's needed from mesa upstream which is missing from 19.0.8. 19.0.x series is dead and won't get new upstream versions anymore... ** Package changed: libdrm (Ubuntu) => mesa (Ubuntu) -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in mesa package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1837170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** Patch added: "lp1668771-disco.debdiff" https://bugs.launchpad.net/systemd/+bug/1668771/+attachment/5278759/+files/lp1668771-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
** Bug watch added: github.com/systemd/systemd/issues #10118 https://github.com/systemd/systemd/issues/10118 ** Also affects: systemd via https://github.com/systemd/systemd/issues/10118 Importance: Unknown Status: Unknown ** Tags added: ddstreet-next systemd -- 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1833671] Re: bond interfaces stop working after restart of systemd-networkd
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Bionic) 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/1833671 Title: bond interfaces stop working after restart of systemd-networkd Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: In Progress Bug description: Running systemd-networkd from systemd 237-3ubuntu10.23 on Ubuntu 18.04.2 I have one machine where, every time systemd-networkd restarts (ie every time there is an update to systemd) the bond0 interface stops working. I see both physical interfaces go soft down and then come back again: Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SEC Jun 21 07:28:24 odin.openstreetmap.org systemd[1]: Detected architecture x86-64. Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for backup interface eno2, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: bond0: link status down for active interface eno1, disabling it in 200 ms Jun 21 07:28:24 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: 8021q: adding VLAN 0 to HW filter on device eno1 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 200 ms for interface eno2 Jun 21 07:28:25 odin.openstreetmap.org kernel: bond0: link status up again after 100 ms for interface eno1 and after that nothing until I stop systemd-networkd, delete the bond interface, and then start systemd-networkd again. On most machines the cycle seems to take a bit longer and the interfaces reach a hard down start before coming back and in that case there seems to be no problem. I think this is likely an instance of this upstream bug: https://github.com/systemd/systemd/issues/10118 which has a fix here: https://github.com/systemd/systemd/pull/10465 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1833671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: [SRU] systemd-resolved negative caching for extended period of time
** Tags added: sts-sponsor sts-sponsor-ddstreet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835581] Re: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes
** Changed in: systemd (Ubuntu Cosmic) Status: In Progress => Won't Fix ** Tags added: sts sts-sponsor sts-sponsor-ddstreet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1835581 Title: networkd-dhcp4 does not set prefsrc for dhcp-provided classless or static routes Status in systemd: Fix Released Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [impact] the systemd networkd dhcp4 client sets the prefsrc for the default route added when a dhcp server provides only the gateway; but if the dhcp server provides classless route(s), those are configured instead, and the prefsrc is not set for those. Normally this is ok, but if the dhcp client system has other address(es) configured on the interface using dhcp, then the src for packets sent through a classless/static route might not be the same as the address provided by the dhcp server. If the gateway/router provided in the dhcp classless/static route(s) only allows traffic from the address provided to the dhcp client, then traffic from the dhcp client may be dropped by the gateway/router. [test case] set up a dhcp server system (e.g. ubuntu with dnsmasq installed and configured) and a dhcp client system. For example on the dhcp server, use this dnsmasq config: interface=ens8 bind-interfaces domain=test,10.10.0.0/24 dhcp-option=42,10.10.0.1 dhcp-range=test,10.10.0.10,10.10.0.100,1h On the dhcp client system, use networkd config such as: $ cat /etc/systemd/network/80-ens8.network [Match] Name=ens8 [Network] DHCP=ipv4 LinkLocalAddressing=ipv6 Address=10.10.0.5/24 Reboot the client, or restart networkd, and it should result in: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3580sec preferred_lft 3580sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp src 10.10.0.75 metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 10.10.0.1 dev ens8 proto dhcp scope link src 10.10.0.75 metric 1024 Note that, because networkd completes the static ip configuration before the dhcp reply is returned and processed, the static address is used for the subnet-local routing. But for global routing through the gateway, the dhcp-provided address is used: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.75 uid 1000 Now on the server, add a classless route: dhcp-option=121,0.0.0.0/0,10.10.0.1 and restart dnsmasq on the server. Then on the client, reboot. It should now have: $ ip -4 a show ens8 3: ens8: mtu 1500 qdisc fq_codel state UP group default qlen 1000 inet 10.10.0.5/24 brd 10.10.0.255 scope global ens8 valid_lft forever preferred_lft forever inet 10.10.0.75/24 brd 10.10.0.255 scope global secondary dynamic ens8 valid_lft 3585sec preferred_lft 3585sec $ ip r default via 10.10.0.1 dev ens8 proto dhcp metric 1024 10.10.0.0/24 dev ens8 proto kernel scope link src 10.10.0.5 Now, the global route will use the static address, not the dhcp- provided address: $ ip r get 1.1.1.1 1.1.1.1 via 10.10.0.1 dev ens8 src 10.10.0.5 uid 1000 If the router, 10.10.0.1, only will forward traffic sent from the dhcp address it provided, 10.10.0.75, then this configuration will result in the client being unable to reach anything through the router, because all its packets will have a source address of 10.10.0.5, which the router would drop/reject. [regression potential] this only affects dhcp routes provided by a dhcp server using the 'static' or 'classless' route dhcp options. Since this behavior is currently the default when a system doesn't add static address(es) to interfaces that also get dhcp addresses, this is likely not a change in behavior for the vast majority of systems. And any systems that do add static address(es) would usually be able to route through a gateway from either the dhcp-provided, or static, address. So the regression potential for this change should be low. [other info] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1835581/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
Currently I found that downgrading these packages: libgl1-mesa-dri_18.2.8-0ubuntu0~18.10.2_amd64.deb mesa-vdpau-drivers_18.2.8-0ubuntu0~18.10.2_amd64.deb I can run Kodi with every single Ubuntu package updated, including libdrm-amdgpu. **Note: from oibaf's ppa I need only libdrm-amdgpu1 libdrm-common libdrm2 libgl1-mesa-dri vdpau-driver-all mesa-vdpau-drivers upgraded to have it running well. I'll give disco a try, but personally I prefer LTS versions for a more solid UI experience. I'll be here, patiently waiting for the next updates to see if I got it fixed. ;) -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: systemd-resolved negative caching for extended period of time
** Patch added: "lp1668771-bionic.debdiff" https://bugs.launchpad.net/systemd/+bug/1668771/+attachment/5278752/+files/lp1668771-bionic.debdiff ** Summary changed: - systemd-resolved negative caching for extended period of time + [SRU] systemd-resolved negative caching for extended period of time -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: [SRU] systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. The following patch https://github.com/systemd/systemd/pull/13047 implements the required changes. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1668771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668771] Re: systemd-resolved negative caching for extended period of time
** Description changed: - 231-9ubuntu3 + [Impact] - If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the + * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd-resolved to have the negative caching purged. - After SERVFAIL DNS server issue has been resolved, chromium/firefox + * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. + + [Test Case] + + * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), + however, there are several use cases on which this condition is not acceptable (See #5552 comments) + and the only workaround would be to disable cache entirely or flush it , which isn't optimal. + + * Configure /etc/systemd/resolved.conf as follows: + + Cache=yes (default) + + * Restart systemd-resolved (systemctl restart systemd-resolved.service) + + * Run a host/getent command against a entry that will return SERVFAIL + and check the journalctl output to see that the reply gets served from + cache. + + root@systemd-disco:/home/ubuntu# host www.no-record.cl + Host www.montemar.cl not found: 2(SERVFAIL) + root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n + -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- + Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Transaction 6222 for on scope dns on ens3/* now complete with + Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Sending response packet with id 61042 on interface 1/AF_INET. + Jul 23 15:10:10 systemd-disco systemd-resolved[1282]: Freeing transaction 6222. + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Got DNS stub UDP query packet for id 53580 + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Looking up RR for www.no-record.cl IN A. + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: RCODE SERVFAIL cache hit for www.no-record.cl IN A + Jul 23 15:10:17 systemd-disco systemd-resolved[1282]: Transaction 58570 for < www.no-record.cl IN A> on scope dns on ens3/* now complete with scope dns on ens3/. + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Using feature level UDP for transaction 22382. + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending query packet with id 22382. + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Processing incoming packet on transaction 22382 (rcode=SERVFAIL). + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Server returned error: SERVFAIL + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Not caching negative entry for: www.metaklass.org IN A, cache mode set to no-negative + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Transaction 22382 for on scope dns on ens3/ now complete with from network (unsigned). + Jul 12 18:48:31 systemd-disco systemd-resolved[2635]: Sending response packet with id 31060 on interface 1/AF_INET. + + The following patch https://github.com/systemd/systemd/pull/13047 + implements the required changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1668771 Title: systemd-resolved negative caching for extended period of time Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Disco: In Progress Status in systemd source package in Eoan: In Progress Bug description: [Impact] * If a DNS lookup returns SERVFAIL, systemd-resolved seems to cache the result for very long (infinity?). I have to restart systemd- resolved to have the negative caching purged. * After SERVFAIL DNS server issue has been resolved, chromium/firefox still returns DNS error despite host can correctly resolve the name. [Test Case] * If a lookup returns SERVFAIL systemd-resolved will cache the result for 30s (See 201d995), however, there are several use cases on which this condition is not acceptable (See #5552 comments) and the only workaround would be to disable cache entirely or flush it , which isn't optimal. * Configure /etc/systemd/resolved.conf as follows: Cache=yes (default) * Restart systemd-resolved (systemctl restart systemd- resolved.service) * Run a host/getent command against a entry that will return SERVFAIL and check the journalctl output to see that the reply gets served from cache. root@systemd-disco:/home/ubuntu# host www.no-record.cl Host www.montemar.cl not found: 2(SERVFAIL) root@systemd-disco:/home/ubuntu# journalctl -u systemd-resolved -n -- Logs begin at Fri 2019-07-12 18:09:42 UTC, end at Tue 2019-07-23 15:10:17 UTC. -- Jul 23 15:10:10 systemd-disco systemd-resolved[1282]:
[Touch-packages] [Bug 1837580] [NEW] memlock is not set
Public bug reported: I discovered this in relation to jack, which installs /etc/security/limits.d/audio.conf, containing: @audio - rtprio 95 @audio - memlockunlimited For a user in the audio group: $ulimit -l -r max locked memory (kbytes, -l) 65536 real-time priority (-r) 95 So jack (run as user via qjackctl) reports: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) but does not report that it cannot set real-time priority, which it does if run by a user not in the audio group. I also tried putting the line in /etc/security/limits.conf, and trying a number rather than "unlimited", but it didn't help. Also reported independently here: https://askubuntu.com/questions/1142943/ulimit-unlimited-cannot-set ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules:amd64 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-lowlatency 5.0.8 Uname: Linux 5.0.0-20-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 15:07:52 2019 InstallationDate: Installed on 2016-10-25 (1000 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pam UpgradeStatus: Upgraded to disco on 2019-07-19 (3 days ago) ** Affects: pam (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1837580 Title: memlock is not set Status in pam package in Ubuntu: New Bug description: I discovered this in relation to jack, which installs /etc/security/limits.d/audio.conf, containing: @audio - rtprio 95 @audio - memlockunlimited For a user in the audio group: $ulimit -l -r max locked memory (kbytes, -l) 65536 real-time priority (-r) 95 So jack (run as user via qjackctl) reports: ERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory) but does not report that it cannot set real-time priority, which it does if run by a user not in the audio group. I also tried putting the line in /etc/security/limits.conf, and trying a number rather than "unlimited", but it didn't help. Also reported independently here: https://askubuntu.com/questions/1142943/ulimit-unlimited-cannot-set ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libpam-modules:amd64 1.3.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-20.21-lowlatency 5.0.8 Uname: Linux 5.0.0-20-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jul 23 15:07:52 2019 InstallationDate: Installed on 2016-10-25 (1000 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: pam UpgradeStatus: Upgraded to disco on 2019-07-19 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1837580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume
Update: The HDMI audio device is missing even after screen off (screensaver). -- 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/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837173] Re: shall allow local save even it's neither ubuntu nor native.
I think the Device enablement team can add a new apport "symptoms" script to collect the debug messages of the OEM image, but not targeting a meta package which is not exist on Ubuntu archive. -- 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/1837173 Title: shall allow local save even it's neither ubuntu nor native. Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: Incomplete Bug description: For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is a local test one, it won't save the log. Let's skip package check if --save option is used. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1837173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837526] Re: Restarting services puts puppet into restart-loop
The attachment "Removes puppet from list of to-be-re-restarted services" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1837526 Title: Restarting services puts puppet into restart-loop Status in openssl package in Ubuntu: New Bug description: Puppet is a configuration and software management system that can be used e.g. for installing and upgrading debian packages, modifying configuration files, etc. Puppet will call apt-get/dpkg when needed to handle packages. When libssl1.1 is installed/upgraded and the installation process is controlled by Puppet, the automatic re-start of ssl-dependant services Puts puppet into a re-start loop: 1. libssl1.1 's postinstall script re-starts puppet via systemd (systemctl restart puppet.service) 2. systemd will terminate all processes associated with the Puppet service 3. dpkg is among these processes since it's called by Puppet and inherits its cgroup-memberships. 4. libssl1.1 's postinstall script will never succeed since it's killed by systemd 5. puppet re-starts 6. puppet runs "dpkg --configura -a" 7. libssl1.1 is unconfigured, the postinst script is run 8. goto 1. Puppet should be removed from hardcoded list of services to be re- started in libssl1.1's postinst script. A patch to do so is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1837526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
On further investigations I have found out that, despite of Network Manager setting up all the requested configurations correctly, sometimes the nmdev.get_ip6_config() in the check_connected_device_config() function in nm.py stays empty (but does not stay None) letting the initial test pass and the check for the IP addresses fail. We do not have a type too slow reaction here which could get worked around/fixed by adding a longer delay or making timeouts longer, the structure stays empty even after several minutes. The request for this structure seems not to cause any interaction with network manager as the debug log which is shown on each failed test does not show entries at the time of calling the get_ip6_config() method. Skipping the check_connected_device_config() call makes the remaining tests of the configuration/connection being done and they all pass safely, especially also the check_low_level_config() call which actually confirms that the interface has gotten the correct IP addresses (check_connected_device_config() in the IPv6 case only checks for the minimum number of IPs though). So as a workaround (fix?) I have skipped the check_connected_device_config() function call now. This way all tests pass for me with the correct IP addresses confirmed. This I have done in the last commit in the merge request attached to this bug report. The others are general fixes/improvements on the nm.py script. ** Changed in: network-manager (Ubuntu) Status: In Progress => Fix Committed -- 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/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: Fix Committed Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694554] Re: package python-crcmod 1.7-1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
The relevant traceback: Traceback (most recent call last): File "/usr/bin/pycompile", line 35, in from debpython.version import SUPPORTED, debsorted, vrepr, \ File "/usr/share/python/debpython/version.py", line 24, in from ConfigParser import SafeConfigParser ImportError: No module named 'ConfigParser' Assigning to python-defaults, because this ships /usr/share/python/debpython/version.py ** Package changed: python-crcmod (Ubuntu) => python-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1694554 Title: package python-crcmod 1.7-1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました Status in python-defaults package in Ubuntu: New Bug description: Google cloud SDK could not installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-crcmod 1.7-1 ProcVersionSignature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: python-crcmod: Install google-cloud-sdk: Install python-crcmod: Configure google-cloud-sdk: Configure Architecture: amd64 Date: Wed May 31 07:37:41 2017 DuplicateSignature: package:python-crcmod:1.7-1:サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました InstallationDate: Installed on 2017-04-12 (48 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-crcmod Title: package python-crcmod 1.7-1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1694554/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1694554] [NEW] package python-crcmod 1.7-1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました
You have been subscribed to a public bug: Google cloud SDK could not installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-crcmod 1.7-1 ProcVersionSignature: Ubuntu 4.4.0-75.96~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.23 AptOrdering: python-crcmod: Install google-cloud-sdk: Install python-crcmod: Configure google-cloud-sdk: Configure Architecture: amd64 Date: Wed May 31 07:37:41 2017 DuplicateSignature: package:python-crcmod:1.7-1:サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました ErrorMessage: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました InstallationDate: Installed on 2017-04-12 (48 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.17 SourcePackage: python-crcmod Title: package python-crcmod 1.7-1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-defaults (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- package python-crcmod 1.7-1 failed to install/upgrade: サブプロセス インストール済みの post-installation スクリプト はエラー終了ステータス 1 を返しました https://bugs.launchpad.net/bugs/1694554 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-defaults in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1836209] Re: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9
** Merge proposal linked: https://code.launchpad.net/~till-kamppeter/network-manager/+git/network-manager/+merge/369586 -- 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/1836209 Title: network-manager 1.18.0-1ubuntu5 ADT test failure with linux 5.2.0-8.9 Status in network-manager package in Ubuntu: In Progress Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/n/network-manager/20190710_160945_9116e@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20190710_110735_e5ce3@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1836209/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837537] [NEW] FTBFS since lxc has different version numbers in Debian and Ubuntu
Public bug reported: The lua-lxc [1] package currently fails to build since it cannot satisfy the build dependency: lxc-dev (>= 1:3.0.2-1~exp+1). Looks like this is caused by different version numbers in Debian and Ubuntu. The latest version in Debian unstable is 1:3.1.0+really3.0.3-8 while Ubuntu eoan has 3.0.3-0ubuntu1. I believe the 1: epoch (?) is causing this issue. Presumably lua-lxc needs to be patched to allow the Ubuntu package to fulfill the build requirements. [1] https://bugs.launchpad.net/ubuntu/+source/lua-lxc/1:3.0.2-1 [2] https://bugs.launchpad.net/ubuntu/+source/lua-lxc/1:3.0.2-1/+build/16664061 ** Affects: lua-lxc (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ftbfs ** Tags added: eoan ftbfs ** Also affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1837537 Title: FTBFS since lxc has different version numbers in Debian and Ubuntu Status in lua-lxc package in Ubuntu: New Status in lxc package in Ubuntu: New Bug description: The lua-lxc [1] package currently fails to build since it cannot satisfy the build dependency: lxc-dev (>= 1:3.0.2-1~exp+1). Looks like this is caused by different version numbers in Debian and Ubuntu. The latest version in Debian unstable is 1:3.1.0+really3.0.3-8 while Ubuntu eoan has 3.0.3-0ubuntu1. I believe the 1: epoch (?) is causing this issue. Presumably lua-lxc needs to be patched to allow the Ubuntu package to fulfill the build requirements. [1] https://bugs.launchpad.net/ubuntu/+source/lua-lxc/1:3.0.2-1 [2] https://bugs.launchpad.net/ubuntu/+source/lua-lxc/1:3.0.2-1/+build/16664061 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua-lxc/+bug/1837537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792579] Re: Network Disconnecting Intermittantly
Please provide us with logs of Network Manager in debug mode. See https://wiki.ubuntu.com/DebuggingNetworkManager for instructions. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1792579 Title: Network Disconnecting Intermittantly Status in network-manager package in Ubuntu: Incomplete Bug description: On my machine (OPTIPLEX GX620, Xubuntu 18.04 LTS) my wired (Ethernet) connection disconnects randomly. Everything was fine before the upgrade from Xenial LTS. It's not yet reproducible (by me). There are no error messages associated with it, the indicator plugin doesn't turn grey, and I've noticed no pattern to when it occurs. The only way I know it is has occurred is when something that uses the (Samba) network times out or stops doing anything. If I click the indicator plugin and select "wired connection 1", it reconnects immediately, But at some later time the same thing may happen again; it could be after a few minutes or many hours. This happens on another, the AMD machine I use as a file server, too, so it looks like a bug in Bionic Beaver, not a software package. lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 I suppose the bug could have something to do with the compatibility of Samba and 18.04 LTS, because after the upgrade, everything in /etc/fstab that used the credentials option stopped working, but that's part of another bug already reported by others but not yet solved. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1792579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Disco: Fix Committed Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] No, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837235] Re: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage)
** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1837235 Title: systemd 229-4ubuntu21.22 ADT test failure with linux 4.4.0-156.183 (storage) Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Fix Committed Status in systemd source package in Xenial: New Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: New Status in linux source package in Disco: Invalid Status in systemd source package in Disco: New Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: New Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/s/systemd/20190719_14_3528c@/log.gz The storage testcase is failing on i386. Running the testcase manually, it hangs at: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk testcrypt1! Looking at the storage testcase, on function start_password_agent(), it expects the 'disk scsi_debug' string on the systemd ask-password file, however the contains: Message=Please enter passphrase for disk testcrypt1! That doesn't seems to happen on other architectures. On amd64, the testcase output is: systemd-229/debian/tests$ sudo ./storage test_luks_by_devname (__main__.CryptsetupTest) LUKS device by plain device name, empty ... Please enter passphrase for disk scsi_debug (testcrypt1)! ok [...] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837526] [NEW] Restarting services puts puppet into restart-loop
Public bug reported: Puppet is a configuration and software management system that can be used e.g. for installing and upgrading debian packages, modifying configuration files, etc. Puppet will call apt-get/dpkg when needed to handle packages. When libssl1.1 is installed/upgraded and the installation process is controlled by Puppet, the automatic re-start of ssl-dependant services Puts puppet into a re-start loop: 1. libssl1.1 's postinstall script re-starts puppet via systemd (systemctl restart puppet.service) 2. systemd will terminate all processes associated with the Puppet service 3. dpkg is among these processes since it's called by Puppet and inherits its cgroup-memberships. 4. libssl1.1 's postinstall script will never succeed since it's killed by systemd 5. puppet re-starts 6. puppet runs "dpkg --configura -a" 7. libssl1.1 is unconfigured, the postinst script is run 8. goto 1. Puppet should be removed from hardcoded list of services to be re- started in libssl1.1's postinst script. A patch to do so is attached. ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: bionic xenial ** Attachment added: "Removes puppet from list of to-be-re-restarted services" https://bugs.launchpad.net/bugs/1837526/+attachment/5278651/+files/libssl.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1837526 Title: Restarting services puts puppet into restart-loop Status in openssl package in Ubuntu: New Bug description: Puppet is a configuration and software management system that can be used e.g. for installing and upgrading debian packages, modifying configuration files, etc. Puppet will call apt-get/dpkg when needed to handle packages. When libssl1.1 is installed/upgraded and the installation process is controlled by Puppet, the automatic re-start of ssl-dependant services Puts puppet into a re-start loop: 1. libssl1.1 's postinstall script re-starts puppet via systemd (systemctl restart puppet.service) 2. systemd will terminate all processes associated with the Puppet service 3. dpkg is among these processes since it's called by Puppet and inherits its cgroup-memberships. 4. libssl1.1 's postinstall script will never succeed since it's killed by systemd 5. puppet re-starts 6. puppet runs "dpkg --configura -a" 7. libssl1.1 is unconfigured, the postinst script is run 8. goto 1. Puppet should be removed from hardcoded list of services to be re- started in libssl1.1's postinst script. A patch to do so is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1837526/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785644] Re: Squared number (N^2) of copies printed
Good morning
We are experiencing on Ubuntu 18.04 with CUPS 2.2.7 this strange problem.
We use Ubuntu 18.04 clients to print to raw queues on a Ubuntu 18.04 server.
We do this for print accounting and control in our application.
We do many many tests, on Ubuntu 18.04, Kubuntu 18.04, Ubuntu 19.04, and
to finish, on Debian 9 (with CUPS 2.2.1)
For our testing, we create a printer called MYREMOTEPRINTER .
This is the name of the raw queue on server and, to keep it simple, the name of
the printer for the clients.
Each time we print a document (from Firefox, evince, and many others
applications), asking 2 ou more copies, we get 2^2, or 3^3 and so on copies.
Same behaviour if we print from command line ("lp -d MYREMOTEPRINTER -n 2
MyDocument.PDF").
A document of 3 pages, 2 copies, will generate 3 * 2^2 pages = 12 pages instead
of 6.
And if you want to print just a unique page, 10 copies, you will get 100 pages !
This problem did not exist on Ubuntu 14.04 with CUPS 1.7.2
The same problem has been opened (and closed, without any explanations) on
GitHub here :
https://github.com/apple/cups/issues/5015
(were I posted too this comment)
We discovered also that if we declare the remote printer as :
lpd://REMOTESERVER/MYREMOTEPRINTER
instead of
ipp://REMOTESERVER/printers/MYREMOTEPRINTER
(and declare cups-ldp in inetd.conf, of course) problem is not present.
This doesn't seem just an Ubuntu bug (Debian has same problem), but if
it is a CUPS problem, I don't understand why it has been closed by its
developer.
Do you think this bug could be solved in current Ubuntu 18.04 LTS ?
Best regards
Marco
** Bug watch added: github.com/apple/cups/issues #5015
https://github.com/apple/cups/issues/5015
--
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/1785644
Title:
Squared number (N^2) of copies printed
Status in cups package in Ubuntu:
Confirmed
Bug description:
I wanted to print 4 copies of a 3-pages document (12 pages total) and
instead 16 copies (48 pages) were printed.
Using latest Ubuntu with all updates, Gnome Shell on Xorg, I opened a
PDF file in Evince 3.28.2-1, clicked "Print", clicked "+" button
several times to increase the number of copies to 4, and sent it
printing on Xerox_AltaLink_C8030. That network printer was previously
auto-detected with default drivers.
access_log only has one line at that time:
localhost - - [06/Aug/2018:16:28:14 +0200] "POST
/printers/Xerox_AltaLink_C8030 HTTP/1.1" 200 64269 Print-Job successful-ok
error_log doesn’t have anything related.
I am attaching the print job captured per
https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data
On the cups page with completed jobs
http://localhost:631/printers/Xerox_AltaLink_C8030?which_jobs=completed
the amount of pages is shown as "48".
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 6 16:12:58 2018
InstallationDate: Installed on 2018-05-02 (96 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat:
device for Lexmark_M3150_10_: ipp://ET0021B7C1D744.local:631/ipp/print
device for WorkCentre-7120: socket://10.2.20.114
device for Xerox_AltaLink_C8030: ipp://XRX9C934E98F100.local:631/ipp/print
device for Xerox_VersaLink_C505_8c_ab_2c_4_:
ipps://XC8cab2c.local:631/ipp/print
device for Xerox_VersaLink_C505_8c_ab_50_7_:
ipps://XC8cab50.local:631/ipp/print
MachineType: Dell Inc. OptiPlex 7020
Papersize: a4
PpdFiles:
Error: command ['fgrep', '-H', '*NickName',
'/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd',
'/etc/cups/ppd/Xerox_AltaLink_C8030.ppd',
'/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd',
'/etc/cups/ppd/WorkCentre-7120.ppd', '/etc/cups/ppd/Lexmark_M3150_10_.ppd']
failed with exit code 2: grep:
/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd: Permission denied
Xerox_AltaLink_C8030: AltaLink C8030
grep: /etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd: Permission denied
grep: /etc/cups/ppd/WorkCentre-7120.ppd: Permission denied
grep: /etc/cups/ppd/Lexmark_M3150_10_.ppd: Permission denied
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/usr/bin/fish
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=3fd92192-fa04-40ea-ac71-f1dff8e153f7 ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/25/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 02YYK5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
[Touch-packages] [Bug 1785644] Re: Squared number (N^2) of copies printed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1785644 Title: Squared number (N^2) of copies printed Status in cups package in Ubuntu: Confirmed Bug description: I wanted to print 4 copies of a 3-pages document (12 pages total) and instead 16 copies (48 pages) were printed. Using latest Ubuntu with all updates, Gnome Shell on Xorg, I opened a PDF file in Evince 3.28.2-1, clicked "Print", clicked "+" button several times to increase the number of copies to 4, and sent it printing on Xerox_AltaLink_C8030. That network printer was previously auto-detected with default drivers. access_log only has one line at that time: localhost - - [06/Aug/2018:16:28:14 +0200] "POST /printers/Xerox_AltaLink_C8030 HTTP/1.1" 200 64269 Print-Job successful-ok error_log doesn’t have anything related. I am attaching the print job captured per https://wiki.ubuntu.com/DebuggingPrintingProblems#Capturing_print_job_data On the cups page with completed jobs http://localhost:631/printers/Xerox_AltaLink_C8030?which_jobs=completed the amount of pages is shown as "48". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Aug 6 16:12:58 2018 InstallationDate: Installed on 2018-05-02 (96 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for Lexmark_M3150_10_: ipp://ET0021B7C1D744.local:631/ipp/print device for WorkCentre-7120: socket://10.2.20.114 device for Xerox_AltaLink_C8030: ipp://XRX9C934E98F100.local:631/ipp/print device for Xerox_VersaLink_C505_8c_ab_2c_4_: ipps://XC8cab2c.local:631/ipp/print device for Xerox_VersaLink_C505_8c_ab_50_7_: ipps://XC8cab50.local:631/ipp/print MachineType: Dell Inc. OptiPlex 7020 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd', '/etc/cups/ppd/Xerox_AltaLink_C8030.ppd', '/etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd', '/etc/cups/ppd/WorkCentre-7120.ppd', '/etc/cups/ppd/Lexmark_M3150_10_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_50_7_.ppd: Permission denied Xerox_AltaLink_C8030: AltaLink C8030 grep: /etc/cups/ppd/Xerox_VersaLink_C505_8c_ab_2c_4_.ppd: Permission denied grep: /etc/cups/ppd/WorkCentre-7120.ppd: Permission denied grep: /etc/cups/ppd/Lexmark_M3150_10_.ppd: Permission denied ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/fish ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=3fd92192-fa04-40ea-ac71-f1dff8e153f7 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 02YYK5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd04/25/2014:svnDellInc.:pnOptiPlex7020:pvr01:rvnDellInc.:rn02YYK5:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 7020 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1785644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
if you can't get it to work with the backport stack from 19.04, then I don't know what else could help -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1
also, sounds like you didn't test 19.04 yourself? It's very much tied to radeon hw, so you really should test disco.. -- 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/1837170 Title: Kodi package crash after the update of libdrm-amdgpu1 Status in libdrm package in Ubuntu: Incomplete Bug description: Greetings, The last update of libdrm-amdgpu1 caused a bug on Kodi package, making it to crash after loading any video or reproduce a black image. Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium * Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111) -- Timo Aaltonen Wed, 10 Apr 2019 13:54:06 +0300 Kodi gives this error: #3 0x7f47676c60aa in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f47676c5dd7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Repeated several times #3 0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 #4 0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1 Team-Kodi stated these errors are in relation to 'Not supported GPU drivers', when Kodi can't find these files. I've found the cause, and a temporary solution: This bug was caused after an update for the latest version of libdrm- amdgpu1 2.4.97-1ubuntu1~18.04.1 So I grabbed the previous version from https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/ installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb and now Kodi returns. I created a bug report, the problem affects multiple users. https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828 We have a PointRelease coming soon, would we have time to fix this package? Thank you for your assistance. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1837170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
