[Touch-packages] [Bug 1849859] Re: error when connecting to smb server
And this: ** Attachment added: "not mounted.bmp" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1849859/+attachment/5310640/+files/not%20mounted.bmp -- 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/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1849859] Re: error when connecting to smb server
Yesterday were a lot of updates in samba package and now all is out of work, nothing goes on, nix geht mehr. Connection to the server fails completely, that ist very bad, more then the printer bug. ** Attachment added: "Abbruch.bmp" https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1849859/+attachment/5310639/+files/Abbruch.bmp -- 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/1849859 Title: error when connecting to smb server Status in cups package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in system-config-printer package in Ubuntu: Confirmed Bug description: when I connect to smb server (nas) permanently appears "Error while getting peer-to-peer dbus connection: Operation was cancelled" The printer at this NAS doesn't work too. "held for authentication KeyError: 'auth-info-required'" The same printer at usb port works fine. Ubuntu development version 20.04 system-config-printer version 1.5.11-4ubuntu1 smbclient version 2:4.10.7+dfsg-0ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1849859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855565] [NEW] After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up
Public bug reported: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.31 Sun Oct 27 02:19:35 UTC 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:26:22 2019 DistUpgraded: 2019-11-14 14:45:51,508 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-14 (23 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug corruption eoan third-party-packages ubuntu ** Attachment added: "screenshot showing taskbar with corrupted fonts" https://bugs.launchpad.net/bugs/1855565/+attachment/5310605/+files/Screenshot%20from%202019-12-07%2017-26-57.png -- 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/1855565 Title: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up Status in xorg package in Ubuntu: New Bug description: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.31 Sun Oct 27
[Touch-packages] [Bug 1855565] Re: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up
** Attachment added: "screenshot showing popup asking for sudo password" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855565/+attachment/5310629/+files/Screenshot%20from%202019-12-07%2017-27-46.png -- 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/1855565 Title: After resuming from lockscreen and/or suspend, taskbar, dock, and screen fonts are messed up Status in xorg package in Ubuntu: New Bug description: After waking from suspend, the taskbar fonts are unreadable, as are the fonts used on the dock and on the icons on the desktop. The only cure I can find is to reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-22.24+system76~1573659475~19.10~26b2022~dev-generic 5.3.7 Uname: Linux 5.3.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.31 Sun Oct 27 02:19:35 UTC 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,grid,move,compiztoolbox,gnomecompat,imgpng,resize,imgjpeg,regex,vpswitch,unitymtgrabhandles,snap,place,mousepoll,session,screenshot,resizeinfo,thumbnail,wall,animation,workarounds,expo,ezoom,staticswitcher,fade,scale,unityshell,dbus] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 17:26:22 2019 DistUpgraded: 2019-11-14 14:45:51,508 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204M [GeForce GTX 980M] [10de:1617] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 980M] [1558:7703] InstallationDate: Installed on 2017-11-01 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic root=UUID=fbf9e88e-c136-41b5-91a1-0848d0d8427a ro quiet splash snd_hda_intel.probe_mask=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-11-14 (23 days ago) dmi.bios.date: 07/11/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.10RSA1 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw9 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.10RSA1:bd07/11/2016:svnSystem76,Inc.:pnServalWS:pvrserw9:rvnSystem76,Inc.:rnServalWS:rvrserw9:cvnSystem76,Inc.:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Serval WS dmi.product.sku: Not Applicable dmi.product.version: serw9 dmi.sys.vendor: System76, Inc. version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1855565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
Some additional information and observations. What I am currently seeing with this issue on 3 systems running Ubuntu 18.04 that did not occur on the same systems that previously ran 16.04 is that the actual screen blanking in 18.04, aside from default settings or overrides, fails to turn off the monitor using DPMS as it did in 16.04, but only with nvidia binary drivers installed and only in 18.04, and only with the console blanking code in its current state. In 18.04 without the nvidia binary driver, console blanking seems to work, as expected, with the consoleblank=n. This includes a correct power down. In 18.04 with the nvidia binary driver 340.107, console blanking only blanks the screen, but fails to power down the monitor- yet a call to vbetool dpms off does work, as do any similar calls in X for those systems that have X installed. So if vbetool dpms works with the nvidia binary driver and the console blanking code no longer does, I am half way to an assumption that the dpms code in the console blanking has changed, with some reservation that possibly the latest nvidia binary driver doesn't like the way the call is coming from the newly changed console blanking code. This problem did not exist in 16.04, on any of our systems to my knowledge, with or without a graphical desktop installed and with or without a binary driver installed. >From my perspective, this isn't an issue of default blanking behaviour, but rather an issue with a broken dpms call in 18.04 to a system with the nvidia binary driver. Other calls, such as vbetool dpms off work as do those within graphical desktop systems such as those like the one that xscreensaver uses. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kbd in Ubuntu. https://bugs.launchpad.net/bugs/869017 Title: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) Status in kbd package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in kbd source package in Zesty: Invalid Status in linux source package in Zesty: Fix Released Status in kbd package in Debian: Fix Released Bug description: James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855092] Re: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown
This bug was fixed in the package pam - 1.3.1-5ubuntu3 --- pam (1.3.1-5ubuntu3) focal; urgency=medium * Fix patches to fix FTBFS -- Balint Reczey Thu, 05 Dec 2019 13:18:35 +0100 ** Changed in: pam (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1855092 Title: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown Status in pam package in Ubuntu: Fix Released Status in pam source package in Eoan: Fix Committed Bug description: [Impact] * Users of containers may never see the MOTD of the container if they are always to the container's shell without PAM being involved. * MOTD contains important information about the system's health including the security updates to be installed thus it is desired to show MOTD in container shells, too. * The fix in update-motd is creating a snippet in /etc/profile.d which shows MOTD, but only if UPDATE_MOTD is not set, to avoid printing MOTD twice. [Test Case] * Log in to the system, where PAM prints the MOTD. * After seeing the MOTD observe MOTD_SHOWN set: $ echo $MOTD_SHOWN pam $ [Regression Potential] * The fix is simple thus it is unlikely to see any regression due to bad implementation. * The newly set environment variable may interact with existing software, but this variable seems to be not used: https://codesearch.debian.net/search?q=MOTD_SHOWN=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1855092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855555] [NEW] CA0132: Only stereo with Creative Soundblaster ZxR
Public bug reported: I have a 5.1 sound system that is connected via three 3.5 mm audio cables with my Sound Blaster ZxR: Front Left, Center, Front Right, Rear Left, Rear Right, LFE I only get sound from "Front Left"/"Front Right". All other speakers don't make a sound. I tested Ubuntu 19.04, Ubuntu 19.10, Manjaro 18.10, different Kernels and the Sound Blaster Patch from reddit, nothing helped. After all these tests, I started again with a fresh Ubuntu 19.10 installation with this output from "alsa information script": http ://alsa-project.org/db/?f=c9d4adfbc5441c4975b6e6c7a6fb3cbfc201158a Only thing that I did was changing the default audio device to my ZxR. Otherwise my NVIDIA graphics card is selected. I did that with ~/.asoundrc: defaults.ctl.!card "Creative" defaults.pcm.!card "Creative" defaults.timer.!card "Creative" Interestingly I decided to install Windows 10 on my second drive in dual boot mode. I noticed that when I start Windows all speakers are working. Then I reboot to Ubuntu and all speakers are working, too. This effect will vanish if I shut down my PC and start directly to Ubuntu. So something happens on Windows that is kept while rebooting to Ubuntu.. I already reported this issue at bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=205315 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Package changed: flameshot (Ubuntu) => alsa-driver (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/185 Title: CA0132: Only stereo with Creative Soundblaster ZxR Status in alsa-driver package in Ubuntu: New Bug description: I have a 5.1 sound system that is connected via three 3.5 mm audio cables with my Sound Blaster ZxR: Front Left, Center, Front Right, Rear Left, Rear Right, LFE I only get sound from "Front Left"/"Front Right". All other speakers don't make a sound. I tested Ubuntu 19.04, Ubuntu 19.10, Manjaro 18.10, different Kernels and the Sound Blaster Patch from reddit, nothing helped. After all these tests, I started again with a fresh Ubuntu 19.10 installation with this output from "alsa information script": http://alsa- project.org/db/?f=c9d4adfbc5441c4975b6e6c7a6fb3cbfc201158a Only thing that I did was changing the default audio device to my ZxR. Otherwise my NVIDIA graphics card is selected. I did that with ~/.asoundrc: defaults.ctl.!card "Creative" defaults.pcm.!card "Creative" defaults.timer.!card "Creative" Interestingly I decided to install Windows 10 on my second drive in dual boot mode. I noticed that when I start Windows all speakers are working. Then I reboot to Ubuntu and all speakers are working, too. This effect will vanish if I shut down my PC and start directly to Ubuntu. So something happens on Windows that is kept while rebooting to Ubuntu.. I already reported this issue at bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=205315 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855555] [NEW] CA0132: Only stereo with Creative Soundblaster ZxR
You have been subscribed to a public bug: I have a 5.1 sound system that is connected via three 3.5 mm audio cables with my Sound Blaster ZxR: Front Left, Center, Front Right, Rear Left, Rear Right, LFE I only get sound from "Front Left"/"Front Right". All other speakers don't make a sound. I tested Ubuntu 19.04, Ubuntu 19.10, Manjaro 18.10, different Kernels and the Sound Blaster Patch from reddit, nothing helped. After all these tests, I started again with a fresh Ubuntu 19.10 installation with this output from "alsa information script": http ://alsa-project.org/db/?f=c9d4adfbc5441c4975b6e6c7a6fb3cbfc201158a Only thing that I did was changing the default audio device to my ZxR. Otherwise my NVIDIA graphics card is selected. I did that with ~/.asoundrc: defaults.ctl.!card "Creative" defaults.pcm.!card "Creative" defaults.timer.!card "Creative" Interestingly I decided to install Windows 10 on my second drive in dual boot mode. I noticed that when I start Windows all speakers are working. Then I reboot to Ubuntu and all speakers are working, too. This effect will vanish if I shut down my PC and start directly to Ubuntu. So something happens on Windows that is kept while rebooting to Ubuntu.. I already reported this issue at bugzilla.kernel.org: https://bugzilla.kernel.org/show_bug.cgi?id=205315 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New -- CA0132: Only stereo with Creative Soundblaster ZxR https://bugs.launchpad.net/bugs/185 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver 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 1850267] Re: autopkgtest 'nm' fails because it can't find dnsmasq
test now passes. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/n/network-manager/20191206_224534_e76d4@/log.gz ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1850267 Title: autopkgtest 'nm' fails because it can't find dnsmasq Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: [impact] test 'nm' fails because dnsmasq-base isn't installed [test case] see test results http://autopkgtest.ubuntu.com/packages/network-manager/bionic/amd64 [regression potential] low, test fix only [other info] The d/t/control file 'nm' test section, for bionic, needs to include dnsmasq-base in its dep list. disco and later already include dnsmasq-base in test dep packages, and in xenial network-manager directly depends on dnsmasq-base. So this is needed only for bionic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1850267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855549] Re: ubuntu-wsl: Please recommend show-motd
** Merge proposal linked: https://code.launchpad.net/~rbalint/ubuntu-seeds/+git/ubuntu/+merge/376488 ** Merge proposal linked: https://code.launchpad.net/~rbalint/ubuntu-seeds/+git/ubuntu/+merge/376489 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1855549 Title: ubuntu-wsl: Please recommend show-motd Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1855549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855549] [NEW] ubuntu-wsl: Please recommend show-motd
Public bug reported: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1855549 Title: ubuntu-wsl: Please recommend show-motd Status in ubuntu-meta package in Ubuntu: New Bug description: [ Impact ] * Desktop users of WSL are 'dropped into' the Ubuntu shell instead of logging in to the WSL container, thus they don't see MOTD. Then don't get information about the system's state via desktop notifications either, because the default Ubuntu WSL system does not start the Ubuntu desktop. * To show important system information to users being dropped to a shell directly the show-motd package was created to show MOTD using a /etc/profile.d script. * To have this script in place ubuntu-wsl needs to recommend show-motd. [ Test Case ] * Use 'apt-cache show ubuntu-wsl' to check if ubuntu-wsl recommends update-motd. [ Regression Potential ] * Pulling in a /etc/profile.d script that exits can make the started shell exit immediately. For this reason the shell does not exit in any case. The script can also throw confusing errors. To avoid such errors the script is tested in an autopkgtest and many related packages were fixed where errors were observed. The update-motd package adds Breaks: against related package versions which are known to show errors in MOTD when being run as a regular user. See LP: #1855271 for more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1855549/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855513] Re: log file
** Changed in: lxc (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1855513 Title: log file Status in lxc package in Ubuntu: Invalid Bug description: required log and cli bash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1855513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
e.g. see test results for s390x across releases: http://autopkgtest.ubuntu.com/packages/network-manager ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-disco verification-done-eoan verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855009] Re: autopkgtests all fail on s390x
s390x tests are all now 'neutral' (since no tests are actually run, as explained in description). -- 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/1855009 Title: autopkgtests all fail on s390x Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Committed Status in network-manager source package in Bionic: Fix Committed Status in network-manager source package in Disco: Fix Committed Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] all autopkgtests fail on s390x [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/s390x/n/network- manager/20191130_001946_a5512@/log.gz autopkgtest [00:19:32]: summary wpa-dhclient FAIL non-zero exit status 1 nm.pyFAIL non-zero exit status 1 killswitches-no-urfkill FAIL non-zero exit status 1 urfkill-integration FAIL non-zero exit status 1 [regression potential] this essentially skips all the autopkgtests for network-manager on s390x, so regressions could occur now or in the future due to lack of testing on s390x. However, all the tests already fail on s390x and have since xenial (or earlier), so there hasn't been any useful test coverage on s390x before; this doesn't change that. [other info] as mentioned in comment 2, wireless networking is specifically excluded on s390 systems: menuconfig WIRELESS bool "Wireless" depends on !S390 default y The 'wpa-dhclient' test is specific to wireless, and both 'killswitches-no-urfkill' and 'urfkill-integration' require rfkill which requires wireless, so none of those tests are valid on s390x, since it doesn't have any wireless support. However the 'nm.py' test does have some test cases that don't rely on wireless capability, but it would be much more intrusive to update the test to split out wired vs. wireless testing, and that might introduce test regressions on other archs. The use case for network-manager on s390x in general is questionable, since s390x has no wireless support and obviously is never 'mobile', which are 2 main reasons to use network-manager instead of systemd-networkd. Additionally, all tests are currently skipped on armhf due to the requirement for machine isolation (and armhf tests run in containers), so s390x is not the first arch to simply skip all network-manager autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855183] Re: autopkgtest fails on i386 because linux-headers-generic no longer built for i386
autopkgtest on i386 for eoan now pass, with the rfkill tests skipped: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/i386/n/network-manager/20191206_211958_67c6c@/log.gz ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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/1855183 Title: autopkgtest fails on i386 because linux-headers-generic no longer built for i386 Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: Fix Committed Status in network-manager source package in Focal: Fix Released Bug description: [impact] the kernel is no longer built for i386, starting with Eoan. However some of the autopkgtests depend on linux-headers-generic, which isn't available for i386, so the test fails with bad dependency. [test case] check autopkgtest logs, e.g. http://autopkgtest.ubuntu.com/packages/network-manager/focal/i386 Broken autopkgtest-satdep:i386 Depends on linux-headers-generic:i386 < none @un H > Removing autopkgtest-satdep:i386 because I can't find linux-headers-generic:i386 [regression potential] test case fix only, regressions would involve more/continued test failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825946] Re: 'nm' autopkgtest fails due to GI stderr output
test no longer prints gi warning, e.g.:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/n/network-manager/20191206_223737_58d54@/log.gz
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1825946
Title:
'nm' autopkgtest fails due to GI stderr output
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Xenial:
Fix Committed
Status in network-manager source package in Bionic:
Fix Released
Bug description:
[impact]
'nm' testcase contains:
from gi.repository import NetworkManager, NMClient, GLib
which generates output to stderr:
/tmp/autopkgtest.naU0ts/build.riU/src/debian/tests/nm:23: PyGIWarning:
NetworkManager was imported without specifying a version first. Use
gi.require_version('NetworkManager', '1.0') before import to ensure that the
right version gets loaded.
the gi.require_version call has already been added to cosmic and
disco.
[test case]
see http://autopkgtest.ubuntu.com/packages/network-manager bionic test
results.
[other info]
this only fails intermittently, but the failure is clearly not an
actual problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1825946/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 882825] Re: Does not save the configuration file under ~/.config/
** Also affects: gconf Importance: Undecided Status: New ** Also affects: ipython Importance: Undecided Status: New ** Also affects: nano Importance: Undecided Status: New ** Also affects: remmina Importance: Undecided Status: New ** Also affects: wine Importance: Undecided Status: New ** Also affects: npm Importance: Undecided Status: New ** Also affects: pip Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/882825 Title: Does not save the configuration file under ~/.config/ Status in gconf: New Status in The Gimp: Fix Released Status in IPython: New Status in nano: New Status in npm: New Status in pip: New Status in remmina: New Status in Wine: New Status in adobe-flashplugin package in Ubuntu: New Status in bash package in Ubuntu: New Status in bzr package in Ubuntu: Fix Released Status in compiz package in Ubuntu: Confirmed Status in dbus package in Ubuntu: New Status in dia package in Ubuntu: New Status in gconf package in Ubuntu: Triaged Status in gegl package in Ubuntu: Fix Released Status in gimp package in Ubuntu: Confirmed Status in gl-117 package in Ubuntu: New Status in gnome-games package in Ubuntu: Fix Released Status in gnupg package in Ubuntu: New Status in gvfs package in Ubuntu: Confirmed Status in hydrogen package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in onboard package in Ubuntu: Fix Released Status in python-launchpadlib package in Ubuntu: Invalid Status in shotwell package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Confirmed Status in w3m package in Ubuntu: New Status in xchat package in Ubuntu: Triaged Bug description: It does not save the configuration file(s) and/or the cache under the right location for configuration file storage which is under ~/.config/ and ~/.cache/ To manage notifications about this bug go to: https://bugs.launchpad.net/gconf/+bug/882825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
I have the Samsung Notebook 9 pen and there is no speaker volume at all, in Ubuntu 19.10 -- 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/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 882825] Re: Does not save the configuration file under ~/.config/
** Changed in: thunderbird (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/882825 Title: Does not save the configuration file under ~/.config/ Status in The Gimp: Fix Released Status in adobe-flashplugin package in Ubuntu: New Status in bash package in Ubuntu: New Status in bzr package in Ubuntu: Fix Released Status in compiz package in Ubuntu: Confirmed Status in dbus package in Ubuntu: New Status in dia package in Ubuntu: New Status in gconf package in Ubuntu: Triaged Status in gegl package in Ubuntu: Fix Released Status in gimp package in Ubuntu: Confirmed Status in gl-117 package in Ubuntu: New Status in gnome-games package in Ubuntu: Fix Released Status in gnupg package in Ubuntu: New Status in gvfs package in Ubuntu: Confirmed Status in hydrogen package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in onboard package in Ubuntu: Fix Released Status in python-launchpadlib package in Ubuntu: Invalid Status in shotwell package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Confirmed Status in w3m package in Ubuntu: New Status in xchat package in Ubuntu: Triaged Bug description: It does not save the configuration file(s) and/or the cache under the right location for configuration file storage which is under ~/.config/ and ~/.cache/ To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/882825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855505] Re: Could you add a "Secure Delete" option to the "Purge Trash and Temporary Files" option.
** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1855505 Title: Could you add a "Secure Delete" option to the "Purge Trash and Temporary Files" option. Status in gnome-control-center package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Option to enable secure deletion. 4) There is no option for secure deletion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855507] Re: Previous screen or next screen is not displayed when the left or right arrow is pressed.
** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1855507 Title: Previous screen or next screen is not displayed when the left or right arrow is pressed. Status in gnome-control-center package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Select an item, press right arrow to show next screen. Press left arrow to show previous screen. 4) Selected an item, pressed right arrow, next screen was not displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855507/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855508] Re: Add an "Appearance" item to the menu.
** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1855508 Title: Add an "Appearance" item to the menu. Status in gnome-control-center package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) The ability to change window appearance, icons, etc. Switch between light or dark theme. 4) Unable to change window appearance, icons, etc. Switch between light or dark theme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855510] Re: Sort menu items alphabetically.
** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1855510 Title: Sort menu items alphabetically. Status in gnome-control-center package in Ubuntu: New Bug description: 1) Ubuntu 19.10 2) 1:3.34.1-1ubuntu2 3) Menu items sorted alphabetically. 4) Menu items were not sorted alphabetically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1855510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855536] [NEW] No german translation for gcc-9 (or missing symlink)
Public bug reported: GCC supports translation of error and warning messages into locales. For this to work, the package language-pack-de-base provides the file /usr/share/locale-langpack/de/LC_MESSAGES/gcc.mo. However, the current version of gcc (from package gcc-9, which is a dependency of gcc), is looking for gcc-9.mo. Here is the relevant part of an strace of gcc: openat(AT_FDCWD, "/usr/share/locale/de_DE.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de_DE.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de_DE/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de_DE.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de_DE.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de_DE/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) When creating a symlink from /usr/share/locale- langpack/de/LC_MESSAGES/gcc-9.mo to /usr/share/locale- langpack/de/LC_MESSAGES/gcc.mo, everything is working fine. Older version of gcc behave similarly. (They are looking for gcc-7.mo and gcc-8.mo, respectively). ** Affects: language-pack-de-base (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-de-base in Ubuntu. https://bugs.launchpad.net/bugs/1855536 Title: No german translation for gcc-9 (or missing symlink) Status in language-pack-de-base package in Ubuntu: New Bug description: GCC supports translation of error and warning messages into locales. For this to work, the package language-pack-de-base provides the file /usr/share/locale-langpack/de/LC_MESSAGES/gcc.mo. However, the current version of gcc (from package gcc-9, which is a dependency of gcc), is looking for gcc-9.mo. Here is the relevant part of an strace of gcc: openat(AT_FDCWD, "/usr/share/locale/de_DE.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de_DE.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de_DE/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale/de/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de_DE.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de_DE.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de_DE/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de.UTF-8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de.utf8/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) openat(AT_FDCWD, "/usr/share/locale-langpack/de/LC_MESSAGES/gcc-9.mo", O_RDONLY) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) When creating a symlink from /usr/share/locale- langpack/de/LC_MESSAGES/gcc-9.mo to /usr/share/locale- langpack/de/LC_MESSAGES/gcc.mo, everything is working fine. Older version of gcc behave similarly. (They are looking for gcc-7.mo and gcc-8.mo, respectively). To manage notifications about this bug go
[Touch-packages] [Bug 1841510] Re: LONG delay sometimes 10+ minutes when opening file dialogue
** Description changed: 1) The release of Ubuntu you are using XCFE 4.12 2) The version of the package you are using affects multiple programs including thunderbird and xed thunderbird: - Installed: 1:60.8.0+build1-0ubuntu0.16.04.2 + Installed: 1:60.8.0+build1-0ubuntu0.16.04.2 xed: - Installed: 1.4.6+sonya + Installed: 1.4.6+sonya gthumb: - Installed: 3:3.4.3-1 + Installed: 3:3.4.3-1 3) What you expected to happen I expect to be able to open a file or save as within a few seconds. 4) What happened instead - When I try to open a file or attach a file or save as it can take over 20 minutes. But the really weird thing is sometimes it is nearly instantaneous. So I am writing this as the problem has worsened + When I try to open a file or attach a file or save as it can take over 20 minutes. But the really weird thing is sometimes it is nearly instantaneous. So I am writing this as the problem has worsened - using thunderbird - wanted to attach a file - hung for a few minutes - was able to finally attach it Tried with gthumb (great program) to "save as' clicking on the icon to do so - first image was nearly instantaneous and worked fine - second image - took several minutes (is still hung so cannot say how long!) This works not works is a constant finding! it is almost an alternate use of any file dialogues works fast - works very slow - works fast. Very strange and very annoying Other information: some people report that having network resources not yet mounted caused this: - - I have several network disks - some mounted, some not + - I have several network disks - some mounted, some not - are all in fstab (some are not turned on at the moment) - some are bookmarked in file managers I tried removing these and still had the issue BUT seems to be a longer delay since adding some network disks to fstab I hope this is the correct information - have not reported a bug before. Really appreciate ubuntu and the help you give. Thank you. + + Dec 7th + My husband pc is running Mint 18.2 + I have mint 18.2 first installed and then added xfce as problems with various things in mint (not this issues)last few days his PC now has exactly the same issue. ** Description changed: 1) The release of Ubuntu you are using XCFE 4.12 2) The version of the package you are using affects multiple programs including thunderbird and xed thunderbird: Installed: 1:60.8.0+build1-0ubuntu0.16.04.2 xed: Installed: 1.4.6+sonya gthumb: Installed: 3:3.4.3-1 3) What you expected to happen I expect to be able to open a file or save as within a few seconds. 4) What happened instead When I try to open a file or attach a file or save as it can take over 20 minutes. But the really weird thing is sometimes it is nearly instantaneous. So I am writing this as the problem has worsened - - using thunderbird + - using thunderbird, firefox, Xed - wanted to attach a file - hung for a few minutes - was able to finally attach it Tried with gthumb (great program) to "save as' clicking on the icon to do so - first image was nearly instantaneous and worked fine - second image - took several minutes (is still hung so cannot say how long!) This works not works is a constant finding! it is almost an alternate use of any file dialogues works fast - works very slow - works fast. Very strange and very annoying Other information: some people report that having network resources not yet mounted caused this: - I have several network disks - some mounted, some not - are all in fstab (some are not turned on at the moment) - some are bookmarked in file managers I tried removing these and still had the issue BUT seems to be a longer delay since adding some network disks to fstab I hope this is the correct information - have not reported a bug before. Really appreciate ubuntu and the help you give. Thank you. Dec 7th My husband pc is running Mint 18.2 I have mint 18.2 first installed and then added xfce as problems with various things in mint (not this issues)last few days his PC now has exactly the same issue. -- 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/1841510 Title: LONG delay sometimes 10+ minutes when opening file dialogue Status in gtk+3.0 package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using XCFE 4.12 2) The version of the package you are using affects multiple programs including thunderbird and xed thunderbird: Installed: 1:60.8.0+build1-0ubuntu0.16.04.2 xed: Installed: 1.4.6+sonya gthumb: Installed: 3:3.4.3-1 3) What you expected to happen I expect to be able to open a file or save as within a few seconds. 4) What happened instead When I try to open a file or attach a
[Touch-packages] [Bug 1753928] Re: Please update OpenCV to 3.4
Looks like a couple of releases went by without much happening, but Ubuntu 20.04 is now looking to release with opencv 4.1.2 (https://bugs.launchpad.net/ubuntu/+source/opencv/4.1.2+dfsg-5) ** Changed in: opencv (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1753928 Title: Please update OpenCV to 3.4 Status in opencv package in Ubuntu: Fix Released Bug description: From https://launchpad.net/ubuntu/bionic/+source/opencv I got to know the version of OpenCV that will be shipped with Bionic is 3.1. However this is way too old (from 2015). It's been more than 3 months since OpenCV 3.4.0 was released. Can you consider OpenCV version 3.4.x for Bionic release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1753928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799032] Re: Update to libcap 2.26
Thanks for reporting :) libcap2 2.27 has been packaged in Debian and synced to Ubuntu Focal (https://bugs.launchpad.net/ubuntu/+source/libcap2/1:2.27-1) ** Changed in: libcap2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libcap2 in Ubuntu. https://bugs.launchpad.net/bugs/1799032 Title: Update to libcap 2.26 Status in libcap2 package in Ubuntu: Fix Released Status in libcap2 package in Debian: Fix Released Bug description: Hey everyone, We recently pushed support for ambient capabilities and namespaces filesystem capabilities to libcap2 [1]. Together with Andrew Morgan, Serge Hallyn and I have released a version 2.26 of libcap2. Note that libcap2 has moved to a new location [2] The 2.26 release can be downloaded from [3]. Please update to the new version! [1]: https://sites.google.com/site/fullycapable/release-notes-for-libcap/pre-releasenotesfor226 [2]: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/ [3]: https://git.kernel.org/pub/scm/libs/libcap/libcap.git/snapshot/libcap-2.26.tar.gz Thanks! Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/1799032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853669] Re: systemd resolves own hostname to link local ipv6 address
Ok, just to check, I changed /etc/resolv.conf to remove second nameserver, added "domain .hm" and "search hm", added "fpc.hm" to the respective entry in 10.2.2.3's /etc/hosts. Result is, that localhost's systemd-resolved now no longer knows about upstream dns 10.2.2.3 -- where else am I supposed to configure that? So, I re-added "nameserver 10.2.2.3" to /etc/resolv.conf, and it really seems like it would once again take the second nameserver-entry as that for upstream-dns. Apparently, with "domain" and "search" in place, systemd-resolved no longer makes any attempt to obtain information from routing table, thus appears to work. Nevertheless, apparently systemd-resolved DOES have a feature where it queries local information about network devices to get a list of ip-addresses whenever there is no domain/search defined and a bare name queried. What is the reason behind that feature, if the suggested solution to this ticket is just: "don't use bare hostnames"? ** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1853669 Title: systemd resolves own hostname to link local ipv6 address Status in systemd package in Ubuntu: Confirmed Bug description: I've got an ethernet-device that only has a configured ipv4 address, and some auto-generated link-local (aka "scope link") ipv6 address. Any tool doing a DNS query (and /lib/systemd/systemd-resolved is the DNS-server listening on 127.0.0.53) for this host's hostname gets back two addresses: the correct ipv4 address, and a broken ipv6 address. Unlike on ipv4, it is possible for the same ipv6-address to be assigned to multiple devices, and therefore the address is only valid in the context of the eth-device. Now, if "ifconfig" shows "inet6 fe80::4687:fcff:fe9e:4ac7 prefixlen 64 scopeid 0x20" then "fe80::4687:fcff:fe9e:4ac7" is NOT a connectable address, and syscall connect() typically fails with EINVAL. To make it a valid address, it needs to be suffixed with a "%" and the device name, like: fe80::4687:fcff:fe9e:4ac7%enp4s0 Either the resolver can return the link name attached to the address separated with a "%" char, or it needs to ignore link-local inet6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853669/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383470] Re: scp fails at 'Sending command scp -v -t' when network connection is not reliable
** Summary changed: - scp does not work (fails at 'Sending command scp -v -t') + scp fails at 'Sending command scp -v -t' when network connection is not reliable ** Changed in: openssh (Ubuntu) Status: Expired => 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/1383470 Title: scp fails at 'Sending command scp -v -t' when network connection is not reliable Status in openssh package in Ubuntu: Incomplete Bug description: Following the last update of Ubuntu 14.02, scp (in the default system) has ceased working. It hangs after authentication at the point where it wold start an interactive session. I've verified that the problem is in my system: scp still works at the target machine and scp won't work on my machine to various hosts. Output below. rasmith@rasmith-Lemur-Ultra:~$ scp -v testfil apacentral.org: Executing: program /usr/bin/ssh host apacentral.org, user (unspecified), command scp -v -t . OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /home/rasmith/.ssh/config debug1: /home/rasmith/.ssh/config line 17: Applying options for * debug1: /home/rasmith/.ssh/config line 20: Deprecated option "rhostsauthentication" debug1: /home/rasmith/.ssh/config line 25: Deprecated option "fallbacktorsh" debug1: /home/rasmith/.ssh/config line 26: Deprecated option "usersh" debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug1: Connecting to apacentral.org [65.19.130.61] port 22. debug1: Connection established. debug1: could not open key file '/etc/ssh/ssh_host_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: could not open key file '/etc/ssh/ssh_host_dsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ecdsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_rsa_key': Permission denied debug1: could not open key file '/etc/ssh/ssh_host_ed25519_key': No such file or directory debug1: identity file /home/rasmith/.ssh/identity type 0 debug1: identity file /home/rasmith/.ssh/identity-cert type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4_hpn13v11 FreeBSD-2013 debug1: match: OpenSSH_6.4_hpn13v11 FreeBSD-2013 pat OpenSSH* compat 0x0400 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-ctr hmac-md5-...@openssh.com none debug1: kex: client->server aes128-ctr hmac-md5-...@openssh.com none debug1: sending SSH2_MSG_KEX_ECDH_INIT debug1: expecting SSH2_MSG_KEX_ECDH_REPLY debug1: Server host key: RSA 61:40:9f:26:85:d2:57:34:f9:52:7b:c3:47:9d:7a:ae debug1: Host 'apacentral.org' is known and matches the RSA host key. debug1: Found key in /home/rasmith/.ssh/known_hosts:26 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: Roaming not allowed by server debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Next authentication method: publickey debug1: Offering DSA public key: rasm...@aristotle.tamu.edu debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: Authentication succeeded (publickey). Authenticated to apacentral.org ([65.19.130.61]:22). debug1: channel 0: new [client-session] debug1: Requesting no-more-sessi...@openssh.com debug1: Entering interactive session. debug1: Sending environment. debug1: Sending env LANG = en_US.UTF-8 debug1: Sending command: scp -v -t . (at this point, the command hangs more or less indefinitely until killed with Ctrl-C) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ssh 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 20 15:25:14 2014 InstallationDate: Installed on 2012-10-18 (732 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: Upgraded to trusty on 2014-05-02 (170 days ago) To manage notifications about this bug go to:
[Touch-packages] [Bug 1855092] Re: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown
** Tags added: wsl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1855092 Title: [SRU] Please set MOTD_SHOWN=pam when MOTD was shown Status in pam package in Ubuntu: In Progress Status in pam source package in Eoan: Fix Committed Bug description: [Impact] * Users of containers may never see the MOTD of the container if they are always to the container's shell without PAM being involved. * MOTD contains important information about the system's health including the security updates to be installed thus it is desired to show MOTD in container shells, too. * The fix in update-motd is creating a snippet in /etc/profile.d which shows MOTD, but only if UPDATE_MOTD is not set, to avoid printing MOTD twice. [Test Case] * Log in to the system, where PAM prints the MOTD. * After seeing the MOTD observe MOTD_SHOWN set: $ echo $MOTD_SHOWN pam $ [Regression Potential] * The fix is simple thus it is unlikely to see any regression due to bad implementation. * The newly set environment variable may interact with existing software, but this variable seems to be not used: https://codesearch.debian.net/search?q=MOTD_SHOWN=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1855092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855271] Re: Please make /etc/update-motd.d snippets runnable by regular users
** Tags added: wsl -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1855271 Title: Please make /etc/update-motd.d snippets runnable by regular users Status in base-files package in Ubuntu: Fix Released Status in ubuntu-release-upgrader package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: New Status in base-files source package in Eoan: Fix Committed Bug description: [Impact] * /etc/update-motd.d snippets throw errors when a normal user runs them. * This prevents showing MOTD when the user is dropped to a regular user's shell in WSL. [Test Case] * Run update-motd's autopkgtest and observe scripts not throwing errors. [Regression Potential] * The fixes are fairly simple, but to ensure no breakage the scripts are also run as root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1855271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1855521] [NEW] Internal microphone not detected
Public bug reported: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1855521 Title: Internal microphone not detected Status in alsa-driver package in Ubuntu: New Bug description: No input device available for selection. Output of dmesg | grep snd: [2.247186] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [2.372911] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [2.532497] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [2.532499] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [2.532500] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [2.532501] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [2.532502] snd_hda_codec_realtek hdaudioC0D0:inputs: [2.532503] snd_hda_codec_realtek hdaudioC0D0: Headphone Mic=0x1a [2.532504] snd_hda_codec_realtek hdaudioC0D0: Headset Mic=0x19 --- Alsamixer checked for mutes, all OK. Internal mic not present. Cannot remap using hdajackretask due to error tee: /sys/class/sound/hwC0D0/reconfig: Device or resource busy. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tom3754 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 08:10:21 2019 InstallationDate: Installed on 2019-12-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0012KY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd10/30/2019:svnDellInc.:pnInspiron5490:pvr:rvnDellInc.:rn0012KY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5490 dmi.product.sku: 0955 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to:
