[Touch-packages] [Bug 2026621] [NEW] package linux-image-5.15.0-1039-aws 5.15.0-1039.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: do-release-upgrade 20 to 22. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1039-aws 5.15.0-1039.44 ProcVersionSignature: Ubuntu 5.15.0-1039.44~20.04.1-aws 5.15.99 Uname: Linux 5.15.0-1039-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jul 8 12:32:23 2023 Ec2AMI: ami-0781f4e7be922a91f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-1039-aws 5.15.0-1039.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-07-08 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package ec2-images jammy need-duplicate-check -- 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/2026621 Title: package linux-image-5.15.0-1039-aws 5.15.0-1039.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: do-release-upgrade 20 to 22. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1039-aws 5.15.0-1039.44 ProcVersionSignature: Ubuntu 5.15.0-1039.44~20.04.1-aws 5.15.99 Uname: Linux 5.15.0-1039-aws x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jul 8 12:32:23 2023 Ec2AMI: ami-0781f4e7be922a91f Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1c Ec2InstanceType: t2.micro Ec2Kernel: unavailable Ec2Ramdisk: unavailable ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: initramfs-tools Title: package linux-image-5.15.0-1039-aws 5.15.0-1039.44 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to jammy on 2023-07-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2026621/+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 2024009] [NEW] [PATCH] systemd-resolved can't follow more than 8 CNAMEs
Public bug reported: On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only follows 8 CNAME redirections maximum. So when using a service like Azure Virtual Desktop that has between 9 and 12 redirections, name resolution fails. $ host client.wvd.microsoft.com Host client.wvd.microsoft.com not found: 2(SERVFAIL) $ resolvectl query client.wvd.microsoft.com client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net' On the other hand it's working fine on Ubuntu 20.04 because CNAME loop limit has been raised from 8 to 16. $ host client.wvd.microsoft.com client.wvd.microsoft.com is an alias for client.privatelink-global.wvd.microsoft.com. client.privatelink-global.wvd.microsoft.com is an alias for client.privatelink.wvd.microsoft.com. client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com. rdweb.wvd.microsoft.com is an alias for rdweb.privatelink-global.wvd.microsoft.com. rdweb.privatelink-global.wvd.microsoft.com is an alias for rdweb.privatelink.wvd.microsoft.com. rdweb.privatelink.wvd.microsoft.com is an alias for rdweb-prod-geo.trafficmanager.net. rdweb-prod-geo.trafficmanager.net is an alias for mrs-chnor1c101-rdweb-prod.wvd-ase-chnor1c101-prod.p.azurewebsites.net. mrs-chnor1c101-rdweb-prod.wvd-ase-chnor1c101-prod.p.azurewebsites.net is an alias for waws-prod-zrh-63daa049.sip.p.azurewebsites.windows.net. waws-prod-zrh-63daa049.sip.p.azurewebsites.windows.net is an alias for waws-prod-zrh-63daa049.cloudapp.net. waws-prod-zrh-63daa049.cloudapp.net has address 51.107.69.35 Here's a quick fix that raises the max CNAME limit from 8 to 16 like it is in Ubuntu 22.04, it fixes the problem for me. Best regards, Vincent. --- systemd-245.4.ORIG/src/resolve/resolved-dns-query.c 2023-06-15 16:58:25.454156663 +0200 +++ systemd-245.4/src/resolve/resolved-dns-query.c 2023-06-01 14:30:09.0 +0200 @@ -10,7 +10,7 @@ #include "resolved-etc-hosts.h" #include "string-util.h" -#define CNAME_MAX 8 +#define CNAME_MAX 16 #define QUERIES_MAX 2048 #define AUXILIARY_QUERIES_MAX 64 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: systemd 249.11-0ubuntu3.9 [modified: usr/lib/sysctl.d/50-default.conf] ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jun 15 16:53:19 2023 InstallationDate: Installed on 2022-11-22 (205 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' MachineType: Dell Inc. Latitude 5591 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-42-generic root=/dev/mapper/AmadeUbuntu22-root ro apparmor=1 security=apparmor audit=1 acpi_rev_override load_nvme=YES nouveau.modeset=0 dis_ucode_ldr quiet splash RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 1.25 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.25.0 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.25.0:bd11/21/2022:br1.25:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr:sku0819: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. modified.conffile..etc.cron.daily.apport: [deleted] mtime.conffile..etc.systemd.journald.conf: 2022-11-22T13:40:37.558934 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Tags removed: jammy ** Tags added: focal -- 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/2024009 Title: [PATCH] systemd-resolved can't follow more than 8 CNAMEs Status in systemd package in Ubuntu: New Bug description: On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only follows 8 CNAME redirections maximum. So when using a service like Azure Virtual Desktop that has between 9 and 12 redirections, name resolution fails. $ host client.wvd.microsoft.com Host client.wvd.microsoft.com not found: 2(SERVFAIL) $ resolvectl query client.wvd.microsoft.com client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net' On the other hand it's working fine on Ubuntu 20.04 because CNAME loop limit has been raised from 8 to 16. $ host client.wvd.microsoft.com client.wvd.microsoft.com is an alias
[Touch-packages] [Bug 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy
Hi Benjamin, chrony reads "/usr/share/zoneinfo/right/UTC" to determine when will the next leap second occur and what is the current offset between TAI and UTC. So I’ll have to add "tzdata-legacy" to the list of dependencies. Cheers, Vincent -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/2008076 Title: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-legacy Status in chrony package in Ubuntu: Fix Committed Status in moment-timezone.js package in Ubuntu: Fix Committed Status in rdate package in Ubuntu: Fix Committed Status in tzdata package in Ubuntu: Fix Committed Bug description: The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in /usr/share/zoneinfo/. The tzdata package converts the configured posix/* and right/* timezones to their unprefixed variant on every package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin"). Drop /usr/share/zoneinfo/right from tzdata and move /usr/share/zoneinfo/right into separate tzdata-legacy package. ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu- devel/2023-January/042405.html Two packages need to be adjusted: * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-legacy Following packages were checked and do not need to be touched: Only in source code documentation and/or tests suite: * mariadb * mariadb-10.6 Copies of tz soure code: * rust-chrono-tz (in tz) * udm (in tzdatabase) * r-cran-tzdb (in inst/tzdata) * pike8.0 (in lib/modules/Calendar.pmod/tzdata) Referencing only /usr/share/zoneinfo/posixrules: * manpages-l10n * libdatetime-timezone-perl * asterisk * mozjs102 * mozjs78 * thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/2008076/+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 1990397] [NEW] Screen goes blank after a few seconds of inactivity
Public bug reported: Despite "Never" being selected in the "Screen Blank" section of the "Power" pane of gnome settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-1ubuntu1) ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 21 10:16:49 2022 DistUpgraded: 2022-08-02 22:49:48,677 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/515.65.01, 5.15.0-43-generic, x86_64: installed nvidia/515.65.01, 5.19.0-15-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-15-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [10de:249c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GA104M [GeForce RTX 3080 Mobile / Max-Q 8GB/16GB] [17aa:22e4] InstallationDate: Installed on 2022-05-05 (138 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20Y5CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgubuntu-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-08-03 (49 days ago) dmi.bios.date: 08/26/2022 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N40ET37W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20Y5CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0T76461 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.16 dmi.modalias: dmi:bvnLENOVO:bvrN40ET37W(1.19):bd08/26/2022:br1.19:efr1.16:svnLENOVO:pn20Y5CTO1WW:pvrThinkPadX1ExtremeGen4i:rvnLENOVO:rn20Y5CTO1WW:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20Y5_BU_Think_FM_ThinkPadX1ExtremeGen4i: dmi.product.family: ThinkPad X1 Extreme Gen 4i dmi.product.name: 20Y5CTO1WW dmi.product.sku: LENOVO_MT_20Y5_BU_Think_FM_ThinkPad X1 Extreme Gen 4i dmi.product.version: ThinkPad X1 Extreme Gen 4i dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.1.7-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.1.7-0ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic possible-manual-nvidia-install regression reproducible 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/1990397 Title: Screen goes blank after a few seconds of inactivity Status in xorg package in Ubuntu: New Bug description: Despite "Never" being selected in the "Screen Blank" section of the "Power" pane of gnome settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-1ubun
[Touch-packages] [Bug 1940996]
(In reply to eggert from comment #24) > Sure, feel free to file it as a new bug. Bug 29560. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
What about attachment 10674 ("This test case silently returns the wrong answer"), with the pattern "^(11+)\\1+$|^1?$" and the string "1"? Should it be regarded as part of Bug#17356 or another bug? This case seems quite different from Bug#10844 and Bug#17356. Unless the intent is to group all the bugs about regexp involving backreferences giving a wrong answer[*] (in which case Bug#10844 and Bug#17356 should be regarded as duplicates to each other), I think that this should be a new bug. [*] as opposed to a crash like in this bug 11053. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
(In reply to eggert from comment #20) > OK, so in that case how about if we update Bug#17356 by (1) saying it is no > longer a duplicate of Bug#11053 (as we've fixed the latter but not the > former), and (2) reopening Bug#17536? If I understand you correctly, that > would match the symptoms you describe. Yes, I think that this is the best solution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
Sorry, actually both regbug.c and rebug2.c fail as they return the exit status 1 (with my usual configuration, my prompt shows any non-zero exit status, but this is not the case of the machine on which I had done the test, so that I missed the failure initially): vinc17@gcc92:~$ ./regbug vinc17@gcc92:~$ echo $? 1 vinc17@gcc92:~$ ./rebug2 vinc17@gcc92:~$ echo $? 1 However, in the test from Paolo Bonzini's bug report (comment 0), grep no longer crashes (while it still crashes with glibc 2.34, which does not have the fix). regbug.c is derived from the attachment in Bug#17356 (as said in comment 5). I've tested this original testcase: with glibc 2.34 on x86_64, it crashes (segmentation fault); with glibc 2.35 on riscv64 (host gcc92), it outputs "no match (incorrect)". So it seems that the fix mentioned in comment 13 fixed the crashes (which was the initial bug report), but not the misbehavior. Now, with these new details, is it still OK to regard this bug as fixed and that the misbehavior (rebug.c from Bug#17356; regbug.c and rebug2.c from this bug) is actually a new bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
(In reply to eggert from comment #15) > glibc bug 11053 is fixed, Shouldn't this bug be resolved as fixed, then? > but Debian bug 884075 is not fixed. Perhaps a better match for > Debian bug 884075 is glibc bug 10844. It seems different. With Debian bug 884075, the "|^1?$" part is important (it yields the incorrect output, even though this part isn't matched), and there is nothing like that in glibc bug 10844: vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$|^1?$' 111 vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$' vinc17@gcc92:~$ Note that for the first command, nothing is colored in "111", i.e. the line is output as appeared to be matched, but no matches are shown by colors. As a comparison, with ten 1s instead of eleven, the line is output and the ten 1s are colored. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
This could be simplified a bit: vinc17@gcc92:~$ echo 111 | grep --color=auto -E '^(11+)\1+$|^$' 111 (nothing colored). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: Fix Released Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1940996]
(In reply to cvs-com...@gcc.gnu.org from comment #13) > The master branch has been updated by Paul Eggert : > > https://sourceware.org/git/gitweb.cgi?p=glibc.git; > h=0b5ca7c3e551e5502f3be3b06453324fe8604e82 > > commit 0b5ca7c3e551e5502f3be3b06453324fe8604e82 > Author: Paul Eggert > Date: Tue Sep 21 07:47:45 2021 -0700 [...] > * Fix glibc bug 11053. What is the status of this bug? The comment says that it is fixed, and I could check on an Ubuntu 22.04.1 LTS machine with libc6 2.35-0ubuntu3.1 that regbug.c and rebug2.c no longer fail, but the result is still incorrect with the grep example from Debian bug 884075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884075 vinc17@gcc92:~$ echo 111 | grep -E '^(11+)\1+$|^1?$' ; echo $? 111 0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1940996 Title: test failure - test-regex Status in grep: In Progress Status in grep package in Ubuntu: New Bug description: 'test-regex' fails when building grep against glibc 2.34. Per commentary from grep upstream at https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069, the test failure can be attributed to skew between the glibc built-in regex and the one that is found in the grep source code. To manage notifications about this bug go to: https://bugs.launchpad.net/grep/+bug/1940996/+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 1983529] Re: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)
*** This bug is a duplicate of bug 1979113 *** https://bugs.launchpad.net/bugs/1979113 This was fixed by installing wireplumber, so I think it's a duplicate of https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1979113 ** This bug has been marked a duplicate of bug 1979113 Kinetic sound disappeared after today updates -- 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/1983529 Title: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4) Status in alsa-driver package in Ubuntu: New Bug description: Not sure if it's relevant, but there are some errors in dmesg: $ sudo dmesg | grep audio [ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 15.643730] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Because of those ABI warnings, I tried building the latest mainline kernel from source, and the ABI warnings went away, but I still have no sound. $ sudo dmesg | grep audio # On latest upstream kernel [ 17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: l
[Touch-packages] [Bug 1983529] Re: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4)
I am able to play sound with aplay when pipewire is not running, so I don't think it's a hardware/firmware issue. -- 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/1983529 Title: No sound after upgrade to prerelease Kinetic (Thinkpad X1E Gen 4) Status in alsa-driver package in Ubuntu: New Bug description: Not sure if it's relevant, but there are some errors in dmesg: $ sudo dmesg | grep audio [ 14.290226] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 14.440430] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 14.445129] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 14.445811] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 14.445861] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 14.448966] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 15.467232] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 15.467478] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 15.467479] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 15.467484] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 15.478062] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.478066] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.478068] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.478073] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 15.584074] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 15.584079] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.584080] sof-audio-pci-intel-tgl :00:1f.3: warn: FW ABI is more recent than kernel [ 15.591457] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:18:0 [ 15.591461] sof-audio-pci-intel-tgl :00:1f.3: warn: topology ABI is more recent than kernel [ 15.624250] sof-audio-pci-intel-tgl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 15.643720] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 15.643726] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 15.643727] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 15.643728] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 15.643729] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 15.643730] snd_hda_codec_realtek ehdaudio0D0: Mic=0x19 Because of those ABI warnings, I tried building the latest mainline kernel from source, and the ABI warnings went away, but I still have no sound. $ sudo dmesg | grep audio # On latest upstream kernel [ 17.519958] snd_hda_intel :01:00.1: Handle vga_switcheroo audio client [ 17.804900] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 17.805661] sof-audio-pci-intel-tgl :00:1f.3: Digital mics found on Skylake+ platform, using SOF driver [ 17.806225] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 [ 17.806265] sof-audio-pci-intel-tgl :00:1f.3: init of i915 and HDMI codec failed [ 17.808071] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode [ 21.844005] sof-audio-pci-intel-tgl :00:1f.3: codec #2 probe error, ret: -5 [ 21.844263] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 1 [ 21.844264] sof-audio-pci-intel-tgl :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [ 21.844267] sof-audio-pci-intel-tgl :00:1f.3: DMICs detected in NHLT tables: 2 [ 21.853970] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.853971] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.853979] sof-audio-pci-intel-tgl :00:1f.3: unknown sof_ext_man header type 3 size 0x30 [ 21.961252] sof-audio-pci-intel-tgl :00:1f.3: Firmware info: version 2:1:1-3964a [ 21.961255] sof-audio-pci-intel-tgl :00:1f.3: Firmware: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.967719] sof-audio-pci-intel-tgl :00:1f.3: Topology: ABI 3:21:0 Kernel ABI 3:21:0 [ 21.979145] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC287: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker [ 21.979147] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 21.979148] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/
[Touch-packages] [Bug 1931024] Re: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550]
Same problem today: LUKS FS and stuck at boot on initramfs due to a kernel upgrade, I've no knoledge to solve this easily and going to re- format everything. Fortunately, a live usb allows me to recover my data. -- 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/1931024 Title: BOOT fails on UEFI with 100MB initrd.img [Dell XPS 9550] Status in initramfs-tools package in Ubuntu: Confirmed Bug description: I've been working with a user for the last 2 days on a failure to even start the kernel when installing 20.04 or 21.04 (possibly other releases) with a UEFI boot. System is Dell XPS 9550 amd64 with Ubuntu Budgie. The symptom is that after GRUB successfully loads the kernel into RAM, it fails to return from loading the initrd into RAM. This was proved by adding guard 'echo' and 'sleep' around each stage n grub.cfg. After much investigation since this seemed initially related to a LUKS install I noticed the initrd.img files generated with MODULES=most are 105MB. Most of that is unneeded firmware and other files so I changed to MODULES=dep. Resulting initrd.img's are around 55MB. System then boots correctly. This looks like a possible issue with the UEFI on these XPS models but as initrd.img sizes get ridiculously large this is likely to hit more systems and users. For several years I carry optimisation patches to initramfs-tools that don't add most firmwares except those specifically required (certainly not adding AMD GPU firmware when system has only Intel or Nvidia GPUs - and visa versa) My initrd.img's are a hybrid of MODULES=dep and result in less than 20MB. My recommendation is to add optimisations to initramfs-tools or adopt MODULES=dep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931024/+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 1964283] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: not sure what it does ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 8 19:04:30 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- 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/1964283 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: not sure what it does ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Mar 8 19:04:30 2022 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1964283/+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 1915238] Re: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ
Any news? Note that under Debian, even a reboot will not update the file. So I currently have: -rw-r--r-- 1 195453 2021-10-19 01:46:43 /etc/ssl/certs/ca-certificates.crt -rw-r--r-- 1 200061 2019-09-20 11:53:51 /var/spool/postfix/etc/ssl/certs/ca-certificates.crt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1915238 Title: warning: /var/spool/postfix/etc/ssl/certs/ca-certificates.crt and /etc/ssl/certs/ca-certificates.crt differ Status in ca-certificates package in Ubuntu: New Status in postfix package in Ubuntu: Triaged Status in postfix package in Debian: New Bug description: Postfix package doesn't utilize update-ca-certificate's hooks mechanism. By simply copying certs from /etc/ssl/certs/ca- certificates.crt to /var/spool/postfix/etc/ssl/certs/ca- certificates.crt, this warning and potential security issues could be avoided. Something like this would be a start: $ cat /etc/ca-certificates/update.d/postfix #!/bin/bash if [ -e /var/spool/postfix/etc/ssl/certs/ca-certificates.crt ]; then echo "Updating postfix chrooted certs" cp /etc/ssl/certs/ca-certificates.crt /var/spool/postfix/etc/ssl/certs/ca-certificates.crt systemctl reload postfix fi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1915238/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
I see the fix in -proposed for Focal, will that also be released? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Released Status in procps source package in Hirsute: Fix Released Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-focal verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Fix Released Status in procps source package in Focal: Fix Committed Status in procps source package in Groovy: Fix Committed Status in procps source package in Hirsute: Fix Committed Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
I've tested focal/groovy/hirsute and the changes seem to work. --- root@9ff1aefae2e8:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal root@9ff1aefae2e8:/tmp# sysctl -V sysctl from procps-ng UNKNOWN root@9ff1aefae2e8:/tmp# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii procps 2:3.3.16-1ubuntu2.2 amd64/proc file system utilities root@9ff1aefae2e8:/tmp# echo "kernel.shmmax = 17179869184" > shmmax.conf root@9ff1aefae2e8:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 root@9ff1aefae2e8:/tmp# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@9ff1aefae2e8:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 root@9ff1aefae2e8:/tmp# useradd test root@9ff1aefae2e8:/tmp# su test $ bash test@9ff1aefae2e8:/tmp$ echo "kernel.shmmax = 17179869184" > shmmax.conf test@9ff1aefae2e8:/tmp$ sysctl -e -p shmmax.conf; echo $? sysctl: permission denied on key "kernel.shmmax", ignoring 0 test@9ff1aefae2e8:/tmp$ echo "-kernel.shmmax = 17179869184" > shmmax.conf test@9ff1aefae2e8:/tmp$ sysctl -e -p shmmax.conf; echo $? sysctl: permission denied on key "kernel.shmmax", ignoring 0 --- root@bc651792633c:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bc651792633c:/tmp# sysctl -V sysctl from procps-ng 3.3.16 root@bc651792633c:/tmp# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii procps 2:3.3.16-5ubuntu2.2 amd64/proc file system utilities root@bc651792633c:/tmp# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bc651792633c:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 root@bc651792633c:/tmp# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bc651792633c:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 root@bc651792633c:/tmp# useradd test root@bc651792633c:/tmp# su test $ bash test@bc651792633c:/tmp$ echo "kernel.shmmax = 17179869184" > shmmax.conf test@bc651792633c:/tmp$ sysctl -e -p shmmax.conf; echo $? sysctl: permission denied on key "kernel.shmmax", ignoring 0 test@bc651792633c:/tmp$ echo "-kernel.shmmax = 17179869184" > shmmax.conf test@bc651792633c:/tmp$ sysctl -e -p shmmax.conf; echo $? sysctl: permission denied on key "kernel.shmmax", ignoring 0 --- root@78489e17c933:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="21.04 (Hirsute Hippo)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 21.04" VERSION_ID="21.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=hirsute UBUNTU_CODENAME=hirsute root@78489e17c933:/tmp# sysctl -V sysctl from procps-ng 3.3.16 root@78489e17c933:/tmp# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===--= ii procps 2:3.3.16-5ubuntu3.1 amd64/proc file system utilities root@78489e17c933:/tmp# echo "kernel.shmmax = 17179869184" > shmmax.conf root@78489e17c933:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 root@78489e17c933:/tmp# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@78489e17c933:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: sett
[Touch-packages] [Bug 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
I've been running 2.4.49+dfsg-2ubuntu1.8 from focal-proposed for the past few days and the issue has not returned. As otherwise the issue would occur at least once per day, I consider it fixed. Furthermore, no other issues have cropped up in the meantime. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: Fix Committed Status in openldap source package in Groovy: Fix Released Bug description: [Impact] When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit. [Test Plan] === When using openldap on 20.04, this bug causes failures in the SSSD LDAP backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up With the patched version, this should no longer be a problem. [Where Problems Could Occur] With this patch applied, there may be few edge cases in (and varying b/w) different versions of GnuTLS. And also some bits that are discussed in https://bugs.openldap.org/show_bug.cgi?id=8650. But that said, the patched version is already being run in production for over two weeks time (at the time of writing - 07/04/21). So I believe the SRU will clearly benefit from this and has lower risk of regression. [More Info] === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
The bug hasn't returned since I installed the fixed package and no new issues have cropped up. -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: In Progress Status in openldap source package in Groovy: Fix Released Bug description: [Impact] When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit. [Test Plan] === When using openldap on 20.04, this bug causes failures in the SSSD LDAP backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up With the patched version, this should no longer be a problem. [Where Problems Could Occur] With this patch applied, there may be few edge cases in (and varying b/w) different versions of GnuTLS. And also some bits that are discussed in https://bugs.openldap.org/show_bug.cgi?id=8650. But that said, the patched version is already being run in production for over two weeks time (at the time of writing - 07/04/21). So I believe the SRU will clearly benefit from this and has lower risk of regression. [More Info] === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
I've deployed the patch, I'll let you know whether it works and if any regressions occur. -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Focal: In Progress Status in openldap source package in Groovy: Fix Released Bug description: [Impact] When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit. [Test Plan] === When using openldap on 20.04, this bug causes failures in the SSSD LDAP backend, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up With the patched version, this should no longer be a problem. [Where Problems Could Occur] With this patch applied, there may be few edge cases in (and varying b/w) different versions of GnuTLS. And also some bits that are discussed in https://bugs.openldap.org/show_bug.cgi?id=8650. But that said, the patched version is already being run in production for over two weeks time (at the time of writing - 07/04/21). So I believe the SRU will clearly benefit from this and has lower risk of regression. [More Info] === A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
Just to be sure, is there anything that I would need to do in order to have the bugfix applied in a new openldap release for Ubuntu 20.04? -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Fix Released Status in openldap package in Ubuntu: Confirmed Bug description: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921562] Re: Intermittent hangs during ldap_search_ext when TLS enabled
** Description changed: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. - As this bug affects al systems using LDAP with TLS , I suggest that the + As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Unknown Status in openldap package in Ubuntu: Confirmed Bug description: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1921562] [NEW] Intermittent hangs during ldap_search_ext when TLS enabled
Public bug reported: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. ** Affects: openldap Importance: Unknown Status: Unknown ** Affects: openldap (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: focal ** Patch added: "retry-tls-connect-on-eintr-eagain.patch" https://bugs.launchpad.net/bugs/1921562/+attachment/5481337/+files/retry-tls-connect-on-eintr-eagain.patch -- 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/1921562 Title: Intermittent hangs during ldap_search_ext when TLS enabled Status in openldap: Unknown Status in openldap package in Ubuntu: Confirmed Bug description: When connecting to an LDAP server with TLS, ldap_search_ext can hang if during the initial TLS handshake a signal is received by the process. The cause of this bug is the same as https://bugs.openldap.org/show_bug.cgi?id=8650 which was fixed in https://git.openldap.org/openldap/openldap/-/commit/735e1ab and was released as part of version 2.4.50. This bug effects Ubuntu 20.04 LTS and potentially earlier Ubuntu releases. Later Ubuntu releases use an openldap version that is at least 2.4.50 and are therefore not affected. In our case this bug cause failures in the SSSD LDAP backend at least once per day, resulting in authentication errors followed by a sssd_be restart after a timeout has been hit: Mar 19 19:05:31 mail auth[867454]: pam_sss(dovecot:auth): received for user redacted: 4 (System error) Mar 19 19:05:32 mail sssd_be[867455]: Starting up A reduced version of the patch linked above can be found attached to this bug report. This patch has been applied to version 2.4.49+dfsg- 2ubuntu1.7 and has been running in production for approximately a week and the issue has no longer occurred. No other issues have appeared during this period. As this bug affects all systems using LDAP with TLS, I suggest that the fix for this bug is ported to Ubuntu 20.04 LTS and potentially earlier versions. To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1921562/+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 1916469] [NEW] Ubuntu universe Wayland problem
Public bug reported: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) qdirstat vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") ** Affects: ubuntu Importance: Undecided Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: qdirstat (Ubuntu) Importance: Undecided Status: New ** Affects: telegram-desktop (Ubuntu) Importance: Undecided Status: New ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute wayland ** Tags added: wayland ** Tags added: hirsute ** Also affects: wayland (Ubuntu) Importance: Undecided Status: New ** Also affects: telegram-desktop (Ubuntu) Importance: Undecided Status: New ** Also affects: qdirstat (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Also affects: vlc (Ubuntu) Importance: Undecided Status: New ** Description changed: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: - telegram (Wayland support work with snap version) + telegram-desktop (Wayland support work with snap version) qdirstat vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1916469 Title: Ubuntu universe Wayland problem Status in Ubuntu: New Status in firefox package in Ubuntu: New Status in qdirstat package in Ubuntu: New Status in telegram-desktop package in Ubuntu: New Status in vlc package in Ubuntu: New Status in wayland package in Ubuntu: New Bug description: The Ubuntu universe has a big Wayland problem! What does that mean? So a lot of packages in the Universe repository are not compiled with Wayland support which is really bad and would lead to bad performance after 21.04 comes out. Here are the following packages that I detected with wrong compilation: telegram-desktop (Wayland support work with snap version) qdirstat vlc kiwix firefox (everything works fine with this env variable set:"MOZ_ENABLE_WAYLAND=1") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1916469/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
if focal needs a separate debdiff for it to get applied on that branch, let me know. focal is in need of other updates like the .tarball-version fix included in -5 in upstream debian -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: Confirmed Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1903351] Re: ignore_eacces and ignore_erofs patches don't work properly
Attaching debdiff for groovy. Same changes should work for focal built via pbuilder-dist and tested root@659bc6500a59:/# dpkg -i /home/vfazio/pbuilder/groovy_result/procps_3.3.16-5ubuntu3_amd64.deb (Reading database ... 4259 files and directories currently installed.) Preparing to unpack .../procps_3.3.16-5ubuntu3_amd64.deb ... Unpacking procps (2:3.3.16-5ubuntu3) over (2:3.3.16-5ubuntu2) ... Setting up procps (2:3.3.16-5ubuntu3) ... root@659bc6500a59:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu3 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 root@bfee89058713:/tmp# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/tmp# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax", ignoring: Read-only file system 0 ** Patch added: "groovy debdiff" https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+attachment/5431997/+files/1-3.3.16-5ubuntu3.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: New Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1903351] [NEW] ignore_eacces and ignore_erofs patches don't work properly
Public bug reported: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 ** Affects: procps (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1903351 Title: ignore_eacces and ignore_erofs patches don't work properly Status in procps package in Ubuntu: New Bug description: The patches used to ignore errors in containers no longer work as of 3.3.16 due to upstream commit https://gitlab.com/procps- ng/procps/-/commit/7af88da373bb4d515a98ec2f0f5d56c63904f932 The ignore_eacces patch was fuzzed and gets applied to ReadSetting, not WriteSetting Both patches ignore the change that rc is no longer propagated up and instead everything is trapped by: if (!ignore_failure && errno != ENOENT) rc = -1; Versions affected: focal+ root@bfee89058713:/tmp# cat /etc/os-release NAME="Ubuntu" VERSION="20.10 (Groovy Gorilla)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.10" VERSION_ID="20.10" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=groovy UBUNTU_CODENAME=groovy root@bfee89058713:/# dpkg -l procps Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-=--= ii procps 2:3.3.16-5ubuntu2 amd64/proc file system utilities root@bfee89058713:/# echo "kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 255 root@bfee89058713:/# echo "-kernel.shmmax = 17179869184" > shmmax.conf root@bfee89058713:/# sysctl -e -p shmmax.conf; echo $? sysctl: setting key "kernel.shmmax": Read-only file system 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1903351/+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 1848731] Re: Audio output device changes upon unlock/login
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Ubuntu needs a lock feature in the gnome sound settings, because each time a device is detected the output/input will change automatically. Sometimes this feature is wanted (I plug-in a headphone) sometimes it's not (I don't want the sound output to switch to my monitor when I power it since no speakers are plugged to it) -- 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/1848731 Title: Audio output device changes upon unlock/login Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04. Locking/Suspending and logging in changes my audio output device. This did not happen in 19.04. How to reproduce When I lock my session with key combination "Win+L" and then unlock it again, the sound that's been playing through my headphones/speakers stops playing. When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is selected. When I select "Headphones - Built-in audio", sound continues playing. There is no related log output in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
I just hit this bug with 19.04... The following "/usr/lib/gnome-online-accounts/goa-daemon --replace" did sort of reactivated my accounts accessibility. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Fix Released Status in gnome-online-accounts package in Ubuntu: Fix Released Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Won't Fix Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1826648] [NEW] cupds crashes with core dump
Public bug reported: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended- up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat Apr 27 09:54:21 2019 InstallationDate: Installed on 2019-04-05 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: LENOVO 20L6SF1000 Papersize: letter PpdFiles: Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS Samsung-C460: Samsung C460 Series PS ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SF1000 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SF1000 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480 dmi.product.version: ThinkPad T480 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1826648 Title: cupds crashes with core dump Status in cups package in Ubuntu: New Bug description: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended-up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1826648] Re: cupds crashes with core dump
Here is the core dump with backtrace: $ gdb -c core /usr/sbin/cupsd Reading symbols from /usr/sbin/cupsd... (No debugging symbols found in /usr/sbin/cupsd) [New LWP 15514] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `cupsd -f -c /etc/cups/cupsd.conf'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: Aucun fichier ou dossier de ce type. (gdb) backtrace #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x7ff44c736535 in __GI_abort () at abort.c:79 #2 0x7ff44c79d726 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7ff44c8c3952 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 #3 0x7ff44c7a459a in malloc_printerr (str=str@entry=0x7ff44c8c1a9b "free(): invalid pointer") at malloc.c:5352 #4 0x7ff44c7a63cc in _int_free (av=, p=, have_lock=) at malloc.c:4181 #5 0x7ff44c9a78be in ?? () from /usr/lib/x86_64-linux-gnu/libcups.so.2 #6 0x7ff44c9a7828 in ippDelete () from /usr/lib/x86_64-linux-gnu/libcups.so.2 #7 0x56032e311964 in ?? () #8 0x56032e34baa7 in ?? () #9 0x56032e309310 in ?? () #10 0x7ff44c737b6b in __libc_start_main (main=0x56032e308940, argc=4, argv=0x7fffb6f84b28, init=, fini=, rtld_fini=, stack_end=0x7fffb6f84b18) at ../csu/libc-start.c:308 #11 0x56032e30a5fa in ?? () (gdb) quit ** Attachment added: "core dumped with manual invocation" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826648/+attachment/5259490/+files/core -- 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/1826648 Title: cupds crashes with core dump Status in cups package in Ubuntu: New Bug description: At home my cupsd daemon crashes all the time. Sometimes I'm able to print a few pages but in most cases it ends-up restarting and sending tons of crap to my printer resulting in multiple wasted pages with non-sense characters printed on it. I ended-up manually creating a core dump by launching it from root with: # cupsd -f -c /etc/cups/cupsd.conf (will attach core in post) I tried using the default drivers for my printer then using the Samsung provided ones with same result. My printer is a Samsung C460W. Here is the systemd status: $ sudo systemctl status cups ● cups.service - CUPS Scheduler Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled) Active: failed (Result: core-dump) since Sat 2019-04-27 09:49:09 EDT; 12min ago Docs: man:cupsd(8) Process: 15292 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT) Main PID: 15292 (code=dumped, signal=ABRT) avr 27 09:49:01 eclipse systemd[1]: Started CUPS Scheduler. avr 27 09:49:02 eclipse cupsd[15292]: free(): invalid pointer avr 27 09:49:02 eclipse systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT avr 27 09:49:09 eclipse systemd[1]: cups.service: Failed with result 'core-dump'. avr 27 09:49:09 eclipse systemd[1]: Stopped CUPS Scheduler. I wasn't able to find the core dump it refers to so that's why I ended-up generating one by invoking cupsd manually then launching ubuntu-bug against the cups package. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Sat Apr 27 09:54:21 2019 InstallationDate: Installed on 2019-04-05 (21 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: LENOVO 20L6SF1000 Papersize: letter PpdFiles: Samsung_C460_Series_th0ma7_print_: Samsung C460 Series PS Samsung-C460: Samsung C460 Series PS ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.0.0-13-generic root=UUID=f575ceec-b2a1-4507-ae3b-8487236a2c54 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-05 (21 days ago) dmi.bios.date: 02/20/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N24ET48W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20L6SF1000 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN24ET48W(1.23):bd02/20/2019:svnLENOVO:pn20L6SF1000:pvrThinkPadT480:rvnLENOVO:rn20L6SF1000:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T480 dmi.product.name: 20L6SF1000 dmi.product.sku: LENOVO_MT_20L6_BU_Think_FM_ThinkPad T480
[Touch-packages] [Bug 1800550] [NEW] Xorg freeze
Public bug reported: Both during and after installation (meaning while running the USB iso and booting from HDD after) ubuntu will rapidly become unresponsive and eventually hang when my 4k monitor is plugged in. I have 2 monitors, a 1920x1080, and a 4k. Everything works absolutely perfectly if I only use the 1920 monitor (this is where I am working from right now) but the moment the other monitor is plugged in I get problems. When I cold boot into the system from the small 1920x1080 monitor and then plug in the 4k monitor, the screen on my smaller monitor will glitch before returning to normal a few seconds later, while the 4k monitor never displays an image. The OS begins to bog down, the mouse begins to lag and become less responsive. If I open the display manager I can see that ubuntu has properly detected the 4k monitor and has the correct default settings (resolution, refresh rate, etc.) but attempting to make any changes will result in an immediate crash/hang upon pressing the "apply" button. If I cold boot ubuntu with only the 4k monitor plugged in, I see purple splash screen and ubuntu logo screens (at the correct resolutions) but the monitor output stops and I see only a black screen before the login screen is reached. If I cold boot with both monitors plugged in I see the splash screen and logo, there is a brief moment where the small monitor glitches, and then I see only the magenta backdrop of the login screen but there are no UI elements, and This is only seen on the small monitor; the 4k monitor has once again lost input and turned black. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 29 17:32:16 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1458:d000] NVIDIA Corporation GM204 [GeForce GTX 980] [10de:13c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GM204 [GeForce GTX 980] [1043:8518] InstallationDate: Installed on 2018-10-29 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=baa2b984-a1f5-4440-9c3e-9bfece3b4bc0 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-SLI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic freeze 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/1800550 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Both during and after i
[Touch-packages] [Bug 1797602] [NEW] systemd incompatible with openresolv and dnsmasq
Public bug reported: Problem: systemd breaks resolvconf-dependent DNS Test case: Install dnsmasq with systemd. Result: The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the make_resolv_conf() function to pass DHCP information to the /sbin/resolvconf program. The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the make_resolv_conf() function to write DHCP information to /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf As a result, resolvconf never runs, and dnsmasq never receives the DHCP-supplied nameservers. Therefore, DNS resolution is broken. Expected result: DHCP-supplied nameservers should be passed to both resolvconf and to systemd. Workaround: Use the 127.0.0.53 address for the systemd resolver as the dnsmasq upstream server. lsb_release -rd output: Description:Ubuntu 18.04.1 LTS Release:18.04 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1797602 Title: systemd incompatible with openresolv and dnsmasq Status in systemd package in Ubuntu: New Bug description: Problem: systemd breaks resolvconf-dependent DNS Test case: Install dnsmasq with systemd. Result: The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the make_resolv_conf() function to pass DHCP information to the /sbin/resolvconf program. The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the make_resolv_conf() function to write DHCP information to /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf As a result, resolvconf never runs, and dnsmasq never receives the DHCP-supplied nameservers. Therefore, DNS resolution is broken. Expected result: DHCP-supplied nameservers should be passed to both resolvconf and to systemd. Workaround: Use the 127.0.0.53 address for the systemd resolver as the dnsmasq upstream server. lsb_release -rd output: Description:Ubuntu 18.04.1 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797602/+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 1785236] Re: "dm-tool add-nested-seat" doesn't work normally
** Description changed: Hello, - since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. + since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: New Bug description: Hello, since I installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" hasn't worked normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1785236] [NEW] "dm-tool add-nested-seat" doesn't work normally
Public bug reported: Hello, since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: dm-tool lighdm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1785236 Title: "dm-tool add-nested-seat" doesn't work normally Status in lightdm package in Ubuntu: New Bug description: Hello, since I've installed Xubuntu 18-04 (on 15 july 2018). The command "dm-tool add-nested-seat" doesn't work normally. I have a blank screen instead of a login screen. Maybe the problem is due to greeter cause when I set autologin for an user, then everything seems to work normally. The login screen is just skipped. [Impact] "dm-tool add-nested-seat" doesn't work (excepted when autologin-user is set). [Test Case] 1. Log in 2. From a terminal run "dm-tool add-nested-seat" [Expected result] A window opens with a login screen [Observed result] A window opens with a complete black screen if autologin-user isn't set in /etc/lightdm/lightdm.conf No error in the terminal. If autologin is set in /etc/lightdm/lightdm.conf, then it works normally. [used distribution] Xubuntu 18-04, up to date. I didn't have this trouble in may 2018 while I was under Xubuntu 17-10. [related trouble] maybe it's related to this bug: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1529454 But I don't exactly have the same trouble. So I thought I should open a new one. Sorry if I was wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1785236/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
Same here error with edvi's DisplayLinkManager process to get a displaylink screen from a USB 3.0 hub/docking station like https://www.anker.com/store/USB-3.0-Docking-Station/68ANDOCKS-BA went back to 4.4.0-112 to work. Will wait future 4.4.0-(>116) kernel to retry. -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Still not working..i hope someone can fix this problem... -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@Silas Linux users are patient indeed and they are certainly not waiting for useless comments like yours. If you want to contribute, educate yourself and try to help out. Ranting does contribute NOTHING. So if you really love Linux, think about that. Try to follow the rules regarding the bug report and contribute where you can and people will like it. Nobody asked you to use Ubuntu, if you're happy with windows 10 (which probably nobody else here is) then use it and be happy, why post here? Don't forget Linux is a community effort and the ways to fix certain problems is difficult. However, making an effort to get it to work will teach you and will get you appreciation from others. As bagl0312 commented already, your point is not even viable, because the issue was fixed in 17.04 by a patch. If you google the issue for older versions, you will probably land on a page that describes how to fix that too: https://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns and see work arounds in this thread, so your comment is really just bad timing. Please think twice before you post something and read the rules. Thanks to the relentless efforts of the community, this is fixed and work is going on to get this in the main version(s). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Thomas: I am not an expert on this, but as far as I can tell from the documentation you are seeing a different dns replying at times because (I quote the systemd.resolved.service doc) "Multi-label names are routed to all local interfaces that have a DNS sever configured (...) If lookups are routed to multiple interfaces, the first successful response is returned". So basically all the dns servers defined in all of your links are fair game. DNS requests are sent to all of them at the same time and whichever replies first win the day! My understanding is that you have to specify dhcp-options DOMAIN-ROUTE . in your openvpn connection settings to force dns requests to all domains to go through the vpn link and ignore the dns on other links. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Here is a solution that seems to work for me. Note that I use a simple openvpn client configuration file that I run directly from the console. I don't use a GUI for my vpn connection, but I assume you can do the same via a gui interface. Within my openvpn client config file, I call a script called update- systemd-resolved as a replacement to the standard update-resolv-conf used previously. That script is available here: https://github.com/jonathanio/update- systemd-resolved After that, after connecting, when I run systemd-resolve --status I can see that a new link is added for tun0 with the proper dns entries. But that's only a first step, because it seems that with systemd.resolved.service (I quote) "Multi-label names are routed to all local interfaces that have a DNS sever configured (...) If lookups are routed to multiple interfaces, the first successful response is returned". So basically it's still sending requests on all interfaces, including the main eth0 or whatever it is on your system, and the fastest one wins (in my case because eth0 points to my router that acts as a dns server, it always wins). To avoid leaks, we want only requests to go to the tun0 link. Then I read that "Routing of lookups may be influenced by configuring per-interface domain names". If you read the instructions in the update-systemd-resolved, you'll see that it allows to specify dhcp- options DOMAIN-ROUTE to force a specific domain to go through that interface. You can use a single dot to mean all domains. So basically I added dhcp-option DOMAIN-ROUTE . to my clienf config to send everything exclusively to tun0 and that seems to do the trick. So combined with the instructions from the github page, this is what I have on my config: # avoid dns leak when using systemd-resolved dhcp-option DOMAIN-ROUTE . script-security 2 setenv PATH /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin up /etc/openvpn/update-systemd-resolved down /etc/openvpn/update-systemd-resolved down-pre -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
You can still add the vpn nameserver to /etc/resolv.conf . Epic blunder by both systemd-resolv maintainer and Ubuntu packagers for stacking a broken configuration together for at the 3rd release. Does anyone know how to escalate this? On May 4, 2017 19:04, "Winckler" wrote: > It's a really ugly workaround, but I'm using iptables to block > connections to my ISP's DNS. I manually create and remove iptables rules > using a script but at least this allows me to work remotely. I hope this > get fix soon. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1624317 > > Title: > systemd-resolved breaks VPN with split-horizon DNS > > Status in systemd: > New > Status in systemd package in Ubuntu: > Confirmed > > Bug description: > I use a VPN configured with network-manager-openconnect-gnome in which > a split-horizon DNS setup assigns different addresses to some names > inside the remote network than the addresses seen for those names from > outside the remote network. However, systemd-resolved often decides > to ignore the VPN’s DNS servers and use the local network’s DNS > servers to resolve names (whether in the remote domain or not), > breaking the split-horizon DNS. > > This related bug, reported by Lennart Poettering himself, was closed > with the current Fedora release at the time reaching EOL: > https://bugzilla.redhat.com/show_bug.cgi?id=1151544 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions > -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
indeed, this is COMPLETELY broken on 17.04. It seems systemd-resolved is the only thing being used. My DNS resolving over anyconnect (openconnect) does not work AT ALL anymore. I don't know which brilliant mind decided to change things like that, knowing there are so many bugs open. any work arounds known are greatly appreciated (disabling systemd- resolved did not help) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Same here. Issue still on going with zesty 17.04 and quite painfull to deal with. One other approach is to re-symlink resolv.conf to /run/systemd/resolve/resolv.conf but openconnect then update /run/resolvconf/resolv.conf making this a total mess. I don't get it, this should be fairly trivial... -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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
>From the man page systemd-resolve can run in 3 mode of operations. 1) Ubuntu 17.10 default - The default is to list the 127.0.0.53 DNS stub (see above) as only DNS server. This file may be symlinked from /etc/resolv.conf in order to connect all local clients that bypass local DNS APIs to systemd-resolved. This mode of operation is recommended. 2) WHAT YOU WANT: systemd-resolved maintains the /run/systemd/resolve/resolv.conf file for compatibility with traditional Linux programs. This file may be symlinked from /etc/resolv.conf and is always kept up-to-date, containing information about all known DNS servers 3) PRE-17.04: Alternatively, /etc/resolv.conf may be managed by other packages, in which case systemd-resolved will read it for DNS configuration data. In this mode of operation systemd-resolved is consumer rather than provider of this configuration file. The fix: root@localhost:~# ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 29 mar 7 20:20 /etc/resolv.conf -> ../run/resolvconf/resolv.conf root@localhost:~# rm -f /etc/resolv.conf root@localhost:~# ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf root@localhost:~# ls -la /etc/resolv.conf lrwxrwxrwx 1 root root 32 mar 8 07:30 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf Finally firefox started working properly along with all my command line tools... -- 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: Incomplete 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 1241752] Re: Crash when opening image files larger than 5M (>5M)
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1241752 Title: Crash when opening image files larger than 5M (>5M) Status in cairo package in Ubuntu: Confirmed Bug description: This is similar to the bug reported here: http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=710701 However, the crash that is now getting generated is from an entirely different call and file. Specifically, the error is: eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Assertion `*ptr != ((void *)0)' failed. Aborted (core dumped) In the message above, I was using eog, but this affects other apps, like gThumb as well. In terms of the environment, I'm using Ubuntu 13.10 on an 64-bit machine, and am using libcairo2-1.12.16. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libcairo2 1.12.16-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Fri Oct 18 11:08:27 2013 InstallationDate: Installed on 2013-04-25 (176 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cairo UpgradeStatus: Upgraded to saucy on 2013-10-15 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1241752/+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 1650929] [NEW] DNS resolving fails after adding usb wifi dongle
Public bug reported: I noticed when a USB wifi dongle is plugged in and I disconnect the builtin one (Ubuntu 16.10), that resolving of DNS didn't work anymore. I could ping for example google.nl on IP, but not resolve the name. After some searching I found the issue seems to be caused by dnsmasq or systemd-resolved, the first being the most likely. I disabled dnsmasq in NetworkManager and restarted it and stopped dnsmasq and everything works as expected. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.6-byt-freeze-fix x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 18 19:16:30 2016 InstallationDate: Installed on 2016-12-11 (7 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dnsmasq (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1650929 Title: DNS resolving fails after adding usb wifi dongle Status in dnsmasq package in Ubuntu: New Bug description: I noticed when a USB wifi dongle is plugged in and I disconnect the builtin one (Ubuntu 16.10), that resolving of DNS didn't work anymore. I could ping for example google.nl on IP, but not resolve the name. After some searching I found the issue seems to be caused by dnsmasq or systemd-resolved, the first being the most likely. I disabled dnsmasq in NetworkManager and restarted it and stopped dnsmasq and everything works as expected. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.6-byt-freeze-fix x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 18 19:16:30 2016 InstallationDate: Installed on 2016-12-11 (7 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1650929/+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 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
@Martin Pitt : why did you mark this as resolved ?? This is a huge issue and restarting systemd-resolved did NOT fix my problem. Also, we should not have workarounds, we should have an Ubuntu desktop that: - works out of the box at installation: both 16.04 AND 16.10 - works BEFORE and AFTER an UPGRADE of 16.04 - works without any manual work arounds or hacks So PLEASE, come up with an actual solution that fixes this shit. I honestly find it difficult to express how pissed off I am about the bugs because they affect both home and enterprise users. Here is an overview with a discussion: http://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns/861991#861991 I propose to either: - disable all services that break normal, expected behviour: so out with systemd-resolvd if that fixes it - fix issues with dnsmasq and/or disable that too by default in NetworkManager Let's try to fix this in a proper way, and have non-technical users not deal with these issues. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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 1636375] Re: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf
Again Martin, this is NOT a solution. A fix would be something that avoids the problem from emerging in the first place. If stopping systemd-resolvd is a solution, that let's make sure it is NOT enabled nor installed in 17.04 by default and let's FIX it to be the same in 16.10 if possible. Thank you -- 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/1636375 Title: systemd-resolved does not allow you to connect using subdomains using search domains which are in /etc/resolv.conf Status in systemd: Fix Released Status in systemd package in Ubuntu: Won't Fix Bug description: systemd-resolved doesn't seem to allow you to use subdomains when connecting to hosts in domains that are part of /etc/resolv.conf e.g. 16:01|scrosby@stewie: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver W.X.Y.Z nameserver A.B.C.D nameserver 127.0.0.53 search blah1 blah2 blah3 blah4 blah5 with systemd-resolved running 16:05|scrosby@stewie: ~$ ping foo.bar ping: foo.bar: Name or service not known without systemd-resolved running 16:05|scrosby@stewie: ~$ ping foo.bar PING foo.bar.blah3 (E.F.G.H) 56(84) bytes of data. 64 bytes from foo.bar.blah3 (E.F.G.H): icmp_seq=1 ttl=52 time=1.68 ms 64 bytes from foo.bar.blah3 (E.F.G.H): icmp_seq=2 ttl=52 time=1.09 ms It does seem like looking up hosts without a . in their name does use the search domains in resolv.conf though 16:05|scrosby@stewie: ~$ ping foo2 PING foo2.blah3 (I.J.K.L) 56(84) bytes of data. 64 bytes from foo2.blah3 (I.J.K.L): icmp_seq=1 ttl=52 time=1.34 ms 64 bytes from foo2.blah3 (I.J.K.L): icmp_seq=2 ttl=52 time=1.29 ms ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 Date: Tue Oct 25 16:13:38 2016 InstallationDate: Installed on 2016-06-08 (139 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Dell Inc. OptiPlex 990 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=67011022-ac91-464f-ab8f-c97c6cb5a439 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-10-24 (0 days ago) dmi.bios.date: 08/26/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.asset.tag: UOM97917 dmi.board.name: 0VNP2H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: UOM97917 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd08/26/2015:svnDellInc.:pnOptiPlex990:pvr01:rvnDellInc.:rn0VNP2H:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 990 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1636375/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
Since this number comes before the other, if it were a duplicate, it would be the other way around. While maybe related it is another bug related to ipv6 as far as I can read. The pile of crap coming from changes in networkmanager, vpn, dnsmasq or wherever they come from is horrible : I have never had so many things breaking over a release and never so vital. While I am not happy with the content and tend to disagree, please follow the suggestion of post 50. Let's try to be as specific as possible and file the bugs like that. Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1535058] Re: applications close instantly when launched from the launcher or dash
I am running 16.10 with budgie installed. Installing unity8 gave me the crashing apps issue. Tried to : sudo systemctl enable cgmanager (it was already running) sudo apt-get install libpam-cgfs it was already installed and sudo apt-get install libpam-cgm that was not installed. I still have the problem with apps crashing, except for libertine -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1535058 Title: applications close instantly when launched from the launcher or dash Status in Canonical System Image: Confirmed Status in cgmanager package in Ubuntu: Incomplete Status in qtmir package in Ubuntu: Invalid Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Status in unity8-desktop-session package in Ubuntu: Invalid Status in upstart package in Ubuntu: Invalid Bug description: xenial applications close instantly when launched from the launcher or dash but... if i launch the apps from a VT (for ex firefox using Xmir or gedit native --), the app loads ok. what close instantly means.. it opens the window and then it closes instantly in ~0.3s --- This has been traced to two causes: pam was not installed, it is now a dependency of ubuntu-app-launch or can be installed directly $ sudo apt-get install libpam-cgfs and cgmanager is not enabled by default on systems that were upgraded and not clean installs. To enable it $ sudo systemctl enable cgmanager To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1535058/+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 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
I noticed a few days back after a failed update that I had cups as a broken package. I uninstalled and some other packages were removed, then I reinstalled. That seemed to work. I don't know what I lost and while reporting I got a notification that my conf file was edited. Can't remember ever changing anything. -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: This is in xenial-proposed, please block release to -updates accordingly :) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+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 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@https://launchpad.net/~cyphermox Mathieu, why are you marking this as Incomplete? Can you be specific in what kind of information you need to consider it complete, instead of pointing people to a DNS admin, who may not be interested in filing a bug? Some people clearly described how the behaviour changed from 14.04 and I can confirm this. The current setup is nowhere near a working solution that a normal user that gets VPN connection info can work with. That hurts business users and pisses developers and users off that even want to make an attempt to make it work. The net is flooded with issues regarding VPN and DNS, it would be great if you can point us to the right steps and information to supply to actually get this working like say the cisco AnyConnect secure mobility client. With the exact same VPN server, I can use that tool on Mac OS X without ANY configuration and it "Just works". I would say the goal is to have it working like that for everybody using network manager. Let's talk defaults, settings and requirements and I'll try to get the server info or anything else that is needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Incomplete Status in openvpn package in Ubuntu: Incomplete Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+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 1582979] Re: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
When updating the process fails, a message comes and says the /boot is full, checked it and it is approx 99% full, it contains copies of a approx 20Mb size files and also copies of other multiple but smaller files, these files are all dated. This is a persistent fault. Cannot edit the /boot file as No Permission shows. -- 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/1582979 Title: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Just happened after software update, I did not restart, instead, I powered off and powered on the next day. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-71.92~14.04.1-generic 3.16.7-ckt27 Uname: Linux 3.16.0-71-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue May 17 23:32:21 2016 DuplicateSignature: package:linux-image-3.16.0-71-generic:3.16.0-71.92~14.04.1:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2015-12-06 (163 days ago) InstallationMedia: Edubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.13 SourcePackage: initramfs-tools Title: package linux-image-3.16.0-71-generic 3.16.0-71.92~14.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1582979/+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 1574020] Re: Can't use networkmanager from lightdm
A use case is that I would like to be able to ssh into my Ubuntu 16.04 laptop when I'm logged out, which is of course only possible if it's connected to a network. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1574020 Title: Can't use networkmanager from lightdm Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in unity-greeter package in Ubuntu: Confirmed Bug description: After upgrading to 16.04 desktop (unity) (clean install) from 14.04, (so not really upgrading, but you get the point) I noticed that lightdm with unity-greeter (all stock, nothing changed) can't connect to WiFi with network-manager. WiFi works after loggin it, but it should be working before also, if not, what's the point in having an icon there :) I get the following message: Failed to add/activate connection. - (1) Insufficient privileges. - see image. This worked fine in 14.04. I have noticed this problem in both my desktop (Broadcom WiFi) and Laptop (Intel WiFi) - So it has nothing to be with the chip. Feel free to ask for more info. Edit: From syslog: Apr 23 16:50:46 desktop NetworkManager[979]: nm_settings_connection_delete: assertion 'NM_IS_SETTINGS_CONNECTION (self)' failed Apr 23 16:50:46 desktop NetworkManager[979]: [1461423046.1662] audit: op="connection-add-activate" pid=1275 uid=108 result="fail" reason="Insufficient privileges." Apr 23 16:50:46 desktop NetworkManager[979]: (NetworkManager:979): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1574020/+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 1398614] Re: mediascanner-service-2.0 using large amounts of CPU
I was searching for a way to disable this, I hope I have found the right place in configuration settings... I opened in menus : Applications System tools Preferences Searching & indexing I unchecked everything in "semantics" It looks like there's an option missing in "limits", I would like to choose "never" for "background content indexing", but this option is not provided here... This is manual translation from my installed lang to english so may not be 100% accurate -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1398614 Title: mediascanner-service-2.0 using large amounts of CPU Status in mediascanner2 package in Ubuntu: Confirmed Bug description: Each time I plug my external USB hard disk the mediascanner-service process is activ and is using large amount of CPU for long minutes without interruption. I have the same problem in utopic and vivid ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 00:29:43 2014 InstallationDate: Installed on 2011-05-26 (1286 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: mediascanner2 UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614/+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 1581762] Re: Network manager crashes after last upgrade
Cache policy report. ** Attachment added: "Cache policy for network-manager" https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581762/+attachment/4662713/+files/cache-policy-network-manager.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1581762 Title: Network manager crashes after last upgrade Status in libnl3 package in Ubuntu: New Bug description: Hello I'm running Ubuntu 14.04 and did an upgrade yesterday. Since that upgrade and reboot, network manager crashes and I'm unable to restart it. In my update configuration, pre release (trusty proposed) is NOT selected and I'm still running libnl-*-3-200 3.2.21-1. The syslog states that network manager main process has been killed by SEGV signal. Installed release of network manager is 0.9.8.8-0ubuntu7.2 Restarting the network manager does not do anything, same for ifup/ifdown. Network icon does not appear anymore. Your support will be appreciated. Kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581762/+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 1581762] Re: Network manager crashes after last upgrade
Here is the CRASH report file. ** Attachment added: "Crash file with DUMP" https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581762/+attachment/4662712/+files/_usr_sbin_NetworkManager.0.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1581762 Title: Network manager crashes after last upgrade Status in libnl3 package in Ubuntu: New Bug description: Hello I'm running Ubuntu 14.04 and did an upgrade yesterday. Since that upgrade and reboot, network manager crashes and I'm unable to restart it. In my update configuration, pre release (trusty proposed) is NOT selected and I'm still running libnl-*-3-200 3.2.21-1. The syslog states that network manager main process has been killed by SEGV signal. Installed release of network manager is 0.9.8.8-0ubuntu7.2 Restarting the network manager does not do anything, same for ifup/ifdown. Network icon does not appear anymore. Your support will be appreciated. Kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581762/+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 1581762] [NEW] Network manager crashes after last upgrade
Public bug reported: Hello I'm running Ubuntu 14.04 and did an upgrade yesterday. Since that upgrade and reboot, network manager crashes and I'm unable to restart it. In my update configuration, pre release (trusty proposed) is NOT selected and I'm still running libnl-*-3-200 3.2.21-1. The syslog states that network manager main process has been killed by SEGV signal. Installed release of network manager is 0.9.8.8-0ubuntu7.2 Restarting the network manager does not do anything, same for ifup/ifdown. Network icon does not appear anymore. Your support will be appreciated. Kind regards. ** Affects: libnl3 (Ubuntu) Importance: Undecided Status: New ** Tags: network-manager segv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1581762 Title: Network manager crashes after last upgrade Status in libnl3 package in Ubuntu: New Bug description: Hello I'm running Ubuntu 14.04 and did an upgrade yesterday. Since that upgrade and reboot, network manager crashes and I'm unable to restart it. In my update configuration, pre release (trusty proposed) is NOT selected and I'm still running libnl-*-3-200 3.2.21-1. The syslog states that network manager main process has been killed by SEGV signal. Installed release of network manager is 0.9.8.8-0ubuntu7.2 Restarting the network manager does not do anything, same for ifup/ifdown. Network icon does not appear anymore. Your support will be appreciated. Kind regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1581762/+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 1573811] [NEW] package initscripts 2.88dsf-41ubuntu6.3 failed to install/upgrade: pre-dependency problem - not installing initscripts
Public bug reported: It's during the ubuntu 16.04 lts update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initscripts 2.88dsf-41ubuntu6.3 ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 Date: Fri Apr 22 17:19:58 2016 DpkgTerminalLog: Preparing to unpack .../util-linux_2.27.1-6ubuntu3_amd64.deb ... Unpacking util-linux (2.27.1-6ubuntu3) over (2.20.1-5.1ubuntu20.7) ... Replacing files in old package sysvinit-utils (2.88dsf-41ubuntu6.3) ... Replacing files in old package initscripts (2.88dsf-41ubuntu6.3) ... DuplicateSignature: package:initscripts:2.88dsf-41ubuntu6.3:pre-dependency problem - not installing initscripts ErrorMessage: pre-dependency problem - not installing initscripts InstallationDate: Installed on 2016-01-23 (90 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.0.1ubuntu2.13 SourcePackage: sysvinit Title: package initscripts 2.88dsf-41ubuntu6.3 failed to install/upgrade: pre-dependency problem - not installing initscripts UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) ** Affects: sysvinit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1573811 Title: package initscripts 2.88dsf-41ubuntu6.3 failed to install/upgrade: pre-dependency problem - not installing initscripts Status in sysvinit package in Ubuntu: New Bug description: It's during the ubuntu 16.04 lts update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initscripts 2.88dsf-41ubuntu6.3 ProcVersionSignature: Ubuntu 3.19.0-59.65~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.20 Architecture: amd64 Date: Fri Apr 22 17:19:58 2016 DpkgTerminalLog: Preparing to unpack .../util-linux_2.27.1-6ubuntu3_amd64.deb ... Unpacking util-linux (2.27.1-6ubuntu3) over (2.20.1-5.1ubuntu20.7) ... Replacing files in old package sysvinit-utils (2.88dsf-41ubuntu6.3) ... Replacing files in old package initscripts (2.88dsf-41ubuntu6.3) ... DuplicateSignature: package:initscripts:2.88dsf-41ubuntu6.3:pre-dependency problem - not installing initscripts ErrorMessage: pre-dependency problem - not installing initscripts InstallationDate: Installed on 2016-01-23 (90 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.0.1ubuntu2.13 SourcePackage: sysvinit Title: package initscripts 2.88dsf-41ubuntu6.3 failed to install/upgrade: pre-dependency problem - not installing initscripts UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1573811/+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 1434986] Re: Not working network connection after boot
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1328260] Re: mighty mouse bluetooth not pairing
A decent OS would just pair with a mouse and implement the workaround or structurally fix the bug. The bug is confirmed, so it's up to someone to fix it. Complain at the mouse vendor or at the developer and pick your hardware carefully and Linux is fun and nice. I reported this bug almost 2 years ago on an LTS release, I would have hoped for a fix by now. Instead I have a laptop that freezes now on the new soon to be released LTS. Had to rant a bit because I have had that a lot in the past. I don't see why a command line action is acceptable,for Linux to be great, these things should just work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1328260 Title: mighty mouse bluetooth not pairing Status in bluez package in Ubuntu: Confirmed Bug description: Using the default GUI, I cannot pair my Apple Mighty Mouse. The mouse is detected, but when trying to pair, nothing happens and it is impossible to connect. It seems there should be an agent running to handle the pairing/pin stuff, I found that here: http://askubuntu.com/questions/453655/ubuntu-14-04-bluetooth-magic-mouse-doesnt-pair-no-agent-available It might be an issue with more devices, I did not test it. So the fix: In a terminal as a normal user do: bluez-simple-agent then use pin (worked in my case). Description: Ubuntu 14.04 LTS Release: 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1328260/+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 1533711] Re: Printer is not responding
problem in the IP of the printer ** Changed in: cups (Ubuntu) Status: New => Invalid -- 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/1533711 Title: Printer is not responding Status in cups package in Ubuntu: Invalid Bug description: I tried to installed a Kyocera Taskfala 3510i printer, but I can't print with it. Here is the nmap result : $ nmap 172.29.222.10 Starting Nmap 6.40 ( http://nmap.org ) at 2016-01-13 16:08 CET Nmap scan report for 172.29.222.10 Host is up (0.0012s latency). Not shown: 989 closed ports PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 515/tcp open printer 9090/tcp open zeus-admin 9091/tcp open xmltec-xmlmail 9100/tcp open jetdirect 9101/tcp open jetdirect 9102/tcp open jetdirect 9103/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds Thanks you for your help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 13 16:05:13 2016 Lpstat: device for Kyocera-Mita-TASKalfa-3510i-KPDL: socket://127.29.222.10:9100 MachineType: LENOVO 20CLS32H00 Papersize: a4 PpdFiles: Kyocera-Mita-TASKalfa-3510i-KPDL: Kyocera TASKalfa 3510i (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET36W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS32H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CLS32H00:pvrThinkPadX250:rvnLENOVO:rn20CLS32H00:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CLS32H00 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1533711/+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 1533711] [NEW] Printer is not responding
Public bug reported: I tried to installed a Kyocera Taskfala 3510i printer, but I can't print with it. Here is the nmap result : $ nmap 172.29.222.10 Starting Nmap 6.40 ( http://nmap.org ) at 2016-01-13 16:08 CET Nmap scan report for 172.29.222.10 Host is up (0.0012s latency). Not shown: 989 closed ports PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 515/tcp open printer 9090/tcp open zeus-admin 9091/tcp open xmltec-xmlmail 9100/tcp open jetdirect 9101/tcp open jetdirect 9102/tcp open jetdirect 9103/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds Thanks you for your help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 13 16:05:13 2016 Lpstat: device for Kyocera-Mita-TASKalfa-3510i-KPDL: socket://127.29.222.10:9100 MachineType: LENOVO 20CLS32H00 Papersize: a4 PpdFiles: Kyocera-Mita-TASKalfa-3510i-KPDL: Kyocera TASKalfa 3510i (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET36W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS32H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CLS32H00:pvrThinkPadX250:rvnLENOVO:rn20CLS32H00:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CLS32H00 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug trusty -- 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/1533711 Title: Printer is not responding Status in cups package in Ubuntu: New Bug description: I tried to installed a Kyocera Taskfala 3510i printer, but I can't print with it. Here is the nmap result : $ nmap 172.29.222.10 Starting Nmap 6.40 ( http://nmap.org ) at 2016-01-13 16:08 CET Nmap scan report for 172.29.222.10 Host is up (0.0012s latency). Not shown: 989 closed ports PORT STATE SERVICE 80/tcp open http 139/tcp open netbios-ssn 443/tcp open https 445/tcp open microsoft-ds 515/tcp open printer 9090/tcp open zeus-admin 9091/tcp open xmltec-xmlmail 9100/tcp open jetdirect 9101/tcp open jetdirect 9102/tcp open jetdirect 9103/tcp open jetdirect Nmap done: 1 IP address (1 host up) scanned in 0.05 seconds Thanks you for your help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: cups 1.7.2-0ubuntu1.7 ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30 Uname: Linux 3.13.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 13 16:05:13 2016 Lpstat: device for Kyocera-Mita-TASKalfa-3510i-KPDL: socket://127.29.222.10:9100 MachineType: LENOVO 20CLS32H00 Papersize: a4 PpdFiles: Kyocera-Mita-TASKalfa-3510i-KPDL: Kyocera TASKalfa 3510i (KPDL) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-74-generic root=/dev/mapper/vg0-root ro quiet splash vt.handoff=7 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N10ET36W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20CLS32H00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN10ET36W(1.15):bd06/19/2015:svnLENOVO:pn20CLS32H00:pvrThinkPadX250:rvnLENOVO:rn20CLS32H00:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20CLS32H00 dmi.product.version: ThinkPad X250 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1533711/+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 1261338] Re: lxc-stop and even lxc-stop -k can hang
It never happened again (and may have been a misuse involving immortal sudo subprocesses but I'm blurry on the details), marking invalid but fixed released may be correct as well. ** Changed in: lxc (Ubuntu) Status: Expired => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1261338 Title: lxc-stop and even lxc-stop -k can hang Status in lxc package in Ubuntu: Invalid Bug description: and even 'lxc-stop -k -t ' can hang :-/ The context is an automated test run with otto using a lxc-container trigerring a kernel crash on the host. The host is still alive and so is the container but trying to implement a catch-all to stop a container left running is blocked because there is no way in this particular case to stop the container. The only alternative so far is to reboot the host :-/ http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty- daily_release/label=qa-intel-4000/951/console is one occurrence where the kernel crashed and 'lxc-stop -k -t 120 -n trusty-i386-20131216-0008' hanged requiring the job to be aborted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1261338/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
Funny thing I noticed is that if I close the lid again and open it again, it does work again -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1422143] Re: No wifi connection after suspend with systemd due to missing "wpa_cli suspend"
Same issue for me on Lenovo Yoga 2 11 running Ubuntu 15.04 and systemd . 01:00.0 Network controller: Broadcom Corporation BCM43142 802.11b/g/n (rev 01) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1422143 Title: No wifi connection after suspend with systemd due to missing "wpa_cli suspend" Status in One Hundred Papercuts: Confirmed Status in NetworkManager: Unknown Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Wily: Fix Committed Status in wpa source package in Xenial: Fix Released Bug description: Using systemd as my default init system if I resume from suspend my laptop, it doesn't automatically reconnect to the wireless network and it doesn't list the available network connections. The only way to get a wireless connection is to restart the network- manager daemon or going to the gnome-control-center, disable wireless and enable it again. SRU INFORMATION === In some of these cases this bug can be worked around by calling "wpa_cli suspend/resume" before/after suspend, like we used to do with the old pm-utils quirks (/usr/lib/pm-utils/sleep.d/60_wpa_supplicant). This only affects particular hardware, and thus this needs to be tested by affected reporters, there is no general reproducer for arbitrary systems. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 Uname: Linux 3.19.0-031900-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 Date: Sun Feb 15 18:27:39 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-10-22 (116 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) IpRoute: default via 10.0.0.1 dev wlan0 proto static metric 1024 10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.36 169.254.0.0/16 dev wlan0 scope link metric 1000 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-01-13 (32 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0wifi connected/org/freedesktop/NetworkManager/Devices/2 openhost_caldas 09d1f69d-d3da-4978-a69c-d94455db7ecf /org/freedesktop/NetworkManager/ActiveConnection/0 docker0 bridgeunavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- eth0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1422143/+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 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting
i still get this bug ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1442044 Title: Ordering processes: networkmanager should wait for kernel'module been activated first before starting Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: Get that journalctl log showing networkmanager starting before the related kernel'module been ready: systemd[1]: Starting Network. systemd[1]: Starting /etc/rc.local Compatibility... NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (lo): link connected NetworkManager[724]: (lo): carrier is ON NetworkManager[724]: (lo): new Generic device (driver: 'unknown' ifindex: 1) NetworkManager[724]: (lo): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth0): carrier is OFF NetworkManager[724]: (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) NetworkManager[724]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[724]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[724]: (eth0): preparing device NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth1): carrier is OFF NetworkManager[724]: (eth1): new Ethernet device (driver: 'sky2' ifindex: 3) NetworkManager[724]: (eth1): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager[724]: (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] kernel: sky2 :04:00.0 eth0: enabling interface kernel: sky2 :03:00.0 eth1: enabling interface NetworkManager[724]: (eth1): preparing device NetworkManager[724]: urfkill disappeared from the bus that mobo have eth0 & eth1 ports, but only eth1 is used. As the last lines logged, networworkmanager is able to be loaded when the module sky2 is enabled. network-manager 0.9.10.0-4ubuntu13 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:41:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1442044/+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 1442044] Re: Ordering processes: networkmanager should wait for kernel'module been activated first before starting
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1518681 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1442044 Title: Ordering processes: networkmanager should wait for kernel'module been activated first before starting Status in One Hundred Papercuts: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: Get that journalctl log showing networkmanager starting before the related kernel'module been ready: systemd[1]: Starting Network. systemd[1]: Starting /etc/rc.local Compatibility... NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (lo): link connected NetworkManager[724]: (lo): carrier is ON NetworkManager[724]: (lo): new Generic device (driver: 'unknown' ifindex: 1) NetworkManager[724]: (lo): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth0): carrier is OFF NetworkManager[724]: (eth0): new Ethernet device (driver: 'sky2' ifindex: 2) NetworkManager[724]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 NetworkManager[724]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] NetworkManager[724]: (eth0): preparing device NetworkManager[724]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed NetworkManager[724]: (eth1): carrier is OFF NetworkManager[724]: (eth1): new Ethernet device (driver: 'sky2' ifindex: 3) NetworkManager[724]: (eth1): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager[724]: (eth1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] kernel: sky2 :04:00.0 eth0: enabling interface kernel: sky2 :03:00.0 eth1: enabling interface NetworkManager[724]: (eth1): preparing device NetworkManager[724]: urfkill disappeared from the bus that mobo have eth0 & eth1 ports, but only eth1 is used. As the last lines logged, networworkmanager is able to be loaded when the module sky2 is enabled. network-manager 0.9.10.0-4ubuntu13 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:41:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1442044/+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 1518681] Re: NM failed to initialize WiFi driver (after boot/ return from suspend)
This error is in the systemd boot logs: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1518681 Title: NM failed to initialize WiFi driver (after boot/ return from suspend) Status in network-manager package in Ubuntu: New Bug description: Since 15.10 my network is not working because of this bug. I got this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. Only workaround: sudo systemctl restart network-manager.service ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 22 11:23:48 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-11-21 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev wlxf81a67191694 proto static metric 600 169.254.0.0/16 dev wlxf81a67191694 scope link metric 1000 192.168.1.0/24 dev wlxf81a67191694 proto kernel scope link src 192.168.1.126 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxf81a67191694 wifi connected /org/freedesktop/NetworkManager/Devices/2 WG-WLAN c2683c87-f2df-40a9-b40b-d2b4ec6f1d12 /org/freedesktop/NetworkManager/ActiveConnection/0 eno1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1518681/+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 1518681] [NEW] NM failed to initialize WiFi driver (after boot/ return from suspend)
Public bug reported: Since 15.10 my network is not working because of this bug. I got this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. Only workaround: sudo systemctl restart network-manager.service ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 22 11:23:48 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-11-21 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IpRoute: default via 192.168.1.1 dev wlxf81a67191694 proto static metric 600 169.254.0.0/16 dev wlxf81a67191694 scope link metric 1000 192.168.1.0/24 dev wlxf81a67191694 proto kernel scope link src 192.168.1.126 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlxf81a67191694 wifi connected /org/freedesktop/NetworkManager/Devices/2 WG-WLAN c2683c87-f2df-40a9-b40b-d2b4ec6f1d12 /org/freedesktop/NetworkManager/ActiveConnection/0 eno1 ethernet unavailable /org/freedesktop/NetworkManager/Devices/0 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1518681 Title: NM failed to initialize WiFi driver (after boot/ return from suspend) Status in network-manager package in Ubuntu: New Bug description: Since 15.10 my network is not working because of this bug. I got this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. Only workaround: sudo systemctl restart network-manager.service ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov
[Touch-packages] [Bug 1434986] Re: Not working network connection after boot
I get this error: Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (wlan0): failed to initialize WiFi driver Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wlan0: factory failed to create device: (unknown) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: object NMDeviceWifi 0xeda450 finalized while still in-construction Nov 22 03:45:23 arbeits-pc NetworkManager[685]: (NetworkManager:685): GLib-GObject-CRITICAL **: Custom constructor for class NMDeviceWifi returned NULL (which is invalid). Please use GInitable instead. Nov 22 03:45:23 arbeits-pc NetworkManager[685]: wpa_supplicant running Nov 22 03:45:23 arbeits-pc NetworkManager[685]: devices added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694) Nov 22 03:45:23 arbeits-pc NetworkManager[685]: device added (path: /sys/devices/pci:00/:00:1a.0/usb5/5-1/5-1.4/5-1.4:1.0/net/wlxf81a67191694, iface: wlxf81a67191694): no ifupdown configuration found. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1424664] Re: no ifupdown configuration found
*** This bug is a duplicate of bug 1447146 *** https://bugs.launchpad.net/bugs/1447146 ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1424664 Title: no ifupdown configuration found Status in network-manager package in Ubuntu: Fix Released Bug description: booted with systemd-sysv found into syslog: NetworkManager[770]: management mode: unmanaged NetworkManager[770]: devices added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0) NetworkManager[770]: device added (path: /sys/devices/pci:00/:00:1c.3/:04:00.0/net/eth0, iface: eth0): no ifupdown configuration found. NetworkManager[770]: devices added (path: /sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1) NetworkManager[770]: device added (path: /sys/devices/pci:00/:00:1c.4/:03:00.0/net/eth1, iface: eth1): no ifupdown configuration found. NetworkManager[770]: devices added (path: /sys/devices/virtual/net/lo, iface: lo) NetworkManager[770]: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. NetworkManager[770]: end _init. NetworkManager[770]: (NetworkManager:770): GLib-CRITICAL **: g_dir_read_name: assertion 'dir != NULL' failed . NetworkManager[770]: (eth1): link connected NetworkManager[770]: (eth1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40] NetworkManager[770]: Auto-activating connection 'Wired connection 1'. Feb 23 15:06:39 u32 NetworkManager[770]: Activation (eth1) starting connection 'Wired connection 1' NetworkManager[770]: Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager[770]: Activation (eth1) Stage 1 of 5 (Device Prepare) started... NetworkManager[770]: (eth1): device state change: disconnected -> prepare (reason 'none') [30 40 0] NetworkManager[770]: NetworkManager state is now CONNECTING note: only eth1 is used to get stream; so it looks like a race as networkmanager seems working as expected; but what a confusing process: do really need a better design, because that one is a real mess. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-6.6-generic 3.19.0 Uname: Linux 3.19.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Mon Feb 23 15:45:26 2015 IpRoute: default via 192.168.1.1 dev eth1 proto static metric 1024 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.3 IwConfig: lono wireless extensions. eth0 no wireless extensions. eth1 no wireless extensions. RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 802-3-ethernet 1424702496 lun. 23 févr. 2015 15:41:36 CET yes no /org/freedesktop/NetworkManager/Settings/0 yes eth1activated /org/freedesktop/NetworkManager/ActiveConnection/0 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 7086b2ff-1446-45fe-b8f3-cd333cd4cee1 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1424664/+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 1434986] Re: Not working network connection after boot
please fix this, ist very annoying ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1434986 Title: Not working network connection after boot Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: Directly after boot the network connections are not working. I am connected and have an IP address, but I cannot establish a connection with any Internet server. I have the impression it is related to thee DNS lookup, which waits forever for a result. Cycling the connection (disconnect->reconnect) seems to fix the problem for some time. I am reporting this against network-manager, but I am not sure if it is directly in network manager or if it is systemd related. With 14.10 everything worked perfectly. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 22 12:38:26 2015 EcryptfsInUse: Yes IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-01-30 (50 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.26 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.29 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-03-19 (3 days ago) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2015-02-16T00:14:50.662693 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Kabelnetzwerkverbindung 1 4a581685-6002-4401-a993-49aa649667eb /org/freedesktop/NetworkManager/ActiveConnection/4 wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/1 4A616E7320574C414E f45aa3a7-fb44-41b7-a02a-ea9720d79414 /org/freedesktop/NetworkManager/ActiveConnection/3 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1434986/+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 1489154] Re: NetworkManager does not start / fails to start
the bug is still there -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1489154 Title: NetworkManager does not start / fails to start Status in One Hundred Papercuts: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: Yesterday i did the upgrade to version 1.0.4 of NetworkManger. Today my Xubuntu 15.10 cannot connect to the net, and wants to upload a crash report. This also fails cause the start of the NetworkManger fails after booting. Trying manually to start with ~$ sudo systemctl start NetworkManager leads that the icon comes up, disappears, comes up, disappears for 3, 4 times and then it's gone forever. ~$ journalctl -xe Aug 26 22:02:34 Wily NetworkManager[1578]: monitoring ifupdown state file '/run/network/ifstate'. Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVxlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMVethFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMTunFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMMacvlanFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMInfinibandFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMGreFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMEthernetFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBridgeFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBondFactory (internal) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMAtmManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-adsl.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWifiFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wifi.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMBluezManager (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) Aug 26 22:02:34 Wily NetworkManager[1578]: Loaded device plugin: NMWwanFactory (/usr/lib/i386-linux-gnu/NetworkManager/libnm-device-plugin-wwan.so) Aug 26 22:02:34 Wily NetworkManager[1578]: WiFi enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WWAN enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: WiMAX enabled by radio killswitch; enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: Networking is enabled by state file Aug 26 22:02:34 Wily NetworkManager[1578]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (lo): new Generic device (carrier: ON, driver: 'unknown', ifindex: 1) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): link connected Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): new Ethernet device (carrier: ON, driver: 'e1000', ifindex: 2) Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Aug 26 22:02:34 Wily NetworkManager[1578]: keyfile: add connection in-memory (4251ae7f-22a1-4de8-8f11-7a62fd420d65,"Kabelnetzwerkverbindung 1") Aug 26 22:02:34 Wily NetworkManager[1578]: (enp0s3): created default wired connection 'Kabelnetzwerkverbindung 1' Aug 26 22:02:34 Wily NetworkManager[1578]: urfkill disappeared from the bus Aug 26 22:02:34 Wily NetworkManager[1578]: wpa_supplicant running Aug 26 22:02:34 Wily NetworkManager[1578]: ModemManager available in the bus Aug 26 22:02:34 Wily NetworkManager[1578]: ofono is now available Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemAdded' is invalid for instance Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-GObject-WARNING **: /build/glib2.0-6GfMH1/glib2.0-2.45.4/./gobject/gsignal.c:2480: signal 'ModemRemoved' is invalid for instan Aug 26 22:02:34 Wily NetworkManager[1578]: (NetworkManager:1578): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Aug 26 22:02:34 Wily kernel: NetworkManager[1578]: segfault at c ip b6f4b97a sp bffb4890 error 4 in libglib-2.0.so.0.4504.0[b6ec8000+127000] Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV Aug 26 22:02:34 Wily systemd[1]: NetworkManager.service: Unit entered failed state. Aug 26 22:
[Touch-packages] [Bug 1438003] Re: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib.
Same bug on wily ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1438003 Title: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm- glib. Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Triaged Bug description: While attempting to connect to an SSID for the first time, it fails, and I consistently get: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/0' failed in libnm-glib. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Sun Mar 29 23:08:37 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.2 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected /org/freedesktop/NetworkManager/Devices/4 www.ubuntu.com 71c36534-c491-4479-aa91-9238b10f3945 /org/freedesktop/NetworkManager/ActiveConnection/1 wlan1 wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1438003/+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 1451448] Re: bzr fails to build on vivid (release) and trusty (test-rebuild only)
** Changed in: bzr Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1451448 Title: bzr fails to build on vivid (release) and trusty (test-rebuild only) Status in Bazaar: Fix Released Status in bzr package in Ubuntu: Confirmed Status in python2.7 package in Ubuntu: Invalid Status in bzr source package in Trusty: Fix Committed Status in python2.7 source package in Trusty: New Status in bzr source package in Vivid: Fix Released Status in python2.7 source package in Vivid: Invalid Status in bzr package in Debian: Fix Released Bug description: bzr fails to build on vivid (release) and trusty (test-rebuild only) various test failures seen, likely exposed by python 2.7.10. release: https://launchpad.net/ubuntu/+archive/test-rebuild-20150402/+build/7133674 test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20150501-updates/+build/7375272 how to validate: successful build. the testsuite is run during the build To manage notifications about this bug go to: https://bugs.launchpad.net/bzr/+bug/1451448/+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 1426930] Re: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
same issue for me on 14.04 normal update to vivid. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1426930 Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in fontconfig package in Ubuntu: Confirmed Bug description: I am new and I do not fully understand the technical issues but this occurred while I was repairing my GRUB. Thank You! ProblemType: Package DistroRelease: Ubuntu 14.04 Package: fontconfig 2.11.1-0ubuntu6 ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 Date: Sun Mar 1 09:20:08 2015 DuplicateSignature: package:fontconfig:2.11.1-0ubuntu6:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-19 (40 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: fontconfig Title: package fontconfig 2.11.1-0ubuntu6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1426930/+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 1408963] Re: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 0000:03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by lo
The intermittent disconnection still happens with kernel 4.2.0-16-generic. It does not happen on 2.4 ghz network though. The method suggested on http://ubuntuforums.org/showthread.php?t=2259037&p=13198699#post13198699 seems to be working for me. I'm quoting here: sudo iw reg set IN sudo sed -i 's/^REG.*=$/&IN/' /etc/default/crda -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1408963 Title: [Xbuntu 14.04, 14.10 and 15.04] Network manager stops working: iwl3945 :03:00.0: BSM uCode verification failed at addr ...; wlan0: deauthenticating from... by local choice (Reason: 3=DEAUTH_LEAVING), Status in linux-firmware package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: From time to time, the system loses all wireles networks and kubuntu network manager applet goes blank - not even one network is shown. All wifi connections are broken. Rebooting fixes the issue, switching to WICD on-the-fly enables to continue browsing without rebooting, so it seems to be no hardware issue or iwl3945 issue. What to expect: stable connections and flawless network managing. What happens: so above. Further informations about the system, the network configuration, the package version can be found in the attachment, also parts of rsyslog and dmesg. Interesting, according to some helpers, are the following lines: dmesg: wlan0: deauthenticating from 02:26:4d:ac:8f:45 by local choice (Reason: 3=DEAUTH_LEAVING) lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 14.10 Release:14.10 Codename: utopic apt-cache policy network-manager network-manager: Installiert: 0.9.8.8-0ubuntu28 Installationskandidat: 0.9.8.8-0ubuntu28 Versionstabelle: *** 0.9.8.8-0ubuntu28 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1408963/+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 702452]
The default when AppUserModelID's are implemented should be the full path to the .exe file (exe's with the same filename in different directories do not group together on windows), so that's what I'd suggest setting WM_CLASS to. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/702452 Title: [launcher] Wine applications are wrongly matched Status in BAMF: Confirmed Status in libwnck: Fix Released Status in Unity: Confirmed Status in Wine: Unknown Status in bamf package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: After launching a Wine app from terminal or via gnome-do, it appears in the launcher with the Wine icon, instead of its own icon. The title is "Wine Window Program Loader" instead of the proper application name. It can't be favorited since it will favorite the wine executable itself. And obviously different wine apps are all grouped under the same launcher icon. See also bug #635223 about Wine applications not showing up in the dash. - A way to fix this is to make all the Wine generated .desktop file to include a StartupWMClass value that matches the instance name of the related program (generally the .exe file name to be executed). So for example, a "Mozilla Firefox.desktop" file can be easily fixed adding this parameter: StartupWMClass=firefox.exe Wine should try to add this information at file generation time. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/702452/+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 1492144] Re: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
*** This bug is a duplicate of bug 1482439 *** https://bugs.launchpad.net/bugs/1482439 same as comment #12 for me. disabling wifi caused this bug in my case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Confirmed Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+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 269170] Re: NetworkManager crashed with SIGSEGV in g_main_context_dispatch()
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/269170 Title: NetworkManager crashed with SIGSEGV in g_main_context_dispatch() Status in network-manager package in Ubuntu: Invalid Bug description: Binary package hint: network-manager Network Manager Crashes @ boottime, not able to start it ... ProblemType: Crash Architecture: amd64 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/sbin/NetworkManager Gconf: Package: network-manager 0.7~~svn20080908t183521+eni0-0ubuntu2 ProcCmdline: /usr/sbin/NetworkManager ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin Signal: 11 SourcePackage: network-manager StacktraceTop: ?? () ?? () g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 ?? () from /usr/lib/libglib-2.0.so.0 g_main_loop_run () from /usr/lib/libglib-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_main_context_dispatch() Uname: Linux 2.6.27-3-generic x86_64 UserGroups: mythtv WpaSupplicantLog: CTRL-EVENT-SCAN-RESULTS CTRL-EVENT-TERMINATING - signal 15 received To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/269170/+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 1134060] Re: network-manager selects a random connection, not the last used
** This bug is no longer a duplicate of bug 996939 After resume from suspend, NM should activate the most recently used (rather than some other "Connect automatically") connection -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1134060 Title: network-manager selects a random connection, not the last used Status in network-manager package in Ubuntu: Confirmed Bug description: Having multiple wired and wireless network settings. Using 1 wired and 1 wireless at the same time. At startup, NM connects to networks that i don't want. Ethernet and wireless networks Seems to be randomly selected. I have to unckeck "Automatically connects to this network when it's available" to prevent that but it's not very user friendly. It should connect at the last network used. It worked like that before raring ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 27 08:53:51 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2011-10-14 (501 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.254 dev wlan0 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.149.0.0/24 dev eth1 proto kernel scope link src 192.149.0.47 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.13 metric 9 195.25.246.12 via 192.149.0.251 dev eth1 proto static MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-02-21 (5 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1134060/+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 1134060] Re: network-manager selects a random connection, not the last used
*** This bug is a duplicate of bug 996939 *** https://bugs.launchpad.net/bugs/996939 ** This bug has been marked a duplicate of bug 996939 After resume from suspend, NM should activate the most recently used (rather than some other "Connect automatically") connection -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1134060 Title: network-manager selects a random connection, not the last used Status in network-manager package in Ubuntu: Confirmed Bug description: Having multiple wired and wireless network settings. Using 1 wired and 1 wireless at the same time. At startup, NM connects to networks that i don't want. Ethernet and wireless networks Seems to be randomly selected. I have to unckeck "Automatically connects to this network when it's available" to prevent that but it's not very user friendly. It should connect at the last network used. It worked like that before raring ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: network-manager 0.9.7.995+git201301311547.17123fc-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0 Uname: Linux 3.8.0-7-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Wed Feb 27 08:53:51 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationDate: Installed on 2011-10-14 (501 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IpRoute: default via 192.168.0.254 dev wlan0 proto static 169.254.0.0/16 dev eth1 scope link metric 1000 192.149.0.0/24 dev eth1 proto kernel scope link src 192.149.0.47 metric 1 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.13 metric 9 195.25.246.12 via 192.149.0.251 dev eth1 proto static MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to raring on 2013-02-21 (5 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetconnected /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.7.995 connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1134060/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- 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/1333140 Title: Fix udev rules to consider mmc rpmb partitions Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: New Status in udev package in Ubuntu: Invalid Status in udisks package in Ubuntu: Triaged Status in udev source package in Precise: Triaged Status in udisks source package in Precise: Confirmed Status in systemd source package in Trusty: Fix Released Status in udisks source package in Trusty: Confirmed Bug description: As per JEDEC 4.5 spec for eMMC devices, There is a new partitions as part of eMMC storage devices it self. (Further details please refer eMMC spec) *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions with "mmcblkXrpmb" if device expresses it support of RPMB. Issues observed: issue 1: RPMB (Replay Protected Memory Block), A signed access to a Replay Protected Memory Block is provided. This function provides means for the system to store data to the specific memory area in an authenticated and replay protected manner. In that case, any read/write access to this partition device will report errors. issue 2: The by-path, line is wrongly mapping to platform-sdhci-tegra.1 -> mmcblk2rpmb were as it should be platform-sdhci-tegra.1 -> mmcblk2 ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 -> ../../mmcblk2rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 -> ../../mmcblk2p1 lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 -> ../../mmcblk1p1 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 -> ../../mmcblk0rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 -> ../../mmcblk0p2 We have locally resolved in our platform in this file 60-persistent- storage.rules For issue 1: (with this rule) # skip block read for partitions of type rpmb KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end" For issue 2: ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb" ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}" Please consider this issues fix in next udev release . SRU INFO: This is mostly an issue with running backported kernels on 12.04 and 14.04. There is no test case which would reproduce this on arbitrary hardware, but there are several reporters which are in a position to verify a proposed update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
** Tags added: vivid -- 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/1333140 Title: Fix udev rules to consider mmc rpmb partitions Status in systemd package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: New Status in udev package in Ubuntu: Invalid Status in udisks package in Ubuntu: Triaged Status in udev source package in Precise: Triaged Status in udisks source package in Precise: Confirmed Status in systemd source package in Trusty: Fix Released Status in udisks source package in Trusty: Confirmed Bug description: As per JEDEC 4.5 spec for eMMC devices, There is a new partitions as part of eMMC storage devices it self. (Further details please refer eMMC spec) *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions with "mmcblkXrpmb" if device expresses it support of RPMB. Issues observed: issue 1: RPMB (Replay Protected Memory Block), A signed access to a Replay Protected Memory Block is provided. This function provides means for the system to store data to the specific memory area in an authenticated and replay protected manner. In that case, any read/write access to this partition device will report errors. issue 2: The by-path, line is wrongly mapping to platform-sdhci-tegra.1 -> mmcblk2rpmb were as it should be platform-sdhci-tegra.1 -> mmcblk2 ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 -> ../../mmcblk2rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 -> ../../mmcblk2p1 lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 -> ../../mmcblk1p1 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 -> ../../mmcblk0rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 -> ../../mmcblk0p2 We have locally resolved in our platform in this file 60-persistent- storage.rules For issue 1: (with this rule) # skip block read for partitions of type rpmb KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end" For issue 2: ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb" ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}" Please consider this issues fix in next udev release . SRU INFO: This is mostly an issue with running backported kernels on 12.04 and 14.04. There is no test case which would reproduce this on arbitrary hardware, but there are several reporters which are in a position to verify a proposed update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1333140] Re: Fix udev rules to consider mmc rpmb partitions
It's also important that you fix the live medium + installer because it takes a long time to boot up an install ubuntu. -- 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/1333140 Title: Fix udev rules to consider mmc rpmb partitions Status in systemd package in Ubuntu: Fix Released Status in udev package in Ubuntu: Invalid Status in udisks package in Ubuntu: Triaged Status in udev source package in Precise: Triaged Status in udisks source package in Precise: Confirmed Status in systemd source package in Trusty: Fix Released Status in udisks source package in Trusty: Confirmed Bug description: As per JEDEC 4.5 spec for eMMC devices, There is a new partitions as part of eMMC storage devices it self. (Further details please refer eMMC spec) *In Linux Kernel@ 3.10.33, mmc driver has created a new partitions with "mmcblkXrpmb" if device expresses it support of RPMB. Issues observed: issue 1: RPMB (Replay Protected Memory Block), A signed access to a Replay Protected Memory Block is provided. This function provides means for the system to store data to the specific memory area in an authenticated and replay protected manner. In that case, any read/write access to this partition device will report errors. issue 2: The by-path, line is wrongly mapping to platform-sdhci-tegra.1 -> mmcblk2rpmb were as it should be platform-sdhci-tegra.1 -> mmcblk2 ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.1 -> ../../mmcblk2rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.1-part1 -> ../../mmcblk2p1 lrwxrwxrwx 1 root root 13 Jan 3 2000 platform-sdhci-tegra.2 -> ../../mmcblk1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.2-part1 -> ../../mmcblk1p1 lrwxrwxrwx 1 root root 17 Jan 3 2000 platform-sdhci-tegra.3 -> ../../mmcblk0rpmb lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part1 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Jan 3 2000 platform-sdhci-tegra.3-part2 -> ../../mmcblk0p2 We have locally resolved in our platform in this file 60-persistent- storage.rules For issue 1: (with this rule) # skip block read for partitions of type rpmb KERNEL=="mmcblk[0-9]rpmb", SUBSYSTEM=="block", GOTO="persistent_storage_end" For issue 2: ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL=="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}-rpmb" ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="?*", KERNEL!="mmcblk[0-9]rpmb", SYMLINK+="disk/by-path/$env{ID_PATH}" Please consider this issues fix in next udev release . SRU INFO: This is mostly an issue with running backported kernels on 12.04 and 14.04. There is no test case which would reproduce this on arbitrary hardware, but there are several reporters which are in a position to verify a proposed update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1333140/+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 1370245] Re: wpa_supplicant version 2.2 available
just wanted to note that 2.4 seems broken, at least in Fedora for some setups of wireless networks: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1473088 a fix in 14.04 seems reasonable, maybe by upgrading to 2.3 if possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1370245 Title: wpa_supplicant version 2.2 available Status in wpa package in Ubuntu: Fix Released Status in wpasupplicant package in Ubuntu: Won't Fix Bug description: Currently version 2.1 is still the version slated to be shipped with utopic. It seems from http://w1.fi/wpa_supplicant/ that wpa_supplicant version 2.2 was released in 2014-06. Is it possible for 2.2 to be packaged? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1370245/+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 1323594] Re: vpn auto-connect works, but doesn't connect automatically when network is available.
Looks like NetworkManager is having issues getting the user's VPN password from gnome-key-daemon. I've posted a workaround at http://askubuntu.com/a/332796/109757. Basically, change password-flags=1 to password-flags=0 in /etc/NetworkManager/system-connections/ (warning: this will store the VPN password in plaintext). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1323594 Title: vpn auto-connect works, but doesn't connect automatically when network is available. Status in network-manager package in Ubuntu: Confirmed Bug description: I'm having a bug in Ubuntu Trusty Tahr 14.04 LTS. The issue I'm having is that with a connection set to auto-connect to a PPTP-vpn, it does not auto-connect when (wireless)-network becomes available. Syslog returns this error: [1401130450.367538] [nm-vpn-connection.c:1374] get_secrets_cb(): Failed to request VPN secrets #2: (6) No agents were available for this request. However it does connect when when connecting to the particular connection manually. e.g. I select the wireless network in the network-manager. This bug seems related to bugs: #280571 #1297849 #1247682 #1298047 The difference between my situation and the others is that vpn- autoconnect does work, it just doesn't work automatically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1323594/+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 1440294] Re: syncevolution - no export of tasks / memos Aquaris E4.5
Do you use Thunderbird + Lightning ? Could you try to create a note / memo / task from it and tell me which database is set? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to syncevolution in Ubuntu. https://bugs.launchpad.net/bugs/1440294 Title: syncevolution - no export of tasks / memos Aquaris E4.5 Status in syncevolution package in Ubuntu: Confirmed Bug description: Phone: bq Aquaris E4.5 Ubuntu Edtion OS: Ubuntu 14.10(r20) SyncEvolution 1.5 Can not export my Tasks and memos. Calendar and contacts export works! phablet@ubuntu-phablet:~$ syncevolution --print-databases CalDAV: select database via absolute URL, set username/password to scan, set syncURL to base URL if server does not support auto-discovery () CalDAVTodo: select database via absolute URL, set username/password to scan, set syncURL to base URL if server does not support auto-discovery () CalDAVJournal: select database via absolute URL, set username/password to scan, set syncURL to base URL if server does not support auto-discovery () CardDAV: select database via absolute URL, set username/password to scan, set syncURL to base URL if server does not support auto-discovery () Evolution Address Book = Evolution Contacts = evolution-contacts: Persönlich (system-address-book) Evolution Calendar = evolution-calendar: Geburts- & Jahrestage (birthdays) Persönlich (system-calendar) Evolution Task List = Evolution Tasks = evolution-tasks: Alarms (1427538744.24638.0@ubuntu-phablet) Persönlich (system-task-list) Reminders (1427534898.18825.0@ubuntu-phablet) Evolution Memos = evolution-memos: Persönlich (system-memo-list) phablet@ubuntu-phablet:~$ syncevolution --export tasks backend=evolution-tasks phablet@ubuntu-phablet:~$ file tasks tasks: empty phablet@ubuntu-phablet:~$ syncevolution --print-items backend =evolution-tasks phablet@ubuntu-phablet:~$ syncevolution --print-items backend =evolution-memos phablet@ubuntu-phablet:~$ click list com.canonical.payui 15.01.120 com.canonical.scopes.bbc-sport1.03 com.canonical.scopes.etsy 1.0.29 com.canonical.scopes.euronews 0.5 com.canonical.scopes.fitbit 1.0.40 com.mikeasoft.podbird 0.5 com.ubuntu.calendar 0.4.600 com.ubuntu.camera 3.0.0.544 com.ubuntu.developer.bobo1993324.qvbam0.1.3.1 com.ubuntu.developer.liberavia.ardmediathek 0.1 com.ubuntu.developer.majster-pl.utorch1.6 com.ubuntu.developer.mzanetti.leo 0.2 com.ubuntu.developer.ogra.rtv-de 0.3 com.ubuntu.developer.tyrelparker0.metalhammer 0.2 com.ubuntu.docviewer 0.3.109 com.ubuntu.filemanager0.4.386 com.ubuntu.gallery2.9.1.1183 com.ubuntu.music 2.0.846 com.ubuntu.reminders 0.5.380 com.ubuntu.scopes.soundcloud 1.0.1-39 com.ubuntu.scopes.vimeo 1.0.2-84 com.ubuntu.telegram 1.1.2.95 com.ubuntu.terminal 0.7.70 dekko.dekkoproject0.5.1 help.ubuntucoredev0.2 noobslabscope.noobslab0.1.1 omgubuntu-scope.mreese1.4 com.canonical.scopes.bbc 1.7 com.canonical.scopes.calls1.1 com.canonical.scopes.cnet 0.6 com.canonical.scopes.contacts 0.7 com.canonical.scopes.dashboard1.6 com.canonical.scopes.engadget 0.5 com.canonical.scopes.events 1.0.11 com.canonical.scopes.fbphotos 1.23 com.canonical.scopes.flickr 1.0.24 com.canonical.scopes.hints0.20 com.canonical.scopes.holidays 1.1 com.canonical.scopes.inrix1.0.28 com.canonical.scopes.instagram1.0.15 com.canonical.scopes.news 2.13 com.canonical.scopes.photos 1.31 com.canonical.scopes.photos-local 1.23 com.canonical.scopes.poi 1.0.11 com.canonical.scopes.shopping 1.9 com.canonical.scopes.songkick 1.0.11 com.canonical.scopes.tasks1.3 com.canonical.scopes.texts1.0 com.canonical.scopes.timeout 0.4.12 com.canonical.scopes.transport-alerts 1.10 com.canonical.scopes.twittertrending 1.0.9 com.canonical.scopes.wikinear 1.0.9 com.canonical.scopes.yelp 1.0.34 com.canonical.unity-scope-nearby 0.8.8 com.nokia.heremaps1.0.4 com.ubuntu.developer.ken-vandine.pathwind 0.2.9 com.ubuntu.developer.mzanetti.tagger 0.9.0.0 com.ubuntu.developer.webapps.webapp-twitter 1.0.21 com.zeptolab.cuttherope.free 0.5.1 com.ubuntu.calculator 1.3.339 com.ubuntu.clock 3.3.192 com.ubuntu.scopes.youtube 1.0.18-134 com.ubuntu.weather1.1.403 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syncevolution/+bug/1440294/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
@Chris: Thanks ! I had to implement a different scheme not using nested containers but still requiring lxc-1.1.2. I'll give nested containers another shot asap. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update && sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1462739] [NEW] USB devices disconnected when logon is displayed
Public bug reported: I am running Ubuntu 14.04 on Asus N750JV (Core I7). Randomly, after ubuntu boots, I am losing the mouse. Sometimes I need to reboot once, sometmes 10 times before it comes back. I am also losing DCard port. In the details: - at bios, the mouse is enabled (the camera light is on) - during boot, it is on - just when the login interface is displayed, the mouse is diabled (the light is off) I join the dmesg logs | grep usb, so you start investigate; it seems the mouse is disable because the device is not reponding to usb set_address command. ** Affects: libusb (Ubuntu) Importance: Undecided Status: New ** Tags: 14.04 asus mouse n750 usb ** Attachment added: "dmesg_USB_error.log" https://bugs.launchpad.net/bugs/1462739/+attachment/4411053/+files/dmesg_USB_error.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1462739 Title: USB devices disconnected when logon is displayed Status in libusb package in Ubuntu: New Bug description: I am running Ubuntu 14.04 on Asus N750JV (Core I7). Randomly, after ubuntu boots, I am losing the mouse. Sometimes I need to reboot once, sometmes 10 times before it comes back. I am also losing DCard port. In the details: - at bios, the mouse is enabled (the camera light is on) - during boot, it is on - just when the login interface is displayed, the mouse is diabled (the light is off) I join the dmesg logs | grep usb, so you start investigate; it seems the mouse is disable because the device is not reponding to usb set_address command. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libusb/+bug/1462739/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
@Chris: Where do you add the ubuntu-lxc/daily ppa ? On the host or on the outer container ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update && sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1436723] Re: Regression: Nested LXC is broken on Vivid
I run into the same issue on a vivid host while trying to start a trusty nested container from inside a trusty container. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: Confirmed Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) -> Trusty (Outer LXC) -> Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc-container-default-with-nesting' >> /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update && sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1398614] Re: mediascanner-service-2.0 using large amounts of CPU
Is there a global way to disable that thing other than "apt-get purge" ? I don't want my CPU to be hogged every time I plug a removable drive. Please stop blindly abusing our resources without giving us a way to escape from it, pretty please. What would be acceptable is a (***not hidden away***) config option where one can choose to "always scan", "always ask" or "never scan"... The same we we can choose to auto-run, auto-launch, auto-open, etc... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1398614 Title: mediascanner-service-2.0 using large amounts of CPU Status in mediascanner2 package in Ubuntu: Confirmed Bug description: Each time I plug my external USB hard disk the mediascanner-service process is activ and is using large amount of CPU for long minutes without interruption. I have the same problem in utopic and vivid ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: mediascanner2.0 0.105+15.04.20141030.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Wed Dec 3 00:29:43 2014 InstallationDate: Installed on 2011-05-26 (1286 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: mediascanner2 UpgradeStatus: Upgraded to vivid on 2013-11-26 (371 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1398614/+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 1439101] Re: impossible receive MMS any operator on bq aquaris E4.5
I send and receive mms without problem here in Switzerland (operator Sunrise). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1439101 Title: impossible receive MMS any operator on bq aquaris E4.5 Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu Mobile: New Status in messaging-app package in Ubuntu: Confirmed Status in telephony-service package in Ubuntu: Confirmed Bug description: In France no MMS is received regardless of the operator used on bq aquaris E4.5 ubuntu Edition For information, my operator is Free even if it seems it doesn't matter. In the same time, let me tell you than I had detect than MMS didn't sent when WIFI is ON. I've read some other people who send the same information so it's seems to be a real bug. Anyway, for resume, For send a MMS, it's OK whan WIFI is OFF, don'T if ON, and in all of case we don't receive MMS :-(( Thank's to you for fix it faster. Sorry for my approximativ english. Fabien To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1439101/+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 1421009] Re: unity8 sometimes hangs on boot
@Pat: Just in case, I'm on vivid and use autopkgtest 3.13, that may be related. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a "Error: Timeout was reached" message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == # Prepare debugging adb shell sudo apt install qtbase5-dbg libc6-dbg # Start the reboot loop # This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang eventually. Current highest amount of reboots without errors is 54, so it's probable a 100 reboots is needed for testing. bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R "~phablet/.cache/QML"; ./tools/unlock-device || break; done # When it fails adb shell sudo gdb -p $(pidof unity8) bt -- At this point, the backtrace should show: #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37 #1 0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=) at thread/qmutex_linux.cpp:146 #2 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:187 #3 QBasicMutex::lockInternal (this=this@entry=0x1523b44) at thread/qmutex_linux.cpp:203 #4 0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59 #5 lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620 #6 QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215 #7 0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, a=ToggleWatchAction, this=) at qdbusthreaddebug_p.h:183 #8 QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, this=) at qdbusthreaddebug_p.h:198 #9 qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46) at qdbusintegrator.cpp:346 #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3 With this, it's know that it was a QDBus locking related problem. -- --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421009/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://la
[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot
@Pat: Can you re-try adding '-d' to your adt-run options and share the log ? /tmp/autopkgtest-reboot is created by adt-run on the testbed at run time. I'm eager to learn how such a failure can happen and where it needs to be fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a "Error: Timeout was reached" message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == # Prepare debugging adb shell sudo apt install qtbase5-dbg libc6-dbg # Start the reboot loop # This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang eventually. Current highest amount of reboots without errors is 54, so it's probable a 100 reboots is needed for testing. bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R "~phablet/.cache/QML"; ./tools/unlock-device || break; done # When it fails adb shell sudo gdb -p $(pidof unity8) bt -- At this point, the backtrace should show: #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37 #1 0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=) at thread/qmutex_linux.cpp:146 #2 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:187 #3 QBasicMutex::lockInternal (this=this@entry=0x1523b44) at thread/qmutex_linux.cpp:203 #4 0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59 #5 lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620 #6 QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215 #7 0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, a=ToggleWatchAction, this=) at qdbusthreaddebug_p.h:183 #8 QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, this=) at qdbusthreaddebug_p.h:198 #9 qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46) at qdbusintegrator.cpp:346 #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3 With this, it's know that it was a QDBus locking related problem. -- --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixes a simple test case, and seems to fix UITK suite as a whole, but on krillin only 2015-04-10: Further patches from upstream fix all AP tests. 2015-04-23: Upstream continues to work on the patches but they have not yet been merged. AP:s pass, but U1 account gets removed usually after a reboot, even though apps can be installed after adding U1 account flawlessly for the duration of that boot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug
[Touch-packages] [Bug 1421009] Re: unity8 sometimes hangs on boot
Also reproduced on arale with the branch above after 25 reboots. $ adb shell system-image-cli -i current build number: 22 device name: arale channel: ubuntu-touch/arale-vivid-proposed last update: 2010-01-01 00:29:22 version version: 22 version ubuntu: 30e975dd988b3be7886017b6d46b2821da187d7b8e5e4c7a30b953114b50bb15 version device: 998baf0435d37e42421b39c34a27ed5f872c145f1d2016e08f477d9ad6b8a654 version custom: 76da72854bde96be6e9d546a607550a952b75ca9c3143e0002f457f826056e87 In addition, the first time I ran this test I ended up with a black screen with only the tiny ubuntu logo after two reboots only. Rebooting the phone from the power button was enough to recover it though. Looks like this test can reproduce more than one bug ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to autopilot in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in the base for Ubuntu mobile products: In Progress Status in autopilot package in Ubuntu: Fix Released Status in libusermetrics package in Ubuntu: Invalid Status in lxc-android-config package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a "Error: Timeout was reached" message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. == Test Case == # Prepare debugging adb shell sudo apt install qtbase5-dbg libc6-dbg # Start the reboot loop # This reboots the device in a loop, and if this bug is not fixed by whatever proposed solution, it will hang eventually. Current highest amount of reboots without errors is 54, so it's probable a 100 reboots is needed for testing. bzr branch lp:unity8 cd unity8 while true; do adb shell rm -R "~phablet/.cache/QML"; ./tools/unlock-device || break; done # When it fails adb shell sudo gdb -p $(pidof unity8) bt -- At this point, the backtrace should show: #0 syscall () at ../sysdeps/unix/sysv/linux/arm/syscall.S:37 #1 0xb6301e12 in _q_futex (op=0, val=3, timeout=0x0, addr=) at thread/qmutex_linux.cpp:146 #2 lockInternal_helper (timeout=-1, elapsedTimer=0x0, d_ptr=...) at thread/qmutex_linux.cpp:187 #3 QBasicMutex::lockInternal (this=this@entry=0x1523b44) at thread/qmutex_linux.cpp:203 #4 0xb6301eb6 in lock (this=0x1523b44) at thread/qmutex.h:59 #5 lock (timeout=-1, this=0x1523b38) at thread/qmutex.cpp:620 #6 QMutex::lock (this=this@entry=0x1523d6c) at thread/qmutex.cpp:215 #7 0xb5f39586 in QDBusMutexLocker (m=0x1523d6c, s=0x1523d48, a=ToggleWatchAction, this=) at qdbusthreaddebug_p.h:183 #8 QDBusDispatchLocker (s=0x1523d48, a=ToggleWatchAction, this=) at qdbusthreaddebug_p.h:198 #9 qDBusRealToggleWatch (d=0x1523d48, watch=0x1524dd0, fd=46) at qdbusintegrator.cpp:346 #10 0xb5ae18f6 in ?? () from /lib/arm-linux-gnueabihf/libdbus-1.so.3 With this, it's know that it was a QDBus locking related problem. -- --- Timeline/Updates: 2015-02-20: libusermetrics lands, causing (apparently) this boot problem to start happening rarely. http://people.canonical.com/~ogra/touch-image-stats/106.changes / http://launchpadlibrarian.net/198152771/libusermetrics_1.1.1%2B14.10.20141020-0ubuntu1_1.1.1%2B15.04.20150219-0ubuntu1.diff.gz ”I got a symbolic trace out of all the threads. It seems to be a dbus lock between usermetrics and networkmanager bits. We suspect a relation to QTBUG https://bugreports.qt.io/browse/QTBUG-44836.” 2015-03-25: qtbase dbus update to support threads (instead of one main thread) in PPA 018 fixes the boot issue, but autopilot test suites start failing randomly. 2015-03-27: an autopilot fix fixe