[Touch-packages] [Bug 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Same. Ubuntu 18.04, Sony WH-CH700N I have to go to bluetooth device list, disconnect device and reconnect from UI. after that, default sound card correctly switches over and i can hear music. Without that, i can't even switch the sound card, even though it's visible in the list. -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
@Rbalint - FYI the test hint is merged and active for now. Since your fix will NOT bump the version of livecd-rootfs it will continue to be hinted even after the fix, would you mind once this bug here is resolved to open up an MP to remove the hint again? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: Invalid Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Confirmed Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+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 1814025] Re: Screen flickering on many programm
It appears you have some unsupported graphics packages installed from the "Oibaf" PPA. Please use 'ppa-purge' to remove that PPA from the system. Then reboot. If the problem still persists after that then run: dpkg -l > allpackages.txt and send us the resulting file 'allpackages.txt'. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814025 Title: Screen flickering on many programm Status in xorg-server package in Ubuntu: Incomplete Bug description: While using VSCode, Firefox Developer Edition, Google Chrome. Watching youtube videos or coding the screen flickering really bad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: i3 Date: Thu Jan 31 10:55:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20] InstallationDate: Installed on 2019-01-11 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. UX430UAR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "Backlight" "intel_backlight" EndSection dmi.bios.date: 10/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.300:bd10/06/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901260730.8e9ad5~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1901260730.8e9ad5~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1901101932.b1c016~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1901211932.33ee0c~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1901240732.ca1391~oibaf~b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1814025/+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 1814025] [NEW] Screen flickering on many programm
Public bug reported: While using VSCode, Firefox Developer Edition, Google Chrome. Watching youtube videos or coding the screen flickering really bad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: i3 Date: Thu Jan 31 10:55:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20] InstallationDate: Installed on 2019-01-11 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. UX430UAR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "Backlight" "intel_backlight" EndSection dmi.bios.date: 10/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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.:bvrUX430UAR.300:bd10/06/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX430UAR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901260730.8e9ad5~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 19.0~git1901260730.8e9ad5~oibaf~b version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git1901101932.b1c016~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1901211932.33ee0c~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1901240732.ca1391~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1814025 Title: Screen flickering on many programm Status in xorg package in Ubuntu: New Bug description: While using VSCode, Firefox Developer Edition, Google Chrome. Watching youtube videos or coding the screen flickering really bad ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: i3 Date: Thu Jan 31 10:55:30 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:1c20] InstallationDate: Installed on 2019-01-11 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: ASUSTeK COMPUTER INC. UX430UAR ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b2e09cf1-c874-41a4-86ee-c64c58e32f29 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "Device" Identifier "Card0" Driver "intel" Option "Backlight" "intel_backlight" EndSection dmi.bios.date: 10/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX430UAR.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX430UAR 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:
[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Looking at pulseaudio upstream, it looks like 12.2 has 15386a710c1500f70085a6312fb4d84be4d254c9 and c7fe78c9f73ded2c3428666722ec9c1af4b82812 but not 83675b3745c64bd738400eae44eb4daa195ed88a fe6a9a8f59932f29cc77eac2a7e2c6bd07c8c7d0 3454c19f3c277d5d0099f17e7ebf5d2005afa4b0 Bionic will needs all of the above sha's. -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Cosmic: Confirmed Status in pulseaudio source package in Disco: Confirmed Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1805418] Re: Update pre-populator patch with correct desktop names
https://launchpad.net/ubuntu/+source/zeitgeist/1.0.1-1ubuntu2 ** Changed in: zeitgeist (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1805418 Title: Update pre-populator patch with correct desktop names Status in zeitgeist package in Ubuntu: Fix Released Bug description: Use correct desktop names for totem, gedit and gnome-calculator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1805418/+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 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
openssh relies on RRSIG records to verify the remote key using DNSSEC and SSHFP resource records. See VerifyHostKeyDNS under ssh_config. systemd-resolve breaks this. Here is a detailed blog article that covers the issue in depth: https://moss.sh/name-resolution-issue-systemd-resolved/ -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+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 1670959] Re: systemd-resolved using 100% CPU
For other souls facing this "Medium" issue, a hammer-ish workaround that works for me: 1) Run: apt-get install cpulimit 2) edit /lib/systemd/system/systemd-resolved.service: 2a) Comment out: #Type=notify 2b) Replace line (may want to remove the -k to let cpulimit throttle it): #ExecStart=!!/lib/systemd/systemd-resolved ExecStart=!!/usr/bin/cpulimit -f -q -k -l 50 -- /lib/systemd/systemd-resolved 3) Run: systemctl daemon-reload systemctl restart systemd-resolved -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU Status in dnsmasq package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: [Triage Notes] "Incomplete" in dnsmasq: may be a valid bug, but developers cannot make progress until someone can provide steps to reproduce. See comment 55. [Original Description] Sometimes systemd-resolved process is using 100% CPU. After a while it changes back to normal. It happens usually after connecting to the (wifi) network, like starting the OS. strace output: sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0", 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], msg_flags=0}, 0) = 81 sendmsg(3, {msg_name(0)=NULL, msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n", 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188 epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1 clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0 recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53 recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0", 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) = 53 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 getrandom("\365I", 2, GRND_NONBLOCK)= 2 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 getrandom("\203;", 2, GRND_NONBLOCK)= 2 clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0 open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18 connect(18, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, u64=94565471566608}}) = 0 write(18, "\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0", 53) = 53 clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0 clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0 epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0 close(18) = 0 journalctl output: Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS queries reached (max: 150) As you can see, I would use it together with dnsmasq. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Wed Mar 8 08:20:18 2017 MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1 ProcEnviron: LANGUAGE=en_US:en
[Touch-packages] [Bug 1812356] Re: AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low
Triaged as a systemd issue per https://gitlab.freedesktop.org/libinput/libinput/issues/232 ** Package changed: linux (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: libinput (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided => Medium -- 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/1812356 Title: AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low Status in libinput package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/232 --- While moving pointer (cursor) using Touchpad, vertical movement is very slow and short (= less velocity and less acceleration compared to horizontal axis). Horizontal movement is fine. So, when circle is drawn on the Touchpad, the pointer moves in oval shape. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1168 F pulseaudio /dev/snd/controlC0: user 1168 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 10:10:35 2019 HibernationDevice: RESUME=UUID=5eb56af0-cec9-43d4-b84a-46d561cecb30 InstallationDate: Installed on 2019-01-13 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80N4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a791b794-48c2-47fb-b2e6-11085529d9ba ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2016 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN71WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN71WW:bd08/03/2016:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD: dmi.product.family: IDEAPAD dmi.product.name: 80N4 dmi.product.version: Lenovo Yoga 500-14IBD dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1812356/+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 1812014] Re: keyboard not responding after suspend after some time
Thanks. The best guess I can make is a problem in upower or the Nvidia driver (comment #15). Those are definitely performance problems (100% CPU for no obvious reason) and could well explain why the keyboard stops responding. Maybe next we need to look at the system log in detail... If you can recover from the problem without rebooting then please run: journalctl -b0 > curlog.txt If you have to reboot to recover from the problem then please run this after rebooting: journalctl -b-1 > prevlog.txt and send us the resulting log file. ** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1812095] Re: console login loop after entering username followed by RETURN
I'm experiencing the same issue. Here is the output from /var/log/auth.log after attempting to login: Jan 30 17:52:39 computername login[3483]: pam_unix(login:auth): conversation failed Jan 30 17:52:39 computername login[3483]: pam_unix(login:auth): auth could not identify password for [username] Jan 30 17:52:42 computername login[3483]: FAILED LOGIN (1) on '/dev/tty2' FOR 'UNKNOWN', Authentication failure Jan 30 17:52:42 computername login[3483]: pam_securetty(login:auth): cannot determine username Jan 30 17:52:46 computername login[3483]: FAILED LOGIN (2) on '/dev/tty2' FOR 'UNKNOWN', Error in service module Jan 30 17:52:46 computername login[3483]: pam_securetty(login:auth): cannot determine username Jan 30 17:52:49 computername login[3483]: FAILED LOGIN (3) on '/dev/tty2' FOR 'UNKNOWN', Error in service module -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1812356] [NEW] AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low
You have been subscribed to a public bug: https://gitlab.freedesktop.org/libinput/libinput/issues/232 --- While moving pointer (cursor) using Touchpad, vertical movement is very slow and short (= less velocity and less acceleration compared to horizontal axis). Horizontal movement is fine. So, when circle is drawn on the Touchpad, the pointer moves in oval shape. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1168 F pulseaudio /dev/snd/controlC0: user 1168 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jan 18 10:10:35 2019 HibernationDevice: RESUME=UUID=5eb56af0-cec9-43d4-b84a-46d561cecb30 InstallationDate: Installed on 2019-01-13 (4 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80N4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=a791b794-48c2-47fb-b2e6-11085529d9ba ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2016 dmi.bios.vendor: Lenovo dmi.bios.version: BDCN71WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lenovo Yoga 500-14IBD dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 500-14IBD dmi.modalias: dmi:bvnLenovo:bvrBDCN71WW:bd08/03/2016:svnLENOVO:pn80N4:pvrLenovoYoga500-14IBD:rvnLENOVO:rnLenovoYoga500-14IBD:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga500-14IBD: dmi.product.family: IDEAPAD dmi.product.name: 80N4 dmi.product.version: Lenovo Yoga 500-14IBD dmi.sys.vendor: LENOVO ** Affects: libinput (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: Triaged ** Tags: amd64 apport-bug bionic -- AlpsPS/2 ALPS GlidePoint vertical pointer speed is very low https://bugs.launchpad.net/bugs/1812356 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd 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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
** Changed in: pulseaudio (Ubuntu Bionic) Status: New => In Progress ** Changed in: pulseaudio (Ubuntu Cosmic) Status: New => Confirmed -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Bionic: In Progress Status in pulseaudio source package in Cosmic: Confirmed Status in pulseaudio source package in Disco: Confirmed Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1385292] Re: can't rename files in nautilus
Distro: Ubuntu 16.04.4 LTS xenial GNOME nautilus 3.14.3 I have the same problem that I can not rename files and folders by pressing the F2 key. I work on a laptop and I have connected an external keyboard (Microsoft Wired Keyboard 400 with number pad). I Identify that if the "Num Lock" key is active, the bug is executed, but if the "Num Lock" key is disabled the bug is no longer present. ** Attachment added: "Keyboard bloqnum" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1385292/+attachment/5234453/+files/keyboard.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1385292 Title: can't rename files in nautilus Status in ibus: Unknown Status in ibus package in Ubuntu: Triaged Bug description: sometimes can't rename files with F2 button. It is higlight changing, but nothing gonna happen, it is not responding ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu15 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Fri Oct 24 17:48:33 2014 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2014-10-24 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1385292/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Basically what I did was backport all the required Arctis stuff that seemed to be required in order to get my lucid sound headphones working. -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Bionic: New Status in pulseaudio source package in Cosmic: New Status in pulseaudio source package in Disco: Confirmed Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
Can someone on this bug please test the packages from https://launchpad.net/~chiluk/+archive/ubuntu/lp1758736 on Bionic? -- 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/1758736 Title: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback Status in pulseaudio package in Ubuntu: Confirmed Status in pulseaudio source package in Bionic: New Status in pulseaudio source package in Cosmic: New Status in pulseaudio source package in Disco: Confirmed Bug description: There is not stereo playback only mono playback ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio /dev/snd/controlC1: kaj1755 F pulseaudio /dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio /dev/snd/controlC0: kaj1755 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Mar 25 21:30:50 2018 InstallationDate: Installed on 2018-03-08 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7 Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R06ET35W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FMS2AV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460 dmi.product.name: 20FMS2AV00 dmi.product.version: ThinkPad T460 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+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 1787495] Re: no explanation for the events in the networkd-dispatcher manpage
This bug was fixed in the package networkd-dispatcher - 2.0-2 --- networkd-dispatcher (2.0-2) unstable; urgency=medium * Refer to networkctl(1) in networkd-dispatcher(8) text (LP: #1787495) -- Julian Andres Klode Wed, 30 Jan 2019 16:01:34 +0100 ** Changed in: networkd-dispatcher (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1787495 Title: no explanation for the events in the networkd-dispatcher manpage Status in networkd-dispatcher package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in networkd-dispatcher source package in Bionic: In Progress Status in systemd source package in Bionic: Triaged Status in networkd-dispatcher source package in Cosmic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] networkd-dispatcher supports four hook directories: $ ls /usr/lib/networkd-dispatcher/ dormant.d no-carrier.d off.d routable.d $ The manpage does not define what these hooks mean. 'routable' and 'no-carrier' are self-explanatory, but it's not at all clear what 'dormant' vs 'off' mean. It's not at all clear what events one should expect to see as part of device bring-up. This needs to be better documented. [Test case] Check that it networkd-dispatcher(8) it's documented in networkctl(1), and that networkctl(1) documents it [Regression potential] If user updates networkd-dispatcher before systemd, they get the reference to networkctl(1) in networkd-dispatcher(8), but won't find any related text in there... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1787495/+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 1801439] Re: Unable to add software sources via the software-properties-qt
** Tags removed: rls-dd-incoming ** Tags added: rls-dd-notfixing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1801439 Title: Unable to add software sources via the software-properties-qt Status in software-properties package in Ubuntu: Triaged Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1801439/+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 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
I don't know if Balint considers me release management but fixing this in an SRU is fine with me. -- 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/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Confirmed Status in apt package in Debian: New Bug description: This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+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 1789642] Re: Nautilus highlights new filename without focusing input field.
I believe it triggerede when I right clicked on a image in a browser and i selected save image as but it works now. -- 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/1789642 Title: Nautilus highlights new filename without focusing input field. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Opening nautilus in order to save picture from e.g. browser does so the name of the new file is highlighted but the focus is not on the input field. I expect when the name is highlighted that it is also focused. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 14:18:08 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-03-08 (173 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+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 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1813581 Title: gpgme1.0 ftbfs in 18.04 LTS Status in gpgme1.0 package in Ubuntu: New Status in gpgme1.0 source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html gpgme1.0 ftbfs. * Start testing of TofuInfoTest * Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 7.3.0) PASS : TofuInfoTest::initTestCase() PASS : TofuInfoTest::testTofuNull() PASS : TofuInfoTest::testTofuInfo() PASS : TofuInfoTest::testTofuSignCount() PASS : TofuInfoTest::testTofuKeyList() PASS : TofuInfoTest::testTofuPolicy() FAIL! : TofuInfoTest::testTofuConflict() 'sig.validity() == Signature::Marginal' returned FALSE. () Loc: [t-tofuinfo.cpp(458)] PASS : TofuInfoTest::cleanupTestCase() Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms * Finished testing of TofuInfoTest * FAIL: t-tofuinfo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+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 1813568] Re: coreutils ftbfs in 18.04 LTS
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1813568 Title: coreutils ftbfs in 18.04 LTS Status in coreutils package in Ubuntu: New Status in coreutils source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html coreutils ftbfs. ../build-aux/test-driver: line 107: 31009 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-rwlock1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1813568/+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 1813580] Re: findutils ftbfs in 18.04 LTS
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to findutils in Ubuntu. https://bugs.launchpad.net/bugs/1813580 Title: findutils ftbfs in 18.04 LTS Status in findutils package in Ubuntu: New Status in findutils source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html findutils ftbfs. ../build-aux/test-driver: line 107: 20659 Aborted (core dumped) "$@" > $log_file 2>&1 FAIL: test-rwlock1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1813580/+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 1813584] Re: libidn ftbfs in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted libidn into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libidn/1.33-2.1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libidn (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Released Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. It is important that packages in stable series are buildable at all times in case security updates need to be prepared. [Test Case] Make sure the package builds successfully. [Regression Potential] Should be relatively minimal. The same change was present in Ubuntu since cosmic, so we would already get mentions of regressions previously. [Original Description] = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+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 1813586] Re: libnih ftbfs in 18.04 LTS (arm64 only)
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnih in Ubuntu. https://bugs.launchpad.net/bugs/1813586 Title: libnih ftbfs in 18.04 LTS (arm64 only) Status in libnih package in Ubuntu: New Status in libnih source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libnih ftbfs on arm64. make check-TESTS make[4]: Entering directory '/<>/nih-dbus' make[5]: Entering directory '/<>/nih-dbus' PASS: test_dbus_error 1 - nih_dbus_error_raise PASS: test_dbus_error 2 - nih_dbus_error_raise_printf make[5]: *** Deleting file 'test_dbus_connection.log' Makefile:1239: recipe for target 'test_dbus_connection.log' failed make[5]: *** [test_dbus_connection.log] Terminated E: Caught signal ‘Terminated’: terminating immediately debian/rules:31: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Terminated make[2]: *** wait: No child processes. Stop. make[2]: *** Waiting for unfinished jobs make[2]: *** wait: No child processes. Stop. Makefile:1211: recipe for target 'check-TESTS' failed make[4]: *** [check-TESTS] Terminated Makefile:1326: recipe for target 'check-am' failed make[3]: *** [check-am] Terminated debian/rules:6: recipe for target 'build-arch' failed make: *** [build-arch] Terminated Build killed with signal TERM after 150 minutes of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1813586/+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 1789642] Re: Nautilus highlights new filename without focusing input field.
So could you describe the steps you were following to trigger the issue your reported? -- 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/1789642 Title: Nautilus highlights new filename without focusing input field. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Opening nautilus in order to save picture from e.g. browser does so the name of the new file is highlighted but the focus is not on the input field. I expect when the name is highlighted that it is also focused. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 14:18:08 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-03-08 (173 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
> * still showing WARNING:Failed to connect to lvmetad. Falling back to device scanning. That is NOT the defining symptom of the bug. This message would always be shown. The question is whether there is an unreasonable and unnecessary boot delay after the message is displayed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I also want to confirm that the sound has come back when I upgraded the kernel to 4.19.18. I am using Mint 19.1 and by default it didn't work. Warning! I first upgraded to 4.20.5 but it didn't work. I switched to the 4.19 and it magically started to work! And on a side note it works better than the stock windows version. The sound card was making weird static noises when used on Windows 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+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 1753572] Re: cpio in Busybox 1.27 ingnores "unsafe links"
Creating image now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1753572 Title: cpio in Busybox 1.27 ingnores "unsafe links" Status in busybox package in Ubuntu: Fix Released Status in debirf package in Ubuntu: Confirmed Status in busybox source package in Bionic: In Progress Status in debirf source package in Bionic: Confirmed Status in busybox source package in Cosmic: Fix Released Status in debirf source package in Cosmic: Confirmed Bug description: Description:Ubuntu Bionic Beaver (development branch) Release:18.04 busybox: Installed: 1:1.27.2-2ubuntu3 Candidate: 1:1.27.2-2ubuntu3 3) Expected my CPIO archive to be fully extracted with proper symlinks Command: unxz < /rootfs.cxz | cpio -i 4) 'Unsafe' symlinks were ignored such as: sbin/init -> /lib/systemd/systemd With the broken 1.27 sbin/init does not get created at all and my debirf initrd fails to load/boot properly. 1.22 from Xenial works. GNU Cpio also works. It looks like 1.28 adds an env var to override this behavior: libarchive: do not extract unsafe symlinks unless $EXTRACT_UNSAFE_SYMLINKS=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1753572/+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 1803601] Re: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable
I have the same problem and it looks like this issue brings my server in real trouble. I deactivated this services completly now and hope it helps. -- 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/1803601 Title: motd-news.service scheduled even when /etc/update-motd.d/50-motd-news is not executable Status in base-files package in Ubuntu: New Bug description: update-motd(5) says: Executable scripts in /etc/update-motd.d/* are executed by pam_motd(8) as the root user at each login, and this information is concatenated in /run/motd.dynamic. The order of script execu‐ tion is determined by the run-parts(8) --lsbsysinit option (basically alphabetical order, with a few caveats). So sysadmins are used to "chmod -x" motd fragments from /etc/update- motd.d/ to prevent their execution. When doing so for /etc/update- motd.d/50-motd-news, I noticed that motd-news.timer was still trying to execute the motd-news.service unit which then logged a failure: systemd[3704]: motd-news.service: Failed to execute command: Permission denied systemd[3704]: motd-news.service: Failed at step EXEC spawning /etc/update-motd.d/50-motd-news: Permission denied systemd[1]: motd-news.service: Main process exited, code=exited, status=203/EXEC systemd[1]: motd-news.service: Failed with result 'exit-code'. systemd[1]: Failed to start Message of the Day. The motd-news.service unit looks like this: $ systemctl cat motd-news.service # /lib/systemd/system/motd-news.service [Unit] Description=Message of the Day After=network-online.target Documentation=man:update-motd(8) [Service] Type=oneshot ExecStart=/etc/update-motd.d/50-motd-news --force This problem was observed on a Bionic system: $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy base-files base-files: Installed: 10.1ubuntu2.3 Candidate: 10.1ubuntu2.3 Version table: *** 10.1ubuntu2.3 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 10.1ubuntu2.2 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 10.1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages But the problem also exist in Disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1803601/+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
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
¡Gracias! El mié., 30 ene. 2019 a las 12:21, José Enrique (<1773...@bugs.launchpad.net>) escribió: > Una cosa. > Chequea el hardware en ocasiones equipos antiguos rinden mal o no rinden > con el 18 > Si es un equipo moderno sin problemas. > También puedes valorar en utilizar escritorios más ligeros con equipos > antiguos XCFE Xubuntu o LXDE Lubuntu. > Yo con un equipo de 2007 y 2 GB ejecuto Xubuntu 18-04 sin problemas. Y en > un Netbook con 1 Giga Lubuntu. > Recuerda que Lubuntu ya no va a crear versiones de 32 bit a partir de la 18 > 04. > Saludos > > El mar., 29 ene. 2019 22:50, juan angel Mora <1773...@bugs.launchpad.net> > escribió: > > > La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5 > > LTS. > > Vale la pena actualizarla? > > Graacias > > > > > > El mar., 29 ene. 2019 a las 22:30, José Enrique (< > > 1773...@bugs.launchpad.net>) > > escribió: > > > > > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que > no > > > quieras perder y actualizarla a 18-04. > > > Funcionar funciona pero estás a punto de que no se actualice más, y > > puedes > > > tener problemas de seguridad, ojo se trata de una actualización > > importante, > > > que debes realizar, seguramente en dos pasos, dos actualizaciones > > > parciales. Primero a 16 y luego a 18-04. > > > Configura el gestor de actualizaciones a versiones LTS, no obstante la > > > 18-04 tiene soporte para 10 años. > > > Saludos > > > > > > El mar., 29 ene. 2019 22:15, juan angel Mora < > 1773...@bugs.launchpad.net > > > > > > escribió: > > > > > > > Muchas gracias por la información. > > > > Si no es mucho consultarte, a veces cuando me pide actualizaciones > las > > > hago > > > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero > > actualizar a > > > > la ultima versión 16. y no lo hago por miedo a que se me desbarate > > todo > > > > de nuevo, cual es tu consejo? > > > > Un saludo > > > > > > > > > > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray () > > > > escribió: > > > > > > > > > The upload of systemd that was purported to fix this bug report was > > > > > superseded by a security update of systemd so the fix is no longer > > > > > available. > > > > > > > > > > ** Changed in: systemd (Ubuntu Bionic) > > > > >Status: Fix Committed => Triaged > > > > > > > > > > -- > > > > > You received this bug notification because you are subscribed to a > > > > > duplicate bug report (1787843). > > > > > https://bugs.launchpad.net/bugs/1773859 > > > > > > > > > > Title: > > > > > upgrades to 18.04 fail > > > > > > > > > > Status in systemd package in Ubuntu: > > > > > Fix Released > > > > > Status in systemd-shim package in Ubuntu: > > > > > Won't Fix > > > > > Status in systemd source package in Bionic: > > > > > Triaged > > > > > Status in systemd-shim source package in Bionic: > > > > > Won't Fix > > > > > Status in systemd source package in Cosmic: > > > > > Fix Released > > > > > Status in systemd-shim source package in Cosmic: > > > > > Won't Fix > > > > > > > > > > Bug description: > > > > > [Impact] > > > > > > > > > >* Some systems fail to upgrade due to conflicts between systemd > > and > > > > > the (now removed from the archive) systemd-shim / upstart. > > > > > > > > > >* Instead of trying to work out what's the problem in ordering / > > > > > removal of diverts, ensure that systemd is never unpacked whilst > > > > > systemd-shim/upstart are still on disk. Thus declare conflicts > > > against > > > > > systemd-shim/upstart packages in systemd package. > > > > > > > > > > [Test Case] > > > > > > > > > >* monitor drop-off of upgrades with below reported problem > > > > > > > > > >* Check that it is possible to upgrade to bionic's > libpam-systemd > > > > > from xenial with systemd-shim installed on xenial, ie. > > > > > > > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > > > > lxc exec test-shim-upgrade > > > > > apt update > > > > > apt install systemd-shim > > > > > wget > > > > > > > > > > > > > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > > > > apt install ./systemd-shim_10-3_amd64.deb > > > > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > > > > apt update > > > > > apt install systemd > > > > > > > > > > this currently passes, however, systemd-shim remains installed. > It > > > > > should be removed instead. Apt install systemd should have lines > > like > > > > > this: > > > > > > > > > > The following packages will be REMOVED: > > > > > systemd-shim > > > > > ... > > > > > Removing 'diversion of > > > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service > to > > > > > > > > > > > > > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > > > > by systemd-shim' > > > > > ... > > > > > > > > > > > > > > > [Regression Potential] > > > > > > > > > >* systemd-shim/upstart are both removed
Re: [Touch-packages] [Bug 1813845] Re: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left
Thank you very much for your advice. I will try and see what I can do. Regards, Gaetano -- Inviato da Libero Mail per Android mercoledì, 30 gennaio 2019, 10:22AM +01:00 da Sebastien Bacher seb...@ubuntu.com : >the problem is that your disk has no free space, you should make some >and try again > >** Changed in: openssl (Ubuntu) > Importance: Undecided => Low > >** Changed in: openssl (Ubuntu) > Status: New => Invalid > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1813845 > >Title: > package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: > unable to make backup symlink for > './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on > device > >Status in openssl package in Ubuntu: > Invalid > >Bug description: > Segnalazione crash: si è verificato un problema durante > l'installazione del software. Pacchetto: ubuntu-mobile-icons > 14.04 +16.04.20180326-0 ubuntu1 > > ProblemType: Package > DistroRelease: Ubuntu 14.04 > Package: libssl-doc 1.0.1f-1ubuntu2.21 > ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 > Uname: Linux 3.13.0-101-generic i686 > ApportVersion: 2.14.1-0ubuntu3.21 > Architecture: i386 > Date: Tue Jan 29 23:52:10 2019 > Dependencies: > > DuplicateSignature: package:libssl-doc:1.0.1f-1ubuntu2.21:unable to make >backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space >left on device > ErrorMessage: unable to make backup symlink for >'./usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device > InstallationDate: Installed on 2014-06-28 (1676 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) > PackageArchitecture: all > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.5 > apt 1.2.29ubuntu0.1 > SourcePackage: openssl > Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: >unable to make backup symlink for >'./usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device > UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1813845/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1813845 Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device Status in openssl package in Ubuntu: Invalid Bug description: Segnalazione crash: si è verificato un problema durante l'installazione del software. Pacchetto: ubuntu-mobile-icons 14.04+16.04.20180326-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl-doc 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:52:10 2019 Dependencies: DuplicateSignature: package:libssl-doc:1.0.1f-1ubuntu2.21:unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device ErrorMessage: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssl Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1813845/+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
Re: [Touch-packages] [Bug 1813846] Re: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25
Thank you very much for your advice. I will try and see what I can do. Regards, Gaetano -- Inviato da Libero Mail per Android mercoledì, 30 gennaio 2019, 03:19AM +01:00 da Daniel van Vugt daniel.van.v...@canonical.com : >It appears you might have briefly run out of disk space. > >Please try running this command: > > sudo apt install --reinstall ubuntu-mobile-icons > >and send us the output from that command. > >** Changed in: ubuntu-themes (Ubuntu) > Status: New => Incomplete > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1813846 > >Title: > package ubuntu-mobile-icons (not installed) failed to install/upgrade: > error creating symbolic link './usr/share/icons/ubuntu- > mobile/status/scalable/nm-signal-25.svg': No space left on device > >Status in ubuntu-themes package in Ubuntu: > Incomplete > >Bug description: > Si è verificato un problema durante l'installazione del software. > Pacchetto: gnome-icon-theme 3.12.0-1ubuntu3 > > ProblemType: Package > DistroRelease: Ubuntu 14.04 > Package: ubuntu-mobile-icons (not installed) > ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 > Uname: Linux 3.13.0-101-generic i686 > ApportVersion: 2.14.1-0ubuntu3.21 > Architecture: i386 > Date: Tue Jan 29 23:54:21 2019 > DuplicateSignature: package:ubuntu-mobile-icons:(not installed):error >creating symbolic link >'./usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space >left on device > ErrorMessage: error creating symbolic link >'./usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space >left on device > InstallationDate: Installed on 2014-06-28 (1676 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) > RelatedPackageVersions: > dpkg 1.18.4ubuntu1.5 > apt 1.2.29ubuntu0.1 > SourcePackage: ubuntu-themes > Title: package ubuntu-mobile-icons (not installed) failed to >install/upgrade: error creating symbolic link >'./usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space >left on device > UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1813846/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1813846 Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu- mobile/status/scalable/nm-signal-25.svg': No space left on device Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: Si è verificato un problema durante l'installazione del software. Pacchetto: gnome-icon-theme 3.12.0-1ubuntu3 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-mobile-icons (not installed) ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:54:21 2019 DuplicateSignature: package:ubuntu-mobile-icons:(not installed):error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device ErrorMessage: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: ubuntu-themes Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1813846/+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 1164016] Re: restore type-ahead find
Yeah right. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1809827] Re: --add-file broken in bionic
This bug was fixed in the package tar - 1.29b-2ubuntu0.1 --- tar (1.29b-2ubuntu0.1) bionic; urgency=medium * debian/patches/git_add_file.patch: - backport "Fix the --add-file option." upstream commit, thanks Martin Vogt (lp: #1809827) -- Sebastien Bacher Mon, 21 Jan 2019 17:38:11 +0100 ** Changed in: tar (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1809827 Title: --add-file broken in bionic Status in tar package in Ubuntu: Fix Released Status in tar source package in Bionic: Fix Released Status in tar package in Fedora: Unknown Bug description: same error like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0 * Impact tar supplied in bionic has --add-file option broken. * Test case Steps to Reproduce: 1. echo >a.txt 2. echo >b.txt 3. tar cf a.tar a.txt 4. tar rf a.tar --add-file=b.txt Actual results: tar: unhandled positional option 0 * Regression potential The changes are around an option which isn't working so no much regression potential there, check that other options still work though Is likely fixed by this: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1809827/+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 1809827] Update Released
The verification of the Stable Release Update for tar has completed successfully and the package has now been 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 tar in Ubuntu. https://bugs.launchpad.net/bugs/1809827 Title: --add-file broken in bionic Status in tar package in Ubuntu: Fix Released Status in tar source package in Bionic: Fix Committed Status in tar package in Fedora: Unknown Bug description: same error like this one: https://bugzilla.redhat.com/show_bug.cgi?id=1436030#c0 * Impact tar supplied in bionic has --add-file option broken. * Test case Steps to Reproduce: 1. echo >a.txt 2. echo >b.txt 3. tar cf a.tar a.txt 4. tar rf a.tar --add-file=b.txt Actual results: tar: unhandled positional option 0 * Regression potential The changes are around an option which isn't working so no much regression potential there, check that other options still work though Is likely fixed by this: http://git.savannah.gnu.org/cgit/tar.git/commit/?id=3a283cfe9f8f1f127e8dc5597a5ea1d249985a54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1809827/+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 1164016] Re: restore type-ahead find
Please read https://www.ubuntu.com/community/code-of-conduct -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1789642] Re: Nautilus highlights new filename without focusing input field.
I followed your suggestion and it works as expected in both chrome and firefox. -- 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/1789642 Title: Nautilus highlights new filename without focusing input field. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Opening nautilus in order to save picture from e.g. browser does so the name of the new file is highlighted but the focus is not on the input field. I expect when the name is highlighted that it is also focused. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 14:18:08 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-03-08 (173 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+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 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Installed system using latest bionic daily, which contains ubiquity 18.04.14.11. There is no /etc/initramfs-tools/conf.d/resume file created, and grepping for RESUME= setting, there are none hardcoded. ** 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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
Re: [Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
On 29/01/2019 13.44, Marc Pignat wrote: > If I understand well, ubiquity is the installer, so the iso image must > be tested. > > Where can I find a 18.04-daily iso image? As I understand it (might be wrong), the normal daily ISO is not the correct one to test with because it is not based on the /proposed/ repository. The correct procedure is documented here: https://wiki.ubuntu.com/Testing/EnableProposed#Installation_testing_using_-proposed Looks like there are no normal ISOs available. Thus there is a requirement to set up a netboot environment, which is documented here: https://help.ubuntu.com/community/Installation/Netboot However, the expected location for the /proposed/ netboot installer does not have recent enough version to include this fix: http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/main/installer-amd64/ Maybe it will appear there at a later time... Janne Snabb sn...@epipe.com -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+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 1787495] Re: no explanation for the events in the networkd-dispatcher manpage
** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: networkd-dispatcher (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: networkd-dispatcher (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Cosmic) Status: New => Fix Released ** Changed in: networkd-dispatcher (Ubuntu Cosmic) Status: New => In Progress ** Changed in: networkd-dispatcher (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Status: New => Triaged ** Description changed: + [Impact] networkd-dispatcher supports four hook directories: $ ls /usr/lib/networkd-dispatcher/ dormant.d no-carrier.d off.d routable.d $ The manpage does not define what these hooks mean. 'routable' and 'no- carrier' are self-explanatory, but it's not at all clear what 'dormant' vs 'off' mean. It's not at all clear what events one should expect to see as part of device bring-up. This needs to be better documented. + + [Test case] + Check that it networkd-dispatcher(8) it's documented in networkctl(1), and that networkctl(1) documents it + + [Regression potential] + If user updates networkd-dispatcher before systemd, they get the reference to networkctl(1) in networkd-dispatcher(8), but won't find any related text in there... -- 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/1787495 Title: no explanation for the events in the networkd-dispatcher manpage Status in networkd-dispatcher package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in networkd-dispatcher source package in Bionic: In Progress Status in systemd source package in Bionic: Triaged Status in networkd-dispatcher source package in Cosmic: In Progress Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] networkd-dispatcher supports four hook directories: $ ls /usr/lib/networkd-dispatcher/ dormant.d no-carrier.d off.d routable.d $ The manpage does not define what these hooks mean. 'routable' and 'no-carrier' are self-explanatory, but it's not at all clear what 'dormant' vs 'off' mean. It's not at all clear what events one should expect to see as part of device bring-up. This needs to be better documented. [Test case] Check that it networkd-dispatcher(8) it's documented in networkctl(1), and that networkctl(1) documents it [Regression potential] If user updates networkd-dispatcher before systemd, they get the reference to networkctl(1) in networkd-dispatcher(8), but won't find any related text in there... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1787495/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
Although this problem is easy to fix once you know what to do, I don't know if it should be only "Medium" importance because the impact is massive: no DNS is available. If you're not technically inclined enough to know to go poking around /etc/resolv.conf if DNS breaks, you would never be able to figure out what was wrong with your system and you can't search the internet to find a solution... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in network-manager package in Ubuntu: Confirmed Status in ppp package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Confirmed Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1778946/+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 1164016] Re: restore type-ahead find
@Javier if by "they" you mean the upstream Nautilus developers, that's right: they don't even understand it's a bug. The Gnome development team, or at least the part responsible for Naitulus, has proven many times to be a bunch of idiots. For the last several years, they have taken many design decision that completely destroyed the usability of their software. But the Ubuntu team seems to be more intelligent. In the past they have patched several things in Nautilus and perhaps other Gnome products to fix the idiotic mistakes made upstream. This was one of them. Now the question is: does Ubuntu consider it worth to keep doing the patching to fix the upstream idiocies in Nautilus? If that is the case, then this, among other things, needs to be fixed. Again. If not, if they are going to rely on the upstream developers fixing upstream issues, then they must drop Nautilus in favor of some other file manager that is not maintained by a bunch of idiots. -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1812095] Re: console login loop after entering username followed by RETURN
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: shadow (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
Coudl you restart the gvfs service with that command $ GVFS_DEBUG=1 /usr/lib/gvfs/gvfsd -r then try to access the Documents folder and share the output for gvfsd on the bug? ** Changed in: libimobiledevice (Ubuntu) Importance: Undecided => Low ** Changed in: libimobiledevice (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: Incomplete Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1787460] Re: Unattended upgrades removed linux-image-generic
bionic: before (1.6.6..) Removing unused kernel packages: linux-headers-generic linux-image-generic after (1.6.8): Removing unused kernel packages: linux-headers-generic and just to verify, if you install dkms: No packages found that can be upgraded unattended and no pending auto-removals (the headers won't get removed then) ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- 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/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 60.02*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+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 1787460] Re: Unattended upgrades removed linux-image-generic
(in practice the headers do not matter - if you have dkms installed, it will keep the headers alive) -- 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/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+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 1787460] Re: Unattended upgrades removed linux-image-generic
cosmic: before (1.7.0ubu...) Removing unused kernel packages: linux-headers-generic linux-image-generic after (1.7.2): Removing unused kernel packages: linux-headers-generic That does the job well enough, even if the headers end up being removed in this particular test case. -- 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/1787460 Title: Unattended upgrades removed linux-image-generic Status in apt package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-hwe package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in linux-meta source package in Xenial: New Status in linux-meta-hwe source package in Xenial: New Status in apt source package in Bionic: Fix Committed Status in linux-meta source package in Bionic: New Status in linux-meta-hwe source package in Bionic: New Status in apt source package in Cosmic: Fix Committed Status in linux-meta source package in Cosmic: New Status in linux-meta-hwe source package in Cosmic: New Status in apt source package in Disco: Fix Released Status in linux-meta source package in Disco: Triaged Status in linux-meta-hwe source package in Disco: Triaged Bug description: [Impact] If a user accidentally removed linux-generic, unattended-upgrades will also autoremove linux-image-generic, leaving them without kernel upgrades. [Test Case] 1. Remove all reverse dependencies of linux-image-generic 2. Mark linux-image-generic as automatically installed 3. Run unattended-upgrades -v --dry-run --debug to ensure that linux-image-generic is not removed (after verifying that it is, with old apt) [Regression potential] This adds two regular expressions to the list of packages that must not be automatically removed. As such, the only possible regression is that some packages starting with linux-image, not containing any dots, are not removed [Original bug report] On a fairly fresh install of 18.04 with no modifications whatsoever to the unattended-upgrades configuration, it decided to remove linux-image-generic which also removed linux-modules-extra which caused sound drivers to disappear, etc. The relative snippet from /var/log/unattended-upgrades/unattended- upgrades.log is: 2018-08-15 06:18:00,048 INFO Starting unattended upgrades script 2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic 2018-08-15 06:18:01,552 INFO Removing unused kernel packages: linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic linux-headers-4.15.0-32 2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic package(s) because it would also remove the following packages which should be kept in this step: libxml2 linux-image-4.15.0-32-generic linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic linux-image-generic 2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic 2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 linux-image-generic 2018-08-15 06:18:10,300 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2018-08-15 06:18:39,238 INFO All upgrades installed 2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: linux-image-generic linux-modules-extra-4.15.0-32-generic 2018-08-15 06:18:42,818 INFO Packages that are kept back: ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: unattended-upgrades 1.1ubuntu1.18.04.5 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 16 13:17:30 2018 InstallationDate: Installed on 2018-07-24 (23 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787460/+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 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
We checked what actually is the backend that the "ssh-add -c" is trying to reach. First we thought that should be the ssh-agent spawned for gnome-keyring-daemon [1] In PS that is visible as: 1 1000 4029 1 20 0 656132 15860 - SLl ? 0:24 /usr/bin/gnome-keyring-daemon --daemonize --login 0 1000 26372 4029 20 0 11304 3696 - S? 0:00 \_ /usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh Note: there is also another ssh-agent running: 0 1000 4047 4036 20 0 568216 14944 poll_s Sl+ tty2 0:00 \_ /usr/lib/gnome-session/gnome-session-binary --session=ubuntu 1 1000 4146 4047 20 0 11304 320 - Ss ? 0:00 \_ /usr/bin/ssh-agent /usr/bin/im-launch env GNOME_SHELL_SESSION_MODE=ubuntu gnome-session --session=ubuntu That binary is the one of the openssh package that we have proven before to work fine.: $ dpkg -S /usr/bin/ssh-agent openssh-client: /usr/bin/ssh-agent But it is interesting that it uses -a /run/user/1000/keyring/.ssh But the env var is actually different (no . in the filename): $ echo $SSH_AUTH_SOCK /run/user/1000/keyring/ssh But look at the ownership of the socket that we found in the env var: $ sudo lsof +fg /run/user/1000/keyring/ssh COMMANDPIDUSER FD TYPE FILE-FLAG DEVICE SIZE/OFF NODE NAME gnome-key 4029 paelzer 14u unix RW,ND,0x8 0x910ac4316800 0t0 130189 /run/user/1000/keyring/ssh type=STREAM So while there is a real /usr/bin/ssh-agent running the actual socket that the env variable points to is actually owned by gnome-keyring process. Above we have proven that with a classic ssh-agent it works fine (comment #6). The bug task for openssh is invalid for now due to that. Maybe the gnome-keyring backend doesn't even have the -c feature [1] doesn't list it - then it would be a feature request there. But in any case we need to re-triage that at gnome-keyring, so that is the package I'm adding a bug task for. [1]: https://wiki.gnome.org/Projects/GnomeKeyring/Ssh -- 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/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in gnome-keyring package in Ubuntu: New Status in openssh package in Ubuntu: Invalid Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1812247/+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 1770706] Re: openvswitch with ifupdown after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => 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/1770706 Title: openvswitch with ifupdown after reboot Status in systemd package in Ubuntu: Confirmed Bug description: Recently I needed to install OVS on fresh ubuntu 18.04. 1). # lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 2). # apt-cache policy openvswitch-switch openvswitch-switch: Installed: 2.9.0-0ubuntu1 Candidate: 2.9.0-0ubuntu1 Version table: *** 2.9.0-0ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status 3). OVS configured after reboot. 4). OVS was not configured after reboot. After this actions: - remove netplan.io - install ifupdown - install openvswitch-switch - add verified ovs related statements to /etc/network/interfaces - reboot I got this in journal: мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1328]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1368]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1392]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru ovs-vsctl[1424]: ovs|2|db_ctl_base|ERR|unix:/var/run/openvswitch/db.sock: database connection failed (No such file or directory) мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:26:49 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. мая 11 16:28:42 host2.lab.atlantis.ru ovs-vsctl[2041]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2091]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:28:43 host2.lab.atlantis.ru ovs-vsctl[2137]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:28:43 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. мая 11 16:30:05 host2.lab.atlantis.ru ovs-vsctl[2243]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:30:06 host2.lab.atlantis.ru ovs-vsctl[2293]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:30:07 host2.lab.atlantis.ru ovs-vsctl[2339]: ovs|2|db_ctl_base|ERR|no bridge named br0 мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: networking.service: Failed with result 'exit-code'. мая 11 16:30:07 host2.lab.atlantis.ru systemd[1]: Failed to start Raise network interfaces. Problem was fixed after the following changes to unit files: # diff /lib/systemd/system/ovsdb-server.service /etc/systemd/system/ovsdb-server.service 4c4 < Before=network.target network.service --- > Before=network.target networking.service # diff /lib/systemd/system/ovs-vswitchd.service /etc/systemd/system/ovs-vswitchd.service 4c4 < Before=network.target network.service --- > Before=network.target networking.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770706/+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 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
** Also affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in gnome-keyring package in Ubuntu: New Status in openssh package in Ubuntu: Invalid Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1812247/+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 1164016] Re: restore type-ahead find
They do not think to fix It :( -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
Same here, with 18.10 and iPhone on 12.1.3 with, iPhone 6s, SE and 7 When accessing "Documents" I get "Unhandled Lockdown error (-2) The other folder seems mounted ok,but when I go to the DCIM folder, I get this error: "Unhandled error message: The name:1.2260 was not provided by any .services files" On commandprompt,: # ideviceinfo ERROR: Could not connect to lockdownd, error code -2 but ideviceinfo -s gives a correct overwieuw of the iPhone config # idevicepair pair ERROR: Device 89799a11f6208c97b1638a3fe33919f9 returned unhandled error code -5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+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 1164016] Re: restore type-ahead find
Why the fuck hasn't this been reopened yet?? -- 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/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1811120] Re: Backport auth.conf.d
The autopkgtests ran successfully and included a check for this, so this is verified. ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-don verification-done-bionic verification-done-cosmic ** Tags removed: verification-don ** Tags added: verification-done -- 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/1811120 Title: Backport auth.conf.d Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in apt source package in Xenial: Triaged Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Committed Status in apt source package in Disco: Fix Released Bug description: [Impact] Backport auth.conf.d support to allow specifying per-repository authentication data in separate files, so packages can setup authenticated repositories. [Regression potential] We ignore errors from opening auth.conf.d files, so regressions can only occur when parsing a file fails, in which case apt would exit with an error. [Test case] The test suite provides autopkgtests for auth.conf.d which creates an auth.conf.d file and checks that it is successfully used; so we can check if those passed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1811120/+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 1813952] [NEW] Audio Playback problem - Speakers only work if Headphones are also plugged in
Public bug reported: Ubuntu 18.04 Linux dadspc 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux pulseaudio v 11.1 $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k4.15.0-44-generic. Audio has been working fine until this morning when "some" update occurred on my Ubuntu desktop system. I found that I was NOT getting any audio out of my speakers. I also found in SOUND SETTINGS that for OUTPUT I only had listed: Digital Output (S/PDIF) - Built-in Audio" Headphones - Built-in audio Next, I plugged in my headphones to my Desktop and when I did that: I started hearing Audio out of my Speakers AND in my Headphones ! AND... in SOUND SETTINGS Line Out - Built-in Audio appeared ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bmullan2599 F pulseaudio /dev/snd/pcmC0D0c: bmullan2599 F...m pulseaudio /dev/snd/pcmC0D0p: bmullan2599 F...m pulseaudio /dev/snd/controlC0: bmullan2599 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:52:10 2019 InstallationDate: Installed on 2018-11-06 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_Type: None of the above Title: [HDA-Intel - HDA ATI SB, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2901 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 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.:bvr2901:bd05/04/2016:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FXR2.0:rvrRev1.xx: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.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Description changed: Ubuntu 18.04 Linux dadspc 4.15.0-44-generic #47-Ubuntu SMP Mon Jan 14 11:26:59 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux pulseaudio v 11.1 $ cat /proc/asound/version Advanced Linux Sound Architecture Driver Version k4.15.0-44-generic. Audio has been working fine until this morning when "some" update occurred on my Ubuntu desktop system. - I found that I wasn NOT getting any audio out of my speakers. + I found that I was NOT getting any audio out of my speakers. I also found in SOUND SETTINGS that for OUTPUT I only had listed: Digital Output (S/PDIF) - Built-in Audio" Headphones - Built-in audio Next, I plugged in my headphones to my Desktop and when I did that: I started hearing Audio out of my Speakers AND in my Headphones ! AND... in SOUND SETTINGS Line Out - Built-in Audio appeared ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: bmullan2599 F pulseaudio - /dev/snd/pcmC0D0c: bmullan2599 F...m pulseaudio - /dev/snd/pcmC0D0p: bmullan2599 F...m pulseaudio - /dev/snd/controlC0: bmullan2599 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: bmullan2599 F pulseaudio + /dev/snd/pcmC0D0c: bmullan2599 F...m pulseaudio + /dev/snd/pcmC0D0p: bmullan2599 F...m pulseaudio + /dev/snd/controlC0: bmullan2599 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:52:10 2019 InstallationDate: Installed on 2018-11-06 (84 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver
[Touch-packages] [Bug 1787495] Re: no explanation for the events in the networkd-dispatcher manpage
** Changed in: networkd-dispatcher (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1787495 Title: no explanation for the events in the networkd-dispatcher manpage Status in networkd-dispatcher package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Bug description: networkd-dispatcher supports four hook directories: $ ls /usr/lib/networkd-dispatcher/ dormant.d no-carrier.d off.d routable.d $ The manpage does not define what these hooks mean. 'routable' and 'no-carrier' are self-explanatory, but it's not at all clear what 'dormant' vs 'off' mean. It's not at all clear what events one should expect to see as part of device bring-up. This needs to be better documented. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/networkd-dispatcher/+bug/1787495/+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 1666203] Re: pam_tty_audit failed in pam_open_session
** Changed in: pam (Debian) Status: Unknown => New -- 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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Status in pam package in Debian: New Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1666203] Re: pam_tty_audit failed in pam_open_session
** Tags added: trusty xen ** Tags removed: xen ** Tags added: cosmic disco xenial -- 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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Status in pam package in Debian: New Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1666203] Re: pam_tty_audit failed in pam_open_session
** Bug watch added: Debian Bug tracker #778664 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778664 ** Also affects: pam (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778664 Importance: Unknown Status: Unknown -- 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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Status in pam package in Debian: Unknown Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1666203] Re: pam_tty_audit failed in pam_open_session
** Tags added: bionic -- 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/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Status in pam package in Debian: Unknown Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
>From the apt side: The patch in #12 looks correct - we want people to put the keys in trusted.gpg.d like this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Status in apt-setup source package in Bionic: New Status in gnupg source package in Bionic: New Status in gnupg2 source package in Bionic: New Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1813584] Re: libidn ftbfs in 18.04 LTS
Actually, I'll just use the fix from cosmic since it's a backport then and the package already had cosmic+disco for testing. My original fix was related to actually re-introducing the removed link-pthread patch that has been dropped previously. I considered that way of fixing actually better as it was only introducing -Wl,--no-as-needed for the two failing tests. But well, since the other fix is already in the devel series, I don't see a reason why not to proceed the other way. Uploaded to bionic Unapproved. ** Description changed: + [Impact] + according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. + It is important that packages in stable series are buildable at all + times in case security updates need to be prepared. + + [Test Case] + + Make sure the package builds successfully. + + [Regression Potential] + + Should be relatively minimal. The same change was present in Ubuntu + since cosmic, so we would already get mentions of regressions + previously. + + [Original Description] + = -GNU Libidn 1.33: lib/gltests/test-suite.log + GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 ** Changed in: libidn (Ubuntu) Status: In Progress => Fix Released ** Changed in: libidn (Ubuntu Cosmic) Status: In Progress => Fix Released ** Changed in: libidn (Ubuntu Cosmic) Assignee: Łukasz Zemczak (sil2100) => (unassigned) ** Changed in: libidn (Ubuntu) Assignee: Łukasz Zemczak (sil2100) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libidn source package in Cosmic: Fix Released Bug description: [Impact] according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. It is important that packages in stable series are buildable at all times in case security updates need to be prepared. [Test Case] Make sure the package builds successfully. [Regression Potential] Should be relatively minimal. The same change was present in Ubuntu since cosmic, so we would already get mentions of regressions previously. [Original Description] = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
** Changed in: lxd Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: Fix Released Status in systemd: Fix Released Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). === Workaround === $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1813622/+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 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
Removing block-proposed, although lxd fix is in flight, I have reverted the relevant commit for now in the systemd in disco-proposed. The intention is to still ship systemd in disco with that patch in place, and thus fixed lxd is still needed in v3.9+ and v3.0 series. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: Fix Released Status in systemd: Fix Released Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). === Workaround === $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1813622/+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 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
** Changed in: systemd (Ubuntu Disco) Status: Fix Released => Fix Committed -- 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/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+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 1805178] Re: Apparmor should include letsencrypt directory for Slapd
** Changed in: openldap (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1805178 Title: Apparmor should include letsencrypt directory for Slapd Status in openldap package in Ubuntu: New Bug description: Apparmor denies access to /etc/letsencrypt for slapd, which is confusing for users trying to secure ldap with Letsencrypt in a stock configuration. The fix is inserting the following line in /etc/apparmor.d/usr.sbin.slapd: /etc/letsencrypt/** r, and then refreshing the profile: # apparmor_parser -vr usr.sbin.slapd This line should simply be included. tarek : ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1805178/+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 1813918] Re: Installing package graphicsmagick* is removing CUPS in Mint18.3
** Package changed: libreoffice (Ubuntu) => graphicsmagick (Ubuntu) ** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1813918 Title: Installing package graphicsmagick* is removing CUPS in Mint18.3 Status in cups package in Ubuntu: New Status in graphicsmagick package in Ubuntu: New Bug description: sudo apt-get install --assume-yes graphicsmagick* Reading package lists... Done Building dependency tree Reading state information... Done Note, selecting 'graphicsmagick' for glob 'graphicsmagick*' Note, selecting 'graphicsmagick-libmagick-dev-compat' for glob 'graphicsmagick*' Note, selecting 'graphicsmagick-imagemagick-compat' for glob 'graphicsmagick*' Note, selecting 'graphicsmagick-dbg' for glob 'graphicsmagick*' Note, selecting 'graphicsmagick-doc' for glob 'graphicsmagick*' Note, selecting 'graphicsmagick-im-compat' for glob 'graphicsmagick*' graphicsmagick is already the newest version (1.3.23-1ubuntu0.1). graphicsmagick-dbg is already the newest version (1.3.23-1ubuntu0.1). graphicsmagick-libmagick-dev-compat is already the newest version (1.3.23-1ubuntu0.1). The following packages will be REMOVED: cups cups-filters imagemagick The following NEW packages will be installed: graphicsmagick-imagemagick-compat 0 upgraded, 1 newly installed, 3 to remove and 405 not upgraded. Need to get 0 B/5,826 B of archives. After this operation, 2,472 kB disk space will be freed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813918/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Disco) Assignee: Victor Tapia (vtapia) => Dimitri John Ledkov (xnox) -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) [Regression potential] Minimal. Originally, one failing mount point blocked the processing of the rest due to how the return codes were handled for every line in /proc/self/mountinfo. This patch removes this "dependency" and keeps the failure local to the affected mount point, allowing the rest to be processed normally. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10874 Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3 [Original Description] netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service
[Touch-packages] [Bug 1809709] Re: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit st
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ibus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1809709 Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 Status in ibus package in Ubuntu: Confirmed Bug description: I removed python and it caused the gui to go, so i installed gnome through tty1 and then later installed ubuntu-desktop . After this all these happened ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 20:56:01 2018 DuplicateSignature: package:gir1.2-ibus-1.0:amd64:1.5.17-3ubuntu4 Removing gir1.2-ibus-1.0:amd64 (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: 6: /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: py3clean: not found dpkg: error processing package gir1.2-ibus-1.0:amd64 (--remove): installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2018-12-17 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ibus Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1809709/+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 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Disco) Assignee: Daniel Axtens (daxtens) => Dimitri John Ledkov (xnox) -- 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/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1812760/+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 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** Changed in: systemd (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: systemd (Ubuntu Disco) Assignee: Dan Streetman (ddstreet) => Dimitri John Ledkov (xnox) -- 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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: New Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Trusty: Invalid Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
** Changed in: systemd (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 apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: New Status in systemd: Fix Released Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Committed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). === Workaround === $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1813622/+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 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
I think we should for now mask the test in britney. I linked a MP for that on the bug. => https://code.launchpad.net/~paelzer/britney/hints-ubuntu-mask-livecd-rootfs-disco/+merge/362445 ** Branch linked: lp:~paelzer/britney/hints-ubuntu-mask-livecd-rootfs- disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: Invalid Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Confirmed Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
before 18.04.2 is released, which means before feb 7th unless it's delayed thanks for verifying! -- 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/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
Before using libegl-mesa0 from bionic-proposed: $ apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 Version table: *** 18.0.5-0ubuntu0~18.04.1 100 100 /var/lib/dpkg/status $ cat main.c main() { eglGetProcAddress("egl148546488546404"); } $ gcc main.c -lEGL $ ./a.out Segmentation fault (core dumped) After upgrading libegl-mesa0 to bionic-proposed: $ apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.2.2-0ubuntu1~18.04.1 Candidate: 18.2.2-0ubuntu1~18.04.1 Version table: *** 18.2.2-0ubuntu1~18.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-proposed/main arm64 Packages 100 /var/lib/dpkg/status 18.0.5-0ubuntu0~18.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages $ ./a.out No crash So I can confirm that the issues is fixed in bionic-proposed. -- 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/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
When it is expected libegl-mesa0 to move from bionic-proposed to bionic- updates ? thanks! -- 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/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+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 1789642] Re: Nautilus highlights new filename without focusing input field.
Thank you for your bug report. The issue you describe seems to be rather with the fileselector widget and not the filemanager application, reassigning to gtk. Could you describe exact steps to trigger the issue? Trying those - open firefox - hit ctrl-S - type the filename is replaced, which means the focus is correctly on the text entry ... what happens in your case? ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (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/1789642 Title: Nautilus highlights new filename without focusing input field. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Opening nautilus in order to save picture from e.g. browser does so the name of the new file is highlighted but the focus is not on the input field. I expect when the name is highlighted that it is also focused. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 14:18:08 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-03-08 (173 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+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 1782599] Re: Search field in "Open file" dialog loses focus after every character typed
*** This bug is a duplicate of bug 1592177 *** https://bugs.launchpad.net/bugs/1592177 The issue is with the gtk fileselector and not the filemanager, it's already reported/known as bug #1592177 ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1592177 Focus drops from search input in GtkFileChooserDialog after first character, which stops searching (broken behaviour) -- 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/1782599 Title: Search field in "Open file" dialog loses focus after every character typed Status in gtk+3.0 package in Ubuntu: New Bug description: When we click in the magnifier icon next to the "Open" button in a (system provided) "Open File" dialog to search for some file by name, after each character typed, if there are any search results, the search field loses focus to the list view of the results. The correct behavior would be to maintain focus until we stopped typing or even manually changed focus. I've added a screencast of the problem as an attachment. PS: I have no idea if this dialog is provided by nautilus, so I'm not marking it here. Also, I tried using xprop to get the correct package, but it only reports the application using it, not the one providing. --- $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1782599/+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 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
** Changed in: systemd (Ubuntu) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: New Status in systemd: Fix Released Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: In Progress Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). === Workaround === $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1813622/+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 1782599] [NEW] Search field in "Open file" dialog loses focus after every character typed
You have been subscribed to a public bug: When we click in the magnifier icon next to the "Open" button in a (system provided) "Open File" dialog to search for some file by name, after each character typed, if there are any search results, the search field loses focus to the list view of the results. The correct behavior would be to maintain focus until we stopped typing or even manually changed focus. I've added a screencast of the problem as an attachment. PS: I have no idea if this dialog is provided by nautilus, so I'm not marking it here. Also, I tried using xprop to get the correct package, but it only reports the application using it, not the one providing. --- $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New -- Search field in "Open file" dialog loses focus after every character typed https://bugs.launchpad.net/bugs/1782599 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1789642] [NEW] Nautilus highlights new filename without focusing input field.
You have been subscribed to a public bug: Opening nautilus in order to save picture from e.g. browser does so the name of the new file is highlighted but the focus is not on the input field. I expect when the name is highlighted that it is also focused. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 29 14:18:08 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'" b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false' b'org.gnome.nautilus.desktop' b'volumes-visible' b'false' InstallationDate: Installed on 2018-03-08 (173 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago) usr_lib_nautilus: ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug bionic -- Nautilus highlights new filename without focusing input field. https://bugs.launchpad.net/bugs/1789642 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 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 1813896] Re: Monitors stopped working
The only recent changes to Ubuntu 18.04 I can see that might be relevant are: gnome-shell - 7 January 2019 linux (kernel) - A couple of times this month There have been no changes to Xorg or mutter anyway... ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1813896 Title: Monitors stopped working Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Latitude E7470 laptop with a docking station and two external monitors. I made a system update yesterday (without restart), and I tried to work today. When the laptop lid is laid off, all displays are black and stays that way. When it's open, it works fine. If I lock the computer, the displays are going black again. Also, I cannot restart the system, it just hangs. The only solution is to switch off the system is holding the power button, then booting up again, with the laptop screen open. My other colleagues with similar configurations have the same issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:58:12 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc] InstallationDate: Installed on 2018-09-24 (128 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=fd65107a-71e9-4b89-9f1e-e90f34670b9f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813896/+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 1813845] Re: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on
the problem is that your disk has no free space, you should make some and try again ** Changed in: openssl (Ubuntu) Importance: Undecided => Low ** Changed in: openssl (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1813845 Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device Status in openssl package in Ubuntu: Invalid Bug description: Segnalazione crash: si è verificato un problema durante l'installazione del software. Pacchetto: ubuntu-mobile-icons 14.04+16.04.20180326-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl-doc 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:52:10 2019 Dependencies: DuplicateSignature: package:libssl-doc:1.0.1f-1ubuntu2.21:unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device ErrorMessage: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssl Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1813845/+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 1813896] [NEW] Monitors stopped working
Public bug reported: I have a Dell Latitude E7470 laptop with a docking station and two external monitors. I made a system update yesterday (without restart), and I tried to work today. When the laptop lid is laid off, all displays are black and stays that way. When it's open, it works fine. If I lock the computer, the displays are going black again. Also, I cannot restart the system, it just hangs. The only solution is to switch off the system is holding the power button, then booting up again, with the laptop screen open. My other colleagues with similar configurations have the same issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:58:12 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc] InstallationDate: Installed on 2018-09-24 (128 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=fd65107a-71e9-4b89-9f1e-e90f34670b9f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813896 Title: Monitors stopped working Status in xorg package in Ubuntu: New Bug description: I have a Dell Latitude E7470 laptop with a docking station and two external monitors. I made a system update yesterday (without restart), and I tried to work today. When the laptop lid is laid off, all displays are black and stays that way. When it's open, it works fine. If I lock the computer, the displays are going black again. Also, I cannot restart the system, it just hangs. The only solution is to switch off the system is holding the power button, then booting up again, with the laptop screen open. My other colleagues with similar configurations have the same issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 30 09:58:12 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc] InstallationDate: Installed on 2018-09-24 (128 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E7470 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=fd65107a-71e9-4b89-9f1e-e90f34670b9f ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3