[Touch-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Package changed: alsa-driver (Ubuntu) => ubuntu -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: irina 818 F pulseaudio /dev/snd/controlC0: irina 818 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 4 01:22:54 2019 InstallationDate: Installed on 2019-02-12 (233 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64
[Touch-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Confirmed Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: irina 818 F pulseaudio /dev/snd/controlC0: irina 818 F pulseaudio CurrentDesktop: GNOME Date: Fri Oct 4 01:22:54 2019 InstallationDate: Installed on 2019-02-
[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
** Tags added: regression-release -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850173] Re: HDMI output selected when it isn't plugged in
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1847570, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1847570 PulseAudio automatically switches to HDMI sound output on login -- 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/1850173 Title: HDMI output selected when it isn't plugged in Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this sometimes. I'm not sure what the pattern is. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
Just to confirm, on the login screen please try both 'Ubuntu' and 'Ubuntu on Wayland'. Do they both have the same bug? -- 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/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
Yeah the shortcuts appear to be correct in a fresh installation. ** Summary changed: - Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work + Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity ** Changed in: gsettings-desktop-schemas (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1849950 Title: Gnome Shell window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work if upgrading from Unity Status in GNOME Shell: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797872] Re: ntpd keeps Soliciting pool server
Same problem on my PC running: Linux Mint 19.2 Mate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1797872 Title: ntpd keeps Soliciting pool server Status in ntp package in Ubuntu: Confirmed Bug description: ntpd keeps printing "Soliciting pool server" in the syslog (once every 5 seconds). $ ntpq -c pe remote refid st t when poll reach delay offset jitter == 0.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 1.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 2.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 3.ubuntu.pool.n .POOL. 16 p- 6400.0000.000 0.000 ntp.ubuntu.com .POOL. 16 p- 6400.0000.000 0.000 $ sudo ntpq -c rv associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart, version="ntpd 4.2.8p4@1.3265-o Fri Jul 6 20:10:51 UTC 2018 (1)", processor="x86_64", system="Linux/4.15.0-33-generic", leap=11, stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT, reftime=. Thu, Feb 7 2036 6:28:16.000, clock=df6ee808.934d239d Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3, mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00, clk_jitter=0.000, clk_wander=0.000 I have changed nothing in the default configuration of ntp or the firewall. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Mon Oct 15 11:17:45 2018 InstallationDate: Installed on 2018-04-20 (177 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1839533] Re: .whl/.egg support in lesspipe is undocumented
This bug was fixed in the package less - 551-1 --- less (551-1) sid; urgency=low * many thanks to Anibal Monsalve Salazar for a decade worth of contributions to this package * new maintainer (closes: #925018) * new upstream release (closes: #925008, #892879, #178276, #473227, #922185, #839103, #626348, #330241, #914197, #707824) - don't count lines in initial screen if using -X with -F (closes: #906261) - update unicode tables to 2017-03-08 (closes: #597918, #881350) - mark truncated lines with a special character (closes: #547257) * set standards version to 4.4.0 * set debhelper compatibility to 12 * build depend on libncurses-dev * add VCS repository URLs * gbp import pristine-tar * move binaries back to /usr/bin (closes: #500092) * update less-is-more patch * update lesspipe man page (lp: #1839533) -- Milan Kupcevic Sat, 14 Sep 2019 22:28:16 -0400 ** Changed in: less (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1839533 Title: .whl/.egg support in lesspipe is undocumented Status in less package in Ubuntu: Fix Released Bug description: Support for .whl/.egg files (used in Python packaging) was added to lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page was apparently not updated at the time, and does not currenly list .whl/.egg as supported file types. This looks like a Debian bug, since the manual page was apparently written for Debian, but reportbug complains at me when I try to use it to submit a bug to the Debian BTS, so hopefully someone who knows what they're doing can report this upstream. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862048 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: i3 Date: Thu Aug 8 20:07:51 2019 Dependencies: debianutils 4.8.4 gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (360 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1839533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
No worries about my previous comment, it is solved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
Joe_Bishop, a new Bionic SRU for bug 1754671 got issued, now much less invasive simply backporting the fixes and not being a full upstream update. Please follow the instructions in bug 1754671. If you are still running 1.10.14 (the old SRU) please downgrade to the old network- manager and then do the updsate to get the new SRU. Please check and report here whether the regressions you observed in 1.10.14 do not occur in the new SRU. Thanks. ** Changed in: network-manager (Ubuntu) Status: Expired => 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/1829913 Title: openconnect VPN is not propagating internal DNS anymore Status in network-manager package in Ubuntu: Incomplete Bug description: Openconnect VPN stopped propagating DNSes to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
Jean, a new Bionic SRU for bug 1754671 got issued, now much less invasive simply backporting the fixes and not being a full upstream update. Please follow the instructions in bug 1754671. If you are still running 1.10.14 (the old SRU) please downgrade to the old network- manager and then do the updsate to get the new SRU. Please check and report here whether the regressions you observed in 1.10.14 do not occur in the new SRU. Thanks. -- 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/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression
Now network-manager is hanging on (all autopkg tests passed): Not touching package due to block request by freeze (contact #ubuntu- release if update is needed) Which freeze do we currently have on Bionic? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849641] Re: New upstream release: bluez 5.51
** Changed in: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1849641 Title: New upstream release: bluez 5.51 Status in bluez package in Ubuntu: Fix Committed Bug description: New upstream release: bluez 5.51 http://www.bluez.org/release-of-bluez-5-51/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849641/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850173] Re: HDMI output selected when it isn't plugged in
** Description changed: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have - to repeat this after suspend/resume. + to repeat this sometimes. I'm not sure what the pattern is. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: - TERM=tmux-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=tmux-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 -- 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/1850173 Title: HDMI output selected when it isn't plugged in Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this sometimes. I'm not sure what the pattern is. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
Ubuntu kernel team: In the kernel package for Ubuntu, CONFIG_SND_SOC_SOF_INTEL_TOPLEVEL (introduced in 5.2-rc1) needs to be changed from 'Y' back to its default value of 'N'. As described by Intel, this option cannot currently be set together with CONFIG_SND_SOC_INTEL_SST_TOPLEVEL. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1846539 Title: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID AC
[Touch-packages] [Bug 1588562] Re: Please add ~/.local/bin to the default $PATH
Add the fix on post #15 to file .bash_profile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1588562 Title: Please add ~/.local/bin to the default $PATH Status in bash package in Ubuntu: Fix Released Status in bash source package in Xenial: Fix Released Status in bash package in Debian: Fix Released Bug description: Starting in Xenial, 'pip install' by default places executables into ~/.local/bin. This is the de-facto standard place to put per-user executables -- for example, Fedora/Redhat puts it on the $PATH by default, and PEP 370 makes it the standard place for unprivileged installs of Python packages to put their scripts. But unfortunately, Ubuntu's does *not* add this directory to $PATH by default, which means that 'pip install' doesn't actually work -- any scripts that are installed are inaccessible, and every user has to manually add this to their PATH. Ubuntu should put ~/.local/bin onto PATH by default. Minor details (discussed with @doko at the PyCon sprints): - this should go at the beginning of PATH rather than the end, in accordance with Debian policy saying that more-local paths go before more-upstream paths. (This is inconsistent with how Fedora/RH do it, but consistent with how Python itself searches for packages.) - this will be added to /etc/skel/profile, so that it won't change any existing user accounts; it will only be applied to user accounts created *after* this change lands - unlike ~/bin (which Debian/Ubuntu have supported for ages), it will be added to PATH unconditionally, even if the directory doesn't exist. This is important to avoid a nasty trap for new users, where the first time they try to install a Python package they have to restart their shell. Since this only applies to new accounts, the directory will always start out nonexistent/empty, so having it in $PATH won't cause any unexpected changes in behavior. - possibly it would make sense to set this in /etc/environment or /etc/skel/.gnomerc or similar, so that it would also apply to non-shell processes (e.g. if the user wants to add a global key-binding to launch a Python program, then generally ~/.profile *doesn't* affect the environment where this command gets executed, and that can frustrate and confuse users if a command works fine from the terminal but not from a keybinding). But we should defer this discussion for the future, because even if this is a good idea, it isn't a good idea in a Xenial stable update. Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820856 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1588562/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
@Balint, after further testing, here's where things are: - On LXD Containers - On Bionic 1) First boot: neither interface mtu, nor ipv6 mtu is applied. 2) Restarting systemd-networkd: neither interface nor ipv6-mtu is applied 3) netplan apply: interface mtu is set correctly, ipv6 mtu is not. On Disco 1) First boot: neither interface mtu, nor ipv6 mtu is applied. 2) Restarting systemd-networkd: neither interface nor ipv6-mtu is applied 3) netplan apply: both interface and ipv6 MTU are set correctly. On Eoan 1) First boot: neither interface mtu, nor ipv6 mtu is applied 2) Restarting systemd-networkd: neither interface nor ipv6-mtu is applied 3) netplan apply: both interface and ipv6 MTU are set correctly. -- On VMs -- On Bionic 1) First boot: interface MTU is set, ipv6 MTU is not applied. 2) Restarting systemd-networkd: both interface and ipv6 MTU are set correctly 3) netplan apply not needed 4) After reboot, same as (1) On Disco 1) First boot: interface MTU is set, ipv6 MTU is not applied. 2) Restarting systemd-networkd: both interface and ipv6 MTU are set correctly 3) netplan apply not needed 4) After reboot, same as (1) On Eoan 1) First boot: interface MTU is set, ipv6 MTU is not applied. 2) Restarting systemd-networkd: both interface and ipv6 MTU are set correctly 3) netplan apply not needed 4) After reboot, same as (1) -- 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: Triaged Status in cloud-init source package in Disco: New Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Triaged Bug description: = netplan.io = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Apply a netplan configuration that specifices ipv6-mtu: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: true ipv6-mtu: 6000 * Check that MTU bytes, is at least IPv6MTUBytes on the interface: $ sysctl net.ipv6.conf.eth0.mtu net.ipv6.conf.eth0.mtu = 6000 [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of netplan.io = = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be
[Touch-packages] [Bug 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
** Changed in: gnome-shell Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work Status in GNOME Shell: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849950] Re: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work
The GNOME guys seem to have decided that this is not caused by them and closed the issue. I think that they are probably right, although I don't have any proof for that. As I said I suspect maybe some transition between Unity and GNOME. Although this is then resided in rather old code for the Upgrade, it still seems relevant, since many users might be affected. I think I am affected on both machines I have running. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1849950 Title: Window shortcuts maximize, windowed and hide (Super + Up / Down / H) don't work Status in GNOME Shell: Fix Released Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: Happens on Ubuntu 19.10, and did also not work on Ubuntu 19.04 (and probably also previous versions), if I recall correctly. I am not sure, whether this is an upstream bug of GNOME or just Ubuntu related. Bug report for GNOME: https://gitlab.gnome.org/GNOME/gnome- shell/issues/1829 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849950/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates
Well yes, ESM packages are not included in upgradable if ESM is disabled. It only shows packages that would/should be upgraded if you run dist-upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Incomplete Bug description: Running `apt list --upgradable` does not show any additional packages to install. Should it? root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60 additional updates are available with UA Infrastructure ESM. To see these additional updates run: apt list --upgradable See https://ubuntu.com/advantage or run: sudo ua status root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable Listing... Done root@humble-mynah:/etc/apt/sources.list.d# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850173] [NEW] HDMI output selected when it isn't plugged in
Public bug reported: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this after suspend/resume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1850173 Title: HDMI output selected when it isn't plugged in Status in pulseaudio package in Ubuntu: New Bug description: Pulseaudio has started preferring the "HDMI / Displayport" sink instead of the USB audio device I have speakers connected to. I'm pretty sure this behavior change coincided with upgrading from Ubuntu 19.04 to 19.10. I've tried using set-default-sink in default.pa, but it doesn't seem to have any effect. The "Set as fallback" buttons in pavucontrol seem to fix it, but I have to repeat this after suspend/resume. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20+kai1-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:15:07 2019 InstallationDate: Installed on 2019-06-18 (132 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to eoan on 2019-10-23 (5 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.60 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.60:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2019-10-25T21:49:15.001833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1850173/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates
@andreas: Yes, I'm using: ii apt 1.0.1ubuntu2.24 amd64 commandline package manager -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Incomplete Bug description: Running `apt list --upgradable` does not show any additional packages to install. Should it? root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60 additional updates are available with UA Infrastructure ESM. To see these additional updates run: apt list --upgradable See https://ubuntu.com/advantage or run: sudo ua status root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable Listing... Done root@humble-mynah:/etc/apt/sources.list.d# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates
Hmm I was able to reproduce even having 1.0.1ubuntu2.24; adding apt as a affects as well. ** Also affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Incomplete Bug description: Running `apt list --upgradable` does not show any additional packages to install. Should it? root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60 additional updates are available with UA Infrastructure ESM. To see these additional updates run: apt list --upgradable See https://ubuntu.com/advantage or run: sudo ua status root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable Listing... Done root@humble-mynah:/etc/apt/sources.list.d# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849972] Re: apt list --upgradable shows no additional updates
This is how I am reproducing: multipass launch trusty --name t1 multipass exec t1 bash echo "deb http://archive.ubuntu.com/ubuntu trusty-proposed main" | tee -a /etc/apt/sources.list sudo apt update -qq sudo apt upgrade -y sudo apt list --upgradable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1849972 Title: apt list --upgradable shows no additional updates Status in apt package in Ubuntu: New Status in ubuntu-advantage-tools package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: Incomplete Bug description: Running `apt list --upgradable` does not show any additional packages to install. Should it? root@humble-mynah:/etc/apt/sources.list.d# apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 60 additional updates are available with UA Infrastructure ESM. To see these additional updates run: apt list --upgradable See https://ubuntu.com/advantage or run: sudo ua status root@humble-mynah:/etc/apt/sources.list.d# apt list --upgradable Listing... Done root@humble-mynah:/etc/apt/sources.list.d# To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1849972/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850165] [NEW] Linux console runs off the bottom of the display
Public bug reported: When switching from X to the Linux framebuffer console using ctrl- alt-f3, the bottom lines of the console text run off the bottom of the display ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:04:26 2019 InstallationDate: Installed on 2019-03-25 (216 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to eoan on 2019-10-23 (4 days ago) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1850165 Title: Linux console runs off the bottom of the display Status in console-setup package in Ubuntu: New Bug description: When switching from X to the Linux framebuffer console using ctrl- alt-f3, the bottom lines of the console text run off the bottom of the display ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: console-setup 1.191ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 11:04:26 2019 InstallationDate: Installed on 2019-03-25 (216 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: console-setup UpgradeStatus: Upgraded to eoan on 2019-10-23 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1850165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801540]
Confirming this for ALC887-VD Analog [ALC887-VD Analog] Audio device [0403]: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller [1022:780d] (rev 01) Crackling seems to only go away when mix is set to lower than 10% in pulseaudio. If the device oversaturates it seems to try to lower the volume and starts to crackle for a while making it unusable to record or talk for a long time. This has been around for a long time now. It seems there is already a patch but im kinda worried by the version number. 5.3.x seems pretty far away from stable releases(5.0.0-27-generic)? -- 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/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()
** Changed in: mesa (Ubuntu Eoan) Status: Triaged => Won't Fix -- 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/1815889 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() Status in Mesa: Won't Fix Status in QEMU: Fix Released Status in mesa package in Ubuntu: In Progress Status in qemu package in Ubuntu: Invalid Status in mesa source package in Disco: Fix Released Status in mesa source package in Eoan: Won't Fix Status in qemu source package in Eoan: Fix Released Bug description: Unable to launch Default Fedora 29 images in gnome-boxes ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 Date: Thu Feb 14 11:00:45 2019 ExecutablePath: /usr/bin/qemu-system-x86_64 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND MachineType: Dell Inc. Precision T3610 ProcEnviron: PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1 Signal: 31 SourcePackage: qemu StacktraceTop: __pthread_setaffinity_new (th=, cpusetsize=128, cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34 () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so start_thread (arg=) at pthread_create.c:486 clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Title: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new() UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video dmi.bios.date: 11/14/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A18 dmi.board.name: 09M8Y8 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision T3610 dmi.product.sku: 05D2 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715931] Re: Update to exiv2 version 0.27
** Tags removed: version-blocked-ff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.27 Status in exiv2 package in Ubuntu: Triaged Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797064] Re: Update to 2.9.8
** Summary changed: - Update to 2.9.8 not this cycle + Update to 2.9.8 ** Tags removed: version-blocked-ff ** Description changed: - The new version is in Debian experimental but it's late to update on - Ubuntu this cycle, especially with a non trivial update on a component - like that, the update is for next cycle + The new version is in Debian experimental only, why? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1797064 Title: Update to 2.9.8 Status in libxml2 package in Ubuntu: Triaged Bug description: The new version is in Debian experimental only, why? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1797064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841113] Re: Update to 2.13.92
** Summary changed: - Don't update to 2.13.92 this cycle + Update to 2.13.92 ** Tags removed: version-blocked-ff ** Description changed: - The new version has non trivial changes and needs proper testing, also - it's not clear there is going to be a stable version before eoan is out, - that update is for next cycle + The new version has non trivial changes and needs proper testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1841113 Title: Update to 2.13.92 Status in fontconfig package in Ubuntu: Triaged Bug description: The new version has non trivial changes and needs proper testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1841113/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841274] Re: update to 2.3.0
** Summary changed: - Don't update to 2.3.0 this cycle + update to 2.3.0 ** Tags removed: version-blocked-ff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ilmbase in Ubuntu. https://bugs.launchpad.net/bugs/1841274 Title: update to 2.3.0 Status in ilmbase package in Ubuntu: Triaged Bug description: The new version includes a soname change and is still in experimental in Debian, no real reason to update now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ilmbase/+bug/1841274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841295] Re: Update to 2.3.0?
** Tags removed: version-blocked-ff -- 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/1841295 Title: Update to 2.3.0? Status in cups package in Ubuntu: Triaged Bug description: There is a new cups version out, likely not for this cycle though? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1841295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841276] Re: Update to 2.3
** Summary changed: - Don't merge with Debian 2.3.0-5 this cycle + Update to 2.3 ** Tags removed: version-blocked-ff ** Description changed: - The new version is in Debian experimental and requires a transition, not - this cycle + The new version is in Debian experimental and requires a transition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1841276 Title: Update to 2.3 Status in openexr package in Ubuntu: Triaged Bug description: The new version is in Debian experimental and requires a transition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1841276/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841296] Re: Update to 2.4.3
** Summary changed: - Update to 2.4.3 next cycle + Update to 2.4.3 ** Tags removed: version-blocked-ff ** Description changed: - The new version includes new features and since we are in feature freeze - now it's not for this cycle + The new version includes new features -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libshout in Ubuntu. https://bugs.launchpad.net/bugs/1841296 Title: Update to 2.4.3 Status in libshout package in Ubuntu: Triaged Status in libshout package in Debian: New Bug description: The new version includes new features To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libshout/+bug/1841296/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1842643] Re: Update to 1.44
** Summary changed: - Don't update to 1.44.6 this cycle + Update to 1.44 ** Tags removed: version-blocked-ff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: Update to 1.44 Status in pango1.0 package in Ubuntu: Triaged Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841783] Re: Update to 1.2.0?
** Summary changed: - Update to 1.2.0 not this cycle + Update to 1.2.0? ** Tags removed: version-blocked-ff ** Description changed: The source was split in rc2, Debian didn't follow the change and we are - in sync (also not the sort of changes we want to deal with after feature - freeze this cycle) + in sync, do we want to update? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1841783 Title: Update to 1.2.0? Status in speex package in Ubuntu: Triaged Bug description: The source was split in rc2, Debian didn't follow the change and we are in sync, do we want to update? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1841783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841785] Re: Update to 3.5.1 not this cycle
https://bugs.launchpad.net/ubuntu/+source/nettle/3.5.1+really3.5.1-2 ** Changed in: nettle (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nettle in Ubuntu. https://bugs.launchpad.net/bugs/1841785 Title: Update to 3.5.1 not this cycle Status in nettle package in Ubuntu: Fix Released Bug description: Debian did the update but it includes a soname change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1841785/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1841745] Re: Update to 1.2.0
** Summary changed: - Update to 1.2.0 not this cycle + Update to 1.2.0 ** Tags removed: version-blocked-ff ** Description changed: - The new version has non trivial change and is not in Debian/Fedora yet, - better to wait for next cycle at this point + The new version has non trivial change and is not in Debian/Fedora yet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxt in Ubuntu. https://bugs.launchpad.net/bugs/1841745 Title: Update to 1.2.0 Status in libxt package in Ubuntu: New Bug description: The new version has non trivial change and is not in Debian/Fedora yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1841745/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600]
it was in default desktop session when i freshly installed it. when i realized the problem, i decided to download gnome-vanilla-desktop with the hope that problem won't transfer in different desktop environment and only with no luck. i had been using 18.10 and 19.04 in the same device earlier where i did not have such issues regarding graphics transition. -- 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/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849878] Re: Debu1: SSH2_MSG_KEXINIT sent
Thank you for taking the time to report this bug and helping to make Ubuntu better. Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1849878 Title: Debu1: SSH2_MSG_KEXINIT sent Status in openssh package in Ubuntu: Incomplete Bug description: I try to make the connection with an NSA that lives on the same network of my Ubuntu 1804 server, however performing authentication via SSH hangs in Debu1: SSH2_MSG_KEXINIT sent. Tracked error: Conection closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1849878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849878] Re: Debu1: SSH2_MSG_KEXINIT sent
There isn't a lot of info on the bug to help, but it already seems to be a config issue. For those you are better with a community page like askubuntu.com as this is about fixing bugs in the package and not about guiding to a valid configuration. A search showed https://askubuntu.com/questions/60350/putty-works-but-ssh-from-terminal-fails-after-ssh2-msg-kexinit https://askubuntu.com/questions/344863/ssh-new-connection-begins-to-hang-not-reject-or-terminate-after-a-day-or-so-on https://stackoverflow.com/questions/2419412/ssh-connection-stop-at-debug1-ssh2-msg-kexinit-sent Maybe one of these can already help you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1849878 Title: Debu1: SSH2_MSG_KEXINIT sent Status in openssh package in Ubuntu: Incomplete Bug description: I try to make the connection with an NSA that lives on the same network of my Ubuntu 1804 server, however performing authentication via SSH hangs in Debu1: SSH2_MSG_KEXINIT sent. Tracked error: Conection closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1849878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed
** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1849156 Title: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed Status in ntp package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Status in ntp source package in Eoan: New Status in systemd source package in Eoan: New Bug description: Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd- timesyncd.service.d/disable-with-time-daemon.conf. This prevents systemd-timesyncd.service from starting if the ntp package has been installed. However, ntp.service has a Conflicts directive for systemd-timesyncd.service. If both services are enabled, neither will start on boot. This breaks upgrades from < 19.10 to 19.10 for systems that have both ntp and systemd installed. Possible workarounds: - Uninstall ntp - Disable systemd-timesyncd.service % lsb_release -rd Description:Ubuntu 19.10 Release:19.10 % apt-cache policy systemd systemd: Installed: 242-7ubuntu3 Candidate: 242-7ubuntu3 Version table: *** 242-7ubuntu3 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status % apt-cache policy ntp ntp: Installed: 1:4.2.8p12+dfsg-3ubuntu2 Candidate: 1:4.2.8p12+dfsg-3ubuntu2 Version table: *** 1:4.2.8p12+dfsg-3ubuntu2 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status % dpkg -S /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf systemd: /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf % sudo systemctl status ntp ● ntp.service - Network Time Service Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:ntpd(8) % sudo systemctl status systemd-timesyncd.service ● systemd-timesyncd.service - Network Time Synchronization Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-timesyncd.service.d └─disable-with-time-daemon.conf Active: inactive (dead) Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago Docs: man:systemd-timesyncd.service(8) Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1849156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850122] Re: ubuntu-bug lightdm no password box
** Project changed: launchpad => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1850122 Title: ubuntu-bug lightdm no password box Status in lightdm package in Ubuntu: New Bug description: As explained in this topic https://discourse.ubuntubudgie.org/t/updated-to-19-10-lock-screen- problem/2597 The PC after waking up from sleep there is no password box in the screen to resume work. So far this problem is seen in Ubuntu Budgie and Solus Budgie. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1850122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843743] Re: klibc ftbfs in eoan
This bug was fixed in the package klibc - 2.0.6-1ubuntu2 --- klibc (2.0.6-1ubuntu2) eoan; urgency=medium * Fix FTBFS on eoan and later with new linux and gcc (LP: #1843743) - cf-protection.patch: Disable cf-protection for syscalls stub. - mman-include.patch: Adjust for changes to linux headers in 5.3. -- Adam Conrad Mon, 21 Oct 2019 15:39:37 -0600 ** Changed in: klibc (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Eoan: Fix Released Bug description: [ SRU Justification / Impact ] klibc is FTBFS in eoan. As we have a history of SRUing klibc to add new features, we should probably make sure it's buildable. [ Test Case ] If it builds, we win. Should also test that a machine with the new klibc installed still boots. [ Regression Potential ] One patch is just adding a missing include, and the other is altering the build of a stub only used to determine which syscalls are availble, a part of the build that will cause the rest of the build to fail if it's generated incorrectly. Regression potential should be very low. [ Original Bug Report ] https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU
@raharper, do I understand correctly that this occurs only on first boot and is fixed when installing eoan's netplan.io on bionic? Also a full Disco systemd works or not? (Disco system, Disco netplan.io, Disco 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/1671951 Title: networkd should allow configuring IPV6 MTU Status in cloud-init package in Ubuntu: Confirmed Status in netplan.io package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cloud-init source package in Bionic: Confirmed Status in netplan.io source package in Bionic: Fix Released Status in systemd source package in Bionic: Triaged Status in cloud-init source package in Disco: New Status in netplan.io source package in Disco: Fix Released Status in systemd source package in Disco: Triaged Bug description: = netplan.io = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Apply a netplan configuration that specifices ipv6-mtu: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: true ipv6-mtu: 6000 * Check that MTU bytes, is at least IPv6MTUBytes on the interface: $ sysctl net.ipv6.conf.eth0.mtu net.ipv6.conf.eth0.mtu = 6000 [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of netplan.io = = systemd = [Impact] * IPv6 traffic failing to send/receive due to incompatible/low MTU setting. Specifically, IPv6 traffic may have higher MTU requirements than IPv4 traffic and thus may need to be overridden and/or set to a higher value than IPv6 traffic. [Test Case] * Use IPv6MTUBytes= setting in a .network unit * Restart systemd-network * Check that there no error messages / warnings about not-recognizing this option * Check that MTU bytes, is at least IPv6MTUBytes on the interface [Regression Potential] * This is a future compatible backport of an additional keyword not used by default. It may result in MTU change to a higher value, which should not cause loss of connectivity. [Other Info] * Original bug report below = end of systemd = 1) Zesty 2) systemd-232-19 3) I need to configure the IPV6 MTU for tunneling by adding an IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 static address in the [Network] section 4) networkd does not parse or read the value and does not apply this configuration to the interface. Upstream has discussed this issue here: https://github.com/systemd/systemd/pull/1533 But it's been closed in favor of only setting via RA. However, we know of multiple use-case which are currently supported in ifdupdown where we want to retain control over IPV6 MTU values outside of PMTU Discovery configurations. Some context from those discussions >> Client systems that route their ipv6 packets to a 6in4 router also >> have to have their ipv6 mtu lowered. They could lower their link mtu, >> so their ipv6 packets are small enough, but that reduces performance >> of their ipv4 network. Yes. Anything that creates a PMTUD black hole can result in situations where the higher header overhead of IPv6 will cause IPv4 to pass but IPv6 traffic to be dropped. One example here is egress from an ipsec tunnel wherein the next hop MTU is too low for IPv6 datagrams to pass. Another is VM -> whatever -> host bridge -> tunnel ingress. If the datagram cannot enter the tunnel due to size, it is dropped, and an ICMP response uses the tunnel address as a source, which may not be routable back to the origin. This one is an issue with IPv4 as well, and is one case where manually setting the IPv6 MTU lower than the (also manually set) device MTU is of benefit. In essence, any of these sort of cases that require an explicit setting of the device MTU will likely require a setting of the IPv6 mtu as well to account for its larger header overhead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1843743] Update Released
The verification of the Stable Release Update for klibc has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to klibc in Ubuntu. https://bugs.launchpad.net/bugs/1843743 Title: klibc ftbfs in eoan Status in klibc package in Ubuntu: Fix Released Status in klibc source package in Eoan: Fix Committed Bug description: [ SRU Justification / Impact ] klibc is FTBFS in eoan. As we have a history of SRUing klibc to add new features, we should probably make sure it's buildable. [ Test Case ] If it builds, we win. Should also test that a machine with the new klibc installed still boots. [ Regression Potential ] One patch is just adding a missing include, and the other is altering the build of a stub only used to determine which syscalls are availble, a part of the build that will cause the rest of the build to fail if it's generated incorrectly. Regression potential should be very low. [ Original Bug Report ] https://launchpadlibrarian.net/441262209/buildlog_ubuntu-eoan-amd64.klibc_2.0.6-1ubuntu1_BUILDING.txt.gz gcc -Wp,-MD,usr/klibc/.sigsuspend.o.d -nostdinc -iwithprefix include -I/<>/usr/include/arch/x86_64 -Iusr/include/arch/x86_64 -I/<>/usr/include/bits64 -Iusr/include/bits64 -I/<>/usr/klibc/../include -Iusr/klibc/../include -I/<>/usr/include -Iusr/include -I/<>/linux/include -Ilinux/include -D__KLIBC__=2 -D__KLIBC_MINOR__=0 -D_BITSIZE=64 -fno-stack-protector -fwrapv -fno-PIE -ggdb -m64 -Os -fomit-frame-pointer -mno-sse -falign-functions=1 -falign-jumps=1 -falign-loops=1 -fno-asynchronous-unwind-tables -W -Wall -Wno-sign-compare -Wno-unused-parameter -c -o usr/klibc/sigsuspend.o usr/klibc/sigsuspend.c usr/klibc/sigsuspend.c:8:10: fatal error: klibc/havesyscall.h: No such file or directory 8 | #include | ^ compilation terminated. make[4]: *** [/<>/scripts/Kbuild.klibc:252: usr/klibc/sigsuspend.o] Error 1 make[3]: *** [/<>/./Kbuild:9: all] Error 2 make[2]: *** [Makefile:118: klibc] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1843743/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1848354] Re: upgrade-between-snapshots autopkgtest is flaky
Correct me if I'm wrong, but since this is only an autopkgtest mark-as- flaky change, it feels to me like something that doesn't necessarily needs to be released into -updates. Let us block it in -proposed until we have more to release. ** Tags added: block-proposed-bionic block-proposed-disco block- proposed-eoan block-proposed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1848354 Title: upgrade-between-snapshots autopkgtest is flaky Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Disco: Fix Committed Status in unattended-upgrades source package in Eoan: Fix Committed Bug description: [Impact] * Flaky upgrade-between-snapshots autopkgtest prevents developers to use the test efficiently. [Test Case] * Run autopkgtests, observe the upgrade-between-snapshots test passing or failing but being marked as FLAKY. [Regression Potential] * None, the test was failing often due to connectivity/internal errors of snapshot.debian.org. [Other Info] * The whole autopkgtest is marked to be failing on amd64 to mitigate the single flaky test, this marking can be removed after marking this single flaky test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850122] [NEW] ubuntu-bug lightdm no password box
You have been subscribed to a public bug: As explained in this topic https://discourse.ubuntubudgie.org/t/updated-to-19-10-lock-screen- problem/2597 The PC after waking up from sleep there is no password box in the screen to resume work. So far this problem is seen in Ubuntu Budgie and Solus Budgie. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New -- ubuntu-bug lightdm no password box https://bugs.launchpad.net/bugs/1850122 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm 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 1850127] Re: Unable to print with Brother printer since upgrade to Ubuntu 19.10
** Attachment added: "Output of "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r"" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1850127/+attachment/5300859/+files/avahi.txt -- 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/1850127 Title: Unable to print with Brother printer since upgrade to Ubuntu 19.10 Status in cups package in Ubuntu: New Bug description: I have recently bought a new color laser printer (Brother HL- L8260CDW), which is connected through wLAN. It works like a charm under Ubuntu 19.04, but refuses to print since the upgrade to stock Ubuntu 19.10. I can reach it via ping and through its HTTP config page from the same computer. During my collection of relevant bug information I discovered the following error messages: 1. Some print filter was unable to grep /etc/cups/ppd/Brother_HL_L8260CDW_series.ppd This file was rw for user "root" and r for group "lp", but not accessible to others. I have made it world readable for testing purposes, but I still can't print. 2. I checked /var/log/syslog for app-armour errors but found none which would be related to cups and/or printing 3. After fixing the permission issue, the new error message is "File \'\' not found" and "Unable to add document to print job.", both of which are too cryptic for me to dig further into this by myself. Attached to this bug report I send the following pieces of information: - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt) - output from "lpinfo -v" (lpinfo.txt) - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" (avahi.txt) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CupsErrorLog: E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job. E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 10:50:05 2019 InstallationDate: Installed on 2015-11-11 (1446 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Brother_HL_L8260CDW_series: implicitclass://Brother_HL_L8260CDW_series/ MachineType: MSI MS-7982 Papersize: a4 PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.10 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO-DH (MS-7982) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7982 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1850127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849856] Re: ip commands error with mellanox devices in switchdev mode
strace from failing command ** Attachment added: "strace-iplink.txt" https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+attachment/5300860/+files/strace-iplink.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1849856 Title: ip commands error with mellanox devices in switchdev mode Status in iproute2 package in Ubuntu: New Bug description: Kernel: using 5.0.0-23-generic from hwe-edge Configuring a mellanox connectx device with configured VF's into switchdev (rather than legacy) mode result in the ip cli tool erroring when trying to query the interface state: $ sudo ip link Error: Buffer too small for object. Dump terminated ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: iproute2 4.15.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Oct 25 14:55:36 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1849856/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850127] Re: Unable to print with Brother printer since upgrade to Ubuntu 19.10
** Attachment added: "Output of "lpinfo -v"" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1850127/+attachment/5300858/+files/lpinfo.txt -- 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/1850127 Title: Unable to print with Brother printer since upgrade to Ubuntu 19.10 Status in cups package in Ubuntu: New Bug description: I have recently bought a new color laser printer (Brother HL- L8260CDW), which is connected through wLAN. It works like a charm under Ubuntu 19.04, but refuses to print since the upgrade to stock Ubuntu 19.10. I can reach it via ping and through its HTTP config page from the same computer. During my collection of relevant bug information I discovered the following error messages: 1. Some print filter was unable to grep /etc/cups/ppd/Brother_HL_L8260CDW_series.ppd This file was rw for user "root" and r for group "lp", but not accessible to others. I have made it world readable for testing purposes, but I still can't print. 2. I checked /var/log/syslog for app-armour errors but found none which would be related to cups and/or printing 3. After fixing the permission issue, the new error message is "File \'\' not found" and "Unable to add document to print job.", both of which are too cryptic for me to dig further into this by myself. Attached to this bug report I send the following pieces of information: - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt) - output from "lpinfo -v" (lpinfo.txt) - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" (avahi.txt) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CupsErrorLog: E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job. E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 10:50:05 2019 InstallationDate: Installed on 2015-11-11 (1446 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Brother_HL_L8260CDW_series: implicitclass://Brother_HL_L8260CDW_series/ MachineType: MSI MS-7982 Papersize: a4 PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.10 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO-DH (MS-7982) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7982 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1850127/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850127] [NEW] Unable to print with Brother printer since upgrade to Ubuntu 19.10
Public bug reported: I have recently bought a new color laser printer (Brother HL-L8260CDW), which is connected through wLAN. It works like a charm under Ubuntu 19.04, but refuses to print since the upgrade to stock Ubuntu 19.10. I can reach it via ping and through its HTTP config page from the same computer. During my collection of relevant bug information I discovered the following error messages: 1. Some print filter was unable to grep /etc/cups/ppd/Brother_HL_L8260CDW_series.ppd This file was rw for user "root" and r for group "lp", but not accessible to others. I have made it world readable for testing purposes, but I still can't print. 2. I checked /var/log/syslog for app-armour errors but found none which would be related to cups and/or printing 3. After fixing the permission issue, the new error message is "File \'\' not found" and "Unable to add document to print job.", both of which are too cryptic for me to dig further into this by myself. Attached to this bug report I send the following pieces of information: - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt) - output from "lpinfo -v" (lpinfo.txt) - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" (avahi.txt) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CupsErrorLog: E [28/Oct/2019:10:40:04 +0100] [Job 112] File \'\' not found E [28/Oct/2019:10:40:12 +0100] [Job 112] Unable to add document to print job. E [28/Oct/2019:10:45:59 +0100] [Job 113] File \'\' not found CurrentDesktop: ubuntu:GNOME Date: Mon Oct 28 10:50:05 2019 InstallationDate: Installed on 2015-11-11 (1446 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lpstat: device for Brother_HL_L8260CDW_series: implicitclass://Brother_HL_L8260CDW_series/ MachineType: MSI MS-7982 Papersize: a4 PpdFiles: Brother_HL_L8260CDW_series: HL-L8260CDW series - IPP Everywhere ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=64458150-bde5-4ffc-8eb1-038fae855347 ro quiet splash SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.10 dmi.board.asset.tag: Default string dmi.board.name: B150M PRO-DH (MS-7982) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.10:bd07/08/2015:svnMSI:pnMS-7982:pvr1.0:rvnMSI:rnB150MPRO-DH(MS-7982):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7982 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "output of /usr/lib/cups/backend/snmp 10.0.0.14" https://bugs.launchpad.net/bugs/1850127/+attachment/5300844/+files/snmp.txt -- 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/1850127 Title: Unable to print with Brother printer since upgrade to Ubuntu 19.10 Status in cups package in Ubuntu: New Bug description: I have recently bought a new color laser printer (Brother HL- L8260CDW), which is connected through wLAN. It works like a charm under Ubuntu 19.04, but refuses to print since the upgrade to stock Ubuntu 19.10. I can reach it via ping and through its HTTP config page from the same computer. During my collection of relevant bug information I discovered the following error messages: 1. Some print filter was unable to grep /etc/cups/ppd/Brother_HL_L8260CDW_series.ppd This file was rw for user "root" and r for group "lp", but not accessible to others. I have made it world readable for testing purposes, but I still can't print. 2. I checked /var/log/syslog for app-armour errors but found none which would be related to cups and/or printing 3. After fixing the permission issue, the new error message is "File \'\' not found" and "Unable to add document to print job.", both of which are too cryptic for me to dig further into this by myself. Attached to this bug report I send the following pieces of information: - output from "/usr/lib/cups/backend/snmp 10.0.0.14" (snmp.txt) - output from "lpinfo -v" (lpinfo.txt) - output from "avahi-browse -a -v -t -r" and "avahi-browse -a -v -c -r" (avahi.txt) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: cups 2.2.12-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvi
[Touch-packages] [Bug 1849920] Re: ubuntu display problem
Thanks for the bug report. Unfortunately you seem to be using the 'oibaf' PPA which is not supported and is often buggy. Please remove that from your machine and then if any problems persist open new bugs for them. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849920 Title: ubuntu display problem Status in xorg-server package in Ubuntu: Invalid Bug description: wrong resolution login takes time does not detect intel graphics i am using ubuntu 18.04.03 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic 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: Sat Oct 26 02:35:27 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5921] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:13d1] InstallationDate: Installed on 2019-10-09 (16 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:b721 Realtek Semiconductor Corp. Bus 001 Device 003: ID 13d3:5a11 IMC Networks Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook 14_ASUS Laptop X441UAR ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=18fd12ef-f3d1-4d80-b60a-a8111a2dd43d ro quiet splash i915.alpha_support=1 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "AccelMethod" "sna" EndSection dmi.bios.date: 06/11/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X441UAR.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X441UAR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX441UAR.308:bd06/11/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook14_ASUSLaptopX441UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook 14_ASUS Laptop X441UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git1910190630.fc9336~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1910200730.7ceafa~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1910200730.7ceafa~oibaf~b 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/1849920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering [Core 2 T6600]
Thanks. Does the problem only occur in Wayland sessions? ** Summary changed: - gnome-tweak-tool window keeps flickering on cursor hovering + gnome-tweak-tool window keeps flickering on cursor hovering [Core 2 T6600] ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Summary changed: - gnome-tweak-tool window keeps flickering on cursor hovering [Core 2 T6600] + gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering [Intel Penryn: Core 2 T6600] Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering
okay i followed the instructions and here you have: ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+attachment/5300835/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
FYI, `sudo apt install gawk` can avoid this problem. Debian Bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933934 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Triaged Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850103/+attachment/5300834/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850103/+attachment/5300833/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering
apport information ** Tags added: apport-collected wayland-session ** Description changed: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. - still the problem is persistent and its abnormal irrespective of the - animation button turned on or off. + still the problem is persistent and its abnormal irrespective of the animation button turned on or off. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-10-26 (1 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: mutter + PackageArchitecture: all + ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 + Tags: wayland-session eoan + Uname: Linux 5.3.0-19-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1850103/+attachment/5300832/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering
Please run: lspci -k > lspcik.txt and send us the file 'lspcik.txt'. Please also run: apport-collect 1850103 to automatically send additional system info. ** Tags added: eoan ** Package changed: gnome-shell (Ubuntu) => gnome-tweaks (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-tweaks (Ubuntu) Status: New => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=
** Changed in: ubuntu-z-systems Status: New => Triaged -- 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/1849261 Title: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart= Status in Ubuntu on IBM z Systems: Triaged Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Disco: Fix Released Status in systemd source package in Eoan: Fix Released Bug description: Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el s390x is available, The pull request for 240 is now requested to backport to 237 for Ubuntu 18.04, which is integrated within the IBM product. Pull request: https://github.com/systemd/systemd/pull/9158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1849261/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp