[Touch-packages] [Bug 2055270] [NEW] Buy Tramadol Online At Lowest Prices
*** This bug is a security vulnerability *** Public security bug reported: Buy Tramadol Online 100mg USA Overnight ➤Order here: https://t.ly/N0hN9 ➤Shop Here: https://t.ly/N0hN9 Tramadol 100mg may interact with other medications, including certain antidepressants, antipsychotics, and medications that affect serotonin levels. It's important to inform your healthcare provider about all medications you are taking, including prescription, over-the-counter, and herbal supplements, to avoid potential interactions. Tramadol should not be used in combination with alcohol or other substances that depress the central nervous system, as this can increase the risk of respiratory depression and other serious side effects. People with a history of substance abuse or addiction should use tramadol with caution, as it has the potential for misuse, dependence, and addiction. Tramadol is not recommended for use in children under the age of 12, as its safety and efficacy in this population have not been established. Older adults may be more sensitive to the side effects of tramadol, particularly dizziness and drowsiness, and may require lower doses or closer monitoring. It's essential to follow your healthcare provider's instructions carefully when taking tramadol 100mg and to report any side effects or concerns promptly. Additionally, do not stop taking tramadol suddenly without consulting your doctor, as this can lead to withdrawal symptoms. If you have any questions or uncertainties about tramadol or its use, don't hesitate to discuss them with your healthcare provider. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Public Security -- 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/2055270 Title: Buy Tramadol Online At Lowest Prices Status in systemd package in Ubuntu: New Bug description: Buy Tramadol Online 100mg USA Overnight ➤Order here: https://t.ly/N0hN9 ➤Shop Here: https://t.ly/N0hN9 Tramadol 100mg may interact with other medications, including certain antidepressants, antipsychotics, and medications that affect serotonin levels. It's important to inform your healthcare provider about all medications you are taking, including prescription, over-the-counter, and herbal supplements, to avoid potential interactions. Tramadol should not be used in combination with alcohol or other substances that depress the central nervous system, as this can increase the risk of respiratory depression and other serious side effects. People with a history of substance abuse or addiction should use tramadol with caution, as it has the potential for misuse, dependence, and addiction. Tramadol is not recommended for use in children under the age of 12, as its safety and efficacy in this population have not been established. Older adults may be more sensitive to the side effects of tramadol, particularly dizziness and drowsiness, and may require lower doses or closer monitoring. It's essential to follow your healthcare provider's instructions carefully when taking tramadol 100mg and to report any side effects or concerns promptly. Additionally, do not stop taking tramadol suddenly without consulting your doctor, as this can lead to withdrawal symptoms. If you have any questions or uncertainties about tramadol or its use, don't hesitate to discuss them with your healthcare provider. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2055270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2043915] Re: Booting into live session results in try/install page white screen
I used build 20240116 today and was able to install normally. Thank you all! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2043915 Title: Booting into live session results in try/install page white screen Status in ubuntu-desktop-installer: New Status in mesa package in Ubuntu: Fix Released Bug description: Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into live session results in try/install page white screen.Selecting install from the dash results in same white screen. see the attached screen shot ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: subiquity (unknown) ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.487 CloudArchitecture: x86_64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud) CurrentDesktop: ubuntu:GNOME Date: Sun Nov 19 07:02:48 2023 LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119) ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: subiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2035339] [NEW] libperl5.30 crash (segfault) at Perl__invlist_intersection_maybe_complement_2nd during nginx reload
Public bug reported: On Focal, I got this in my kern.log: nginx[533]: segfault at 739 ip 7fadc806d5d9 sp 7ffc04f5cd50 error 4 in libperl.so.5.30.0[7fadc8005000+166000] Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d Looking at IP ( 0x7fadc806d5d9 - 0x7fadc8005000 ) it appeared to point at 0x685D9 in libperl.so.5.30.0. # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 685D9 Perl_vload_module op.c:7752 But when looking at the code, it looks like it's at 0x685D9 + 0x48000 = 0xB05D9: # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 B05D9 Perl__invlist_intersection_maybe_complement_2nd regcomp.c:9841 This makes more sense: # objdump -d /usr/lib/x86_64-linux-gnu/libperl.so.5.30 ... 000b0500 : ... b05cd: 4c 8d 0c c2 lea(%rdx,%rax,8),%r9 b05d1: 84 c9 test %cl,%cl b05d3: 0f 84 c7 02 00 00 je b08a0 b05d9: 49 83 39 00 cmpq $0x0,(%r9) <-- here b05dd: 0f 85 ad 03 00 00 jneb0990 b05e3: 49 83 c1 08 add$0x8,%r9 b05e7: 49 83 ed 01 sub$0x1,%r13 There's a similar segfault: nginx[356456]: segfault at 10 ip 7f4f576785a3 sp 7ffd0be49220 error 4 in libperl.so.5.30.0[7f4f5761+166000] Code: 48 89 43 10 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 0f b6 7f 30 48 c1 e8 03 48 29 f8 48 89 c3 74 89 48 8b 02 <4c> 8b 68 10 4d 85 ed 0f 84 28 01 00 00 0f b6 40 30 49 c1 ed 03 49 That is on 0xB05A3, also in Perl__invlist_intersection_maybe_complement_2nd: b0598: 48 29 f8sub%rdi,%rax b059b: 48 89 c3mov%rax,%rbx b059e: 74 89 je b0529 b05a0: 48 8b 02mov(%rdx),%rax b05a3: 4c 8b 68 10 mov0x10(%rax),%r13 <-- here b05a7: 4d 85 edtest %r13,%r13 b05aa: 0f 84 28 01 00 00 je b06d8 On GitHub I found a bug filed for perl 5.30 and this function: https://github.com/Perl/perl5/issues/17154 That issue is fixed in perl 5.32.0 and beyond (across multiple commits). Apparently the bug triggers every now and then, but was not common enough to be noticed. And looking at the timestamps, it is always during an nginx reload. Cheers, Walter Doekes OSSO B.V. ** Affects: perl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2035339 Title: libperl5.30 crash (segfault) at Perl__invlist_intersection_maybe_complement_2nd during nginx reload Status in perl package in Ubuntu: New Bug description: On Focal, I got this in my kern.log: nginx[533]: segfault at 739 ip 7fadc806d5d9 sp 7ffc04f5cd50 error 4 in libperl.so.5.30.0[7fadc8005000+166000] Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d Looking at IP ( 0x7fadc806d5d9 - 0x7fadc8005000 ) it appeared to point at 0x685D9 in libperl.so.5.30.0. # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 685D9 Perl_vload_module op.c:7752 But when looking at the code, it looks like it's at 0x685D9 + 0x48000 = 0xB05D9: # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 B05D9 Perl__invlist_intersection_maybe_complement_2nd regcomp.c:9841 This makes more sense: # objdump -d /usr/lib/x86_64-linux-gnu/libperl.so.5.30 ... 000b0500 : ... b05cd: 4c 8d 0c c2 lea(%rdx,%rax,8),%r9 b05d1: 84 c9 test %cl,%cl b05d3: 0f 84 c7 02 00 00 je b08a0 b05d9: 49 83 39 00 cmpq $0x0,(%r9) <-- here b05dd: 0f 85 ad 03 00 00 jneb0990 b05e3: 49 83 c1 08 add$0x8,%r9 b05e7: 49 83 ed 01 sub$0x1,%r13 There's a similar segfault: nginx[356456]: segfault at 10 ip 7f4f576785a3 sp 7ffd0be49220 error 4 in libperl.so.5.30.0[7f4f5761+166000] Code: 48 89 43 10 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 0f b6 7f 30 48 c1 e8 03 48 29 f8 48 89 c3 74 89 48 8b 02 <4c> 8b 68 10 4d 85 ed 0f 84 28 01 00 00 0f b6 40 30 49 c1 ed 03 49 That is on 0xB05A3, also in Perl__invlist_intersection_maybe_complement_2nd: b0598: 48 29 f8sub%rdi,%rax b059b: 48 89 c3mov%rax,%rbx b059e: 74 89 je
[Touch-packages] [Bug 2035339] Re: libperl5.30 crash (segfault) at Perl__invlist_intersection_maybe_complement_2nd during nginx reload
Forgot to mention the versions: - libperl5.30:amd64 5.30.0-9ubuntu0.4 - nginx-common 1.18.0-0ubuntu1.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/2035339 Title: libperl5.30 crash (segfault) at Perl__invlist_intersection_maybe_complement_2nd during nginx reload Status in perl package in Ubuntu: New Bug description: On Focal, I got this in my kern.log: nginx[533]: segfault at 739 ip 7fadc806d5d9 sp 7ffc04f5cd50 error 4 in libperl.so.5.30.0[7fadc8005000+166000] Code: 00 0f b6 40 30 49 c1 ed 03 49 29 c5 0f 84 17 01 00 00 48 8b 76 10 48 8b 52 10 4c 8d 3c fe 4c 8d 0c c2 84 c9 0f 84 c7 02 00 00 <49> 83 39 00 0f 85 ad 03 00 00 49 83 c1 08 49 83 ed 01 49 8d 74 1d Looking at IP ( 0x7fadc806d5d9 - 0x7fadc8005000 ) it appeared to point at 0x685D9 in libperl.so.5.30.0. # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 685D9 Perl_vload_module op.c:7752 But when looking at the code, it looks like it's at 0x685D9 + 0x48000 = 0xB05D9: # addr2line -Cfe /usr/lib/x86_64-linux-gnu/libperl.so.5.30 B05D9 Perl__invlist_intersection_maybe_complement_2nd regcomp.c:9841 This makes more sense: # objdump -d /usr/lib/x86_64-linux-gnu/libperl.so.5.30 ... 000b0500 : ... b05cd: 4c 8d 0c c2 lea(%rdx,%rax,8),%r9 b05d1: 84 c9 test %cl,%cl b05d3: 0f 84 c7 02 00 00 je b08a0 b05d9: 49 83 39 00 cmpq $0x0,(%r9) <-- here b05dd: 0f 85 ad 03 00 00 jneb0990 b05e3: 49 83 c1 08 add$0x8,%r9 b05e7: 49 83 ed 01 sub$0x1,%r13 There's a similar segfault: nginx[356456]: segfault at 10 ip 7f4f576785a3 sp 7ffd0be49220 error 4 in libperl.so.5.30.0[7f4f5761+166000] Code: 48 89 43 10 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 40 00 0f b6 7f 30 48 c1 e8 03 48 29 f8 48 89 c3 74 89 48 8b 02 <4c> 8b 68 10 4d 85 ed 0f 84 28 01 00 00 0f b6 40 30 49 c1 ed 03 49 That is on 0xB05A3, also in Perl__invlist_intersection_maybe_complement_2nd: b0598: 48 29 f8sub%rdi,%rax b059b: 48 89 c3mov%rax,%rbx b059e: 74 89 je b0529 b05a0: 48 8b 02mov(%rdx),%rax b05a3: 4c 8b 68 10 mov0x10(%rax),%r13 <-- here b05a7: 4d 85 edtest %r13,%r13 b05aa: 0f 84 28 01 00 00 je b06d8 On GitHub I found a bug filed for perl 5.30 and this function: https://github.com/Perl/perl5/issues/17154 That issue is fixed in perl 5.32.0 and beyond (across multiple commits). Apparently the bug triggers every now and then, but was not common enough to be noticed. And looking at the timestamps, it is always during an nginx reload. Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2035339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
Hi Julian,
> [There] isn't much we can do otherwise, this highly depends on network
specifics like latency and mtus and is never reliably reproducible.
So, with my bogus python PoC server I mentioned in the comments, it is
quite easily reproducible.
If I can assist you in getting it up and running, do let me know.
Cheers,
Walter
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
Confirmed
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029,http,1w
apt-get 154026 root6r FIFO 0,13 0t0 4012448 pipe 154030,http,1w
apt-get 154026 root7r FIFO 0,13 0t0 4015192 pipe 154031,http,1w
apt-get 154026 root8w FIFO 0,13 0t0 4015177 pipe 154029,http,0r
apt-get 154026 root9r FIFO 0,13 0t0 4015233 pipe 154033,gpgv,1w
apt-get 154026 root 10w FIFO 0,13 0t0 4012449 pipe 154030,http,0r
apt-get 154026 root 12w FIFO 0,13 0t0 4015193 pipe 154031,http,0r
apt-get 154026 root 14w FIFO 0,13 0t0 4015234 pipe 154033,gpgv,0r
http 154029 _apt0r FIFO 0,13 0t0 4015177 pipe
154026,apt-get,8w
http 154029 _apt1w FIFO 0,13 0t0 4015176 pipe
154026,apt-get,5r
http 154030 _apt0r FIFO 0,13 0t0 4012449 pipe
154026,apt-get,10w
http 154030 _apt1w FIFO 0,13 0t0 4012448 pipe
154026,apt-get,6r
http 154031 _apt0r FIFO 0,13 0t0 4015193 pipe
154026,apt-get,12w
http 154031 _apt1w FIFO 0,13 0t0 4015192 pipe
154026,apt-get,7r
gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe
154026,apt-get,14w
gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe
154026,apt-get,9r
```
So:
- apt-get is waiting for any data written by any of its four children (at fd
5/6/7/9)
- http and gpgv are waiting for any data written by their parent (at their
respective fd 0)
Parent backtrace:
```
#0 0x7f420116a74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f420153fb5d in pkgAcquire::Run(int) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int)
()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#4 0x7f42016d127b in DoUpdate (CmdL=...)
at ./apt-private/private-update.cc:73
#5 0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch
const*, bool) (
[Touch-packages] [Bug 2017035] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
This is not a linux-firmware bug, not an initramfs bug, but a problem caused by unattended-upgrades. ** Package changed: initramfs-tools (Ubuntu) => unattended-upgrades (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/2017035 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: Apparently the post-install needs tree(1) which I do not have installed. I wasn't doing anything at the time. Not sure who invoked linux- firmware post-install. I guess the unattended-upgrades. Walter ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 4343 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Apr 19 22:22:52 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=6f038ef7-c49d-4134-a659-602103fcba2d InstallationDate: Installed on 2017-08-22 (2066 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-02 (321 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:sku075B: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017035] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
I don't even know what unattended-upgrades is doing here. Probably got reinstalled by do-release-upgrade :-/ This unattended upgrading causes too many kernels to be installed, filling up the /boot. And then you get tickets like this: "I didn't perform any action to get this crash." https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977647 I guess the bug should be moved to the unattended-upgrades package. Don't do auto-upgrades if there is less than 200MB of space in /boot or a slightly larger amount in /. -- 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/2017035 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in unattended-upgrades package in Ubuntu: New Bug description: Apparently the post-install needs tree(1) which I do not have installed. I wasn't doing anything at the time. Not sure who invoked linux- firmware post-install. I guess the unattended-upgrades. Walter ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 4343 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Apr 19 22:22:52 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=6f038ef7-c49d-4134-a659-602103fcba2d InstallationDate: Installed on 2017-08-22 (2066 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-02 (321 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:sku075B: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2017035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017035] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
See: https://launchpadlibrarian.net/662036095/AlsaInfo.txt There is the tree(1) error which is the one I saw. So, that's a bug in the information collection then I guess. ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665301/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665302/+files/CurrentDmesg.txt ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665304/+files/Dmesg.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665308/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665309/+files/Lspci.txt ** Attachment removed: "acpidump.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665322/+files/acpidump.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665321/+files/WifiSyslog.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665320/+files/UdevDb.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665319/+files/RfKill.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665318/+files/ProcModules.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665317/+files/ProcInterrupts.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665316/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665315/+files/ProcCpuinfo.txt ** Attachment removed: "PaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665314/+files/PaInfo.txt ** Attachment removed: "Lsusb-v.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665313/+files/Lsusb-v.txt ** Attachment removed: "Lsusb-t.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665312/+files/Lsusb-t.txt ** Attachment removed: "Lsusb.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665311/+files/Lsusb.txt ** Attachment removed: "Lspci-vt.txt" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+attachment/5665310/+files/Lspci-vt.txt -- 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/2017035 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Apparently the post-install needs tree(1) which I do not have installed. I wasn't doing anything at the time. Not sure who invoked linux- firmware post-install. I guess the unattended-upgrades. Walter ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 4343 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Apr 19 22:22:52 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=6f038ef7-c49d-4134-a659-602103fcba2d InstallationDate: Installed on 2017-08-22 (2066 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1
[Touch-packages] [Bug 2017035] Re: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned erro
Oh. But https://launchpadlibrarian.net/662036101/DpkgTerminalLog.txt says it's the disk space. This auto-bug report based on the unattended-upgrades has now wasted both your and my time :( See also: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1992246 https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1977647 I cannot see what I'm reporting. Apport is 90% opaque. First after submitting do I get some clues into what it is reporting. And apparently it's reporting something other than I was looking at in the apport-ui, which was tree(1) not being found. Annoying... and not satisfactorily explained. -- 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/2017035 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Apparently the post-install needs tree(1) which I do not have installed. I wasn't doing anything at the time. Not sure who invoked linux- firmware post-install. I guess the unattended-upgrades. Walter ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 4343 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Apr 19 22:22:52 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=6f038ef7-c49d-4134-a659-602103fcba2d InstallationDate: Installed on 2017-08-22 (2066 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-02 (321 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:sku075B: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017035/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2017035] [NEW] package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned er
Public bug reported: Apparently the post-install needs tree(1) which I do not have installed. I wasn't doing anything at the time. Not sure who invoked linux-firmware post-install. I guess the unattended-upgrades. Walter ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 4343 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Apr 19 22:22:52 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=6f038ef7-c49d-4134-a659-602103fcba2d InstallationDate: Installed on 2017-08-22 (2066 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2022-06-02 (321 days ago) dmi.bios.date: 07/13/2020 dmi.bios.release: 2.14 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.14.2 dmi.board.name: 0PF86Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.14.2:bd07/13/2020:br2.14:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0PF86Y:rvrA00:cvnDellInc.:ct9:cvr:sku075B: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.product.sku: 075B dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- 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/2017035 Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Apparently the post-install needs tree(1) which I do not have installed. I wasn't doing anything at the time. Not sure who invoked linux- firmware post-install. I guess the unattended-upgrades. Walter ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu3.12 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.4 AptOrdering: linux-firmware:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: walter 4343 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Apr 19 22:22:52 2023 Dependencies: firmware-sof-signed 2.0-1ubuntu4.1 ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 HibernationDevice: RESUME=UUID=6f038ef7-c49d-4134-a659-602103fcba2d InstallationDate: Installed on 2017-08-22 (2066 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. XPS 13 9360 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-60-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.6, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-firmware 20220329.git681281e4-0ubuntu3.12 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
n main (argc=2, argv=0x7ffc0e14aa38)
at ./cmdline/apt-get.cc:447
```
Child backtrace:
```
#0 0x7f58b1c9b74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f58b237cb43 in WaitFd(int, bool, unsigned long) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x5643e37bc7b3 in BaseHttpMethod::Loop (
this=0x7ffdeaed56c0) at ./methods/basehttp.cc:611
#3 main (argv=) at ./methods/http.cc:1052
```
Where this is:
```
(gdb) print *this
$1 = { = { = { = {}, = {
methodNames = std::vector of length 2, capacity 2 = {
"http", "http::XX.nl"}}, Binary = "http",
SeccompFlags = 6},
authconfs = std::vector of length 1, capacity 1 = {
std::unique_ptr = {get() = 0x5643e5343100}}},
Server = std::unique_ptr = {
get() = 0x5643e534fba0}, NextURI = "",
AllowRedirect = true, Debug = false, PipelineDepth = 10,
static FailFile = {static npos = 18446744073709551615,
_M_dataplus = {> = {<__gnu_cxx::new_allocator>
= {}, },
_M_p = 0x5643e534d650
"/var/lib/apt/lists/partial/apt.osso.nl_ubuntu-security_dists_jammy-security_InRelease"},
_M_string_length = 85, {
_M_local_buf = "\226", '\000' ,
_M_allocated_capacity = 150}}, static FailFd = -1,
static FailTime = 1674071760}
```
Relevant code in parent:
```
pkgAcquire::RunResult pkgAcquire::Run(int PulseInterval)
{
...
// Run till all things have been acquired
struct timeval tv =
SteadyDurationToTimeVal(std::chrono::microseconds(PulseInterval));
while (ToFetch > 0)
...
int Res;
do
{
Res = select(Highest+1,,,0,);
}
while (Res < 0 && errno == EINTR);
```
Relevant code in child:
```
int BaseHttpMethod::Loop()
{
signal(SIGTERM,SigTerm);
signal(SIGINT,SigTerm);
Server = 0;
int FailCounter = 0;
while (1)
{
// We have no commands, wait for some to arrive
if (Queue == 0)
{
if (WaitFd(STDIN_FILENO) == false)
return 0;
```
Versions:
```
Ubuntu 22.04.1 LTS (Jammy Jellyfish)
apt 2.4.8
```
Preliminiary conclusion/notes:
- I don't know why it stalls, but it does. And this was not a single
incident. All the stalling apt processes had stopped at a different
time/day.
- Apparently there is a situation possible where there are no commands
queued from the parent, and the parent isn't planning on sending any
either.
- Our apt-get is invoked by a cron job which calls either `update-
notifier-common` or `apt-get update`:
https://github.com/ossobv/zabbix-agent-
osso/blob/c61aee6087c0d03e66d03013c61acd9f65d0eaab/scripts/dpkg.updates#L14-L31
-- on the machines where apt-get was hanging, there was no `update-
notifier-common`.
- I don't know if this is 2.4.x related (on Focal we have apt 2.0.x),
but it sure looks like it. I did check a few other Focal machines that
lacked `update-notifier-common`, but they were not having a stalled
apt-get (although _not_ seeing a hung process proves nothing)
Let me know if there's anything I can get you. Should this be filed
elsewhere? (Debian Salsa?)
Cheers,
Walter Doekes
OSSO B.V.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
rn 0; ``` Versions: ``` Ubuntu 22.04.1 LTS (Jammy Jellyfish) apt 2.4.8 ``` Preliminiary conclusion/notes: - I don't know why it stalls, but it does. And this was not a single incident. All the stalling apt processes had stopped at a different time/day. - Apparently there is a situation possible where there are no commands queued from the parent, and the parent isn't planning on sending any either. - Our apt-get is invoked by a cron job which calls either `update- notifier-common` or `apt-get update`: https://github.com/ossobv/zabbix-agent- osso/blob/c61aee6087c0d03e66d03013c61acd9f65d0eaab/scripts/dpkg.updates#L14-L31 -- on the machines where apt-get was hanging, there was no `update- notifier-common`. - I don't know if this is 2.4.x related (on Focal we have apt 2.0.x), but it sure looks like it. I did check a few other Focal machines that lacked `update-notifier-common`, but they were not having a stalled apt-get (although _not_ seeing a hung process proves nothing) Let me know if there's anything I can get you. Should this be filed elsewhere? (Debian Salsa?) Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
in 1022, options [nop,nop,TS val 558653631 ecr
4041174334], length 0
12:31:58.083199 eth0 In IP 217.21.198.165.3851 > 217.21.199.56.42838: Flags
[.], ack 350, win 507, options [nop,nop,TS val 4041174335 ecr 558653631],
length 0
Where that last request was:
GET /ubuntu/dists/jammy-updates/InRelease HTTP/1.1
Host: junk.devs.nu:3851
Cache-Control: max-age=0
Accept: text/*
User-Agent: Debian APT-HTTP/1.3 (2.4.9) non-interactive
And the last response was:
HTTP/1.1 200 OK
date: Fri, 17 Feb 2023 15:11:49 GMT
content-type: octet/stream
content-length: 118747
last-modified: Fri, 17 Feb 2023 13:29:00 GMT
x-original-source:
http://de.archive.ubuntu.com/ubuntu/dists/jammy-updates/InRelease
This response was sent in the FIN packet. So no actual content would be
delivered.
The apt-get process which got the broken server has this backtrace:
(gdb) bt
#0 0x7efc90d3774d in __GI___select (nfds=1, readfds=0x7ffe64790920,
writefds=0x0, exceptfds=0x0, timeout=0x0) at
../sysdeps/unix/sysv/linux/select.c:69
#1 0x7efc91418b43 in WaitFd(int, bool, unsigned long) () from
/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x555a612d47b3 in BaseHttpMethod::Loop (this=0x7ffe64790bf0) at
./methods/basehttp.cc:611
#3 main (argv=) at ./methods/http.cc:1052
The process which got the good server (zabbix) has a similar backtrace:
(gdb) bt
#0 0x7f8e345e674d in __GI___select (nfds=1, readfds=0x7ffc6f6b9990,
writefds=0x0, exceptfds=0x0, timeout=0x0) at
../sysdeps/unix/sysv/linux/select.c:69
#1 0x7f8e34cc7b43 in WaitFd(int, bool, unsigned long) () from
/lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x5614260967b3 in BaseHttpMethod::Loop (this=0x7ffc6f6b9c60) at
./methods/basehttp.cc:611
#3 main (argv=) at ./methods/http.cc:1052
=
server.py
=
http://junk.devs.nu/2023/lp2003851/server.py
http://junk.devs.nu/2023/lp2003851/2023-02-21-13-31.pcap
=
I'll go take a look at why apt-cacher-ng misbehaves.
[~juliank]: Maybe this is sufficient info for you to work with? Even
though our server is at fault, we still don't want an infinitely hanging
apt.
NOTE: Maybe this isn't an apt 2.4.x thing, but something that started
happening for Jammy-served apt-cacher-ng responses and therefore only
visible on Jammy? In that case this isn't a newly introduced problem in
apt.
Cheers,
Walter Doekes
OSSO B.V.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
New
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, NULL).
The http sockets in the children were at fd=3.
Parent lsof:
```
# lsof -p 154026 +E
...
apt-get 154026 root4uW REG8,10 262281
/var/lib/apt/lists/lock
apt-get 154026 root5r FIFO 0,13 0t0 4015176 pipe 154029
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#6 0x7f420169fa97 in DispatchCommandLine (CmdL=...,
Cmds=std::vector of length 27, capacity 32 = {...})
at ./apt-private/private-cmndline.cc:588
#7 0x561fc06bafbd in main (argc=2, argv=0x7ffc0e14aa38)
at ./cmdline/apt-get.cc:447
```
Child backtrace:
```
#0 0x7f58b1c9b74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f58b237cb43 in WaitFd(int, bool, unsigned long) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x5643e37bc7b3 in BaseHttpMethod::Loop (
this=0x7ffdeaed56c0) at ./methods/basehttp.cc:611
#3 main (argv=) at ./methods/http.cc:1052
```
Where this is:
```
(gdb) print *this
$1 = { = { = { = {}, = {
methodNames = std::vector of length 2, capacity 2 = {
"http", "http::XX.nl"}}, Binary = "http",
SeccompFlags = 6},
authconfs = std::vector of length 1, capacity 1 = {
std::unique_ptr = {get() = 0x5643e5343100}}},
Server = std::unique_ptr = {
get() = 0x5643e534fba0}, NextURI = "",
AllowRedirect = true, Debug = false, PipelineDepth = 10,
static FailFile = {static npos = 18446744073709551615,
_M_dataplus = {> = {<__gnu_cxx::new_allocator>
= {}, },
_M_p = 0x5643e534d650
"/var/lib/apt/lists/partial/apt.osso.nl_ubuntu-security_dists_jammy-security_InRelease"},
_M_string_length = 85, {
_M_local_buf = "\226", '\000' ,
_M_allocated_capacity = 150}}, static FailFd = -1,
static FailTime = 1674071760}
```
Relevant code in parent:
```
pkgAcquire::RunResult pkgAcquire::Run(int PulseInterval)
{
...
// Run till all things have been acquired
struct timeval tv =
SteadyDurationToTimeVal(std::chrono::microseconds(PulseInterval));
while (ToFetch > 0)
...
int Res;
do
{
Res = select(Highest+1,,,0,);
}
while (Res < 0 && errno == EINTR);
```
Relevant code in child:
```
int BaseHttpMethod::Loop()
{
signal(SIGTERM,SigTerm);
signal(SIGINT,SigTerm);
Server = 0;
int FailCounter = 0;
while (1)
{
// We have no commands, wait for some to arrive
if (Queue == 0)
{
if (WaitFd(STDIN_FILENO) == false)
return 0;
```
Versions:
```
Ubuntu 22.04.1 LTS (Jammy Jellyfish)
apt 2.4.8
```
Preliminiary conclusion/notes:
- I don't know why it stalls, but it does. And this was not a single
incident. All the stalling apt processes had stopped at a different
time/day.
- Apparently there is a situation possible where there are no commands
queued from the parent, and the parent isn't planning on sending any
either.
- Our apt-get is invoked by a cron job which calls either `update-
notifier-common` or `apt-get update`:
https://github.com/ossobv/zabbix-agent-
osso/blob/c61aee6087c0d03e66d03013c61acd9f65d0eaab/scripts/dpkg.updates#L14-L31
-- on the machines where apt-get was hanging, there was no `update-
notifier-common`.
- I don't know if this is 2.4.x related (on Focal we have apt 2.0.x),
but it sure looks like it. I did check a few other Focal machines that
lacked `update-notifier-common`, but they were not having a stalled
apt-get (although _not_ seeing a hung process proves nothing)
Let me know if there's anything I can get you. Should this be filed
elsewhere? (Debian Salsa?)
Cheers,
Walter Doekes
OSSO B.V.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing
Haha, yea, long time debian/ubuntu user here too. The only way I found out and know was because my script that parses apt-policy failed [1]. Pure luck [2]. Also seconding the do-translations-later. I don't know if there are statistics available for this, but based on anecdotal evidence alone, I say that many people run their OS in English anyway. And that the average debian/ubuntu user is used to more English than average users of proprietary operating systems.. [1] https://github.com/ossobv/vcutil/commit/9a34b973491f7165790f8c239f1b1c39bf4d1687 [2] Yay for defensive coding. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1988819 Title: When apt keeps back packages due to phased updates, it should say nothing Status in apt package in Ubuntu: Triaged Bug description: After phased updates have been introduced, it may happen that apt upgrade shows packages as upgradable but ends up not upgrading them. In this case the packages are indicated as being "kept back". Unfortunately, the feedback provided about this to the user is not very informative. The user sees the packages being kept back and thinks something is going wrong on the system. When packages are kept back because of phased updates, apt should say so e.g., it should say that the upgrade is delayed. Incidentally note that aptitude does not respect phased updates. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apt 2.4.7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Tue Sep 6 10:05:14 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-16 (933 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: apt UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003851] Re: occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
,apt-get,7r
gpgv 154033 _apt0r FIFO 0,13 0t0 4015234 pipe
154026,apt-get,14w
gpgv 154033 _apt1w FIFO 0,13 0t0 4015233 pipe
154026,apt-get,9r
```
So:
- apt-get is waiting for any data written by any of its four children (at fd
5/6/7/9)
- http and gpgv are waiting for any data written by their parent (at their
respective fd 0)
Parent backtrace:
```
#0 0x7f420116a74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f420153fb5d in pkgAcquire::Run(int) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x7f420161d535 in AcquireUpdate(pkgAcquire&, int, bool, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#3 0x7f420161d986 in ListUpdate(pkgAcquireStatus&, pkgSourceList&, int)
()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#4 0x7f42016d127b in DoUpdate (CmdL=...)
at ./apt-private/private-update.cc:73
#5 0x7f420156d73f in CommandLine::DispatchArg(CommandLine::Dispatch
const*, bool) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#6 0x7f420169fa97 in DispatchCommandLine (CmdL=...,
Cmds=std::vector of length 27, capacity 32 = {...})
at ./apt-private/private-cmndline.cc:588
#7 0x561fc06bafbd in main (argc=2, argv=0x7ffc0e14aa38)
at ./cmdline/apt-get.cc:447
```
Child backtrace:
```
#0 0x7f58b1c9b74d in select ()
from /lib/x86_64-linux-gnu/libc.so.6
#1 0x7f58b237cb43 in WaitFd(int, bool, unsigned long) ()
from /lib/x86_64-linux-gnu/libapt-pkg.so.6.0
#2 0x5643e37bc7b3 in BaseHttpMethod::Loop (
this=0x7ffdeaed56c0) at ./methods/basehttp.cc:611
#3 main (argv=) at ./methods/http.cc:1052
```
Where this is:
```
(gdb) print *this
$1 = { = { = { = {}, = {
methodNames = std::vector of length 2, capacity 2 = {
"http", "http::XX.nl"}}, Binary = "http",
SeccompFlags = 6},
authconfs = std::vector of length 1, capacity 1 = {
std::unique_ptr = {get() = 0x5643e5343100}}},
Server = std::unique_ptr = {
get() = 0x5643e534fba0}, NextURI = "",
AllowRedirect = true, Debug = false, PipelineDepth = 10,
static FailFile = {static npos = 18446744073709551615,
_M_dataplus = {> = {<__gnu_cxx::new_allocator>
= {}, },
_M_p = 0x5643e534d650
"/var/lib/apt/lists/partial/apt.osso.nl_ubuntu-security_dists_jammy-security_InRelease"},
_M_string_length = 85, {
_M_local_buf = "\226", '\000' ,
_M_allocated_capacity = 150}}, static FailFd = -1,
static FailTime = 1674071760}
```
Relevant code in parent:
```
pkgAcquire::RunResult pkgAcquire::Run(int PulseInterval)
{
...
// Run till all things have been acquired
struct timeval tv =
SteadyDurationToTimeVal(std::chrono::microseconds(PulseInterval));
while (ToFetch > 0)
...
int Res;
do
{
Res = select(Highest+1,,,0,);
}
while (Res < 0 && errno == EINTR);
```
Relevant code in child:
```
int BaseHttpMethod::Loop()
{
signal(SIGTERM,SigTerm);
signal(SIGINT,SigTerm);
Server = 0;
int FailCounter = 0;
while (1)
{
// We have no commands, wait for some to arrive
if (Queue == 0)
{
if (WaitFd(STDIN_FILENO) == false)
return 0;
```
Versions:
```
Ubuntu 22.04.1 LTS (Jammy Jellyfish)
apt 2.4.8
```
Preliminiary conclusion/notes:
- I don't know why it stalls, but it does. And this was not a single
incident. All the stalling apt processes had stopped at a different
time/day.
- Apparently there is a situation possible where there are no commands
queued from the parent, and the parent isn't planning on sending any
either.
- Our apt-get is invoked by a cron job which calls either `update-
notifier-common` or `apt-get update`:
https://github.com/ossobv/zabbix-agent-
osso/blob/c61aee6087c0d03e66d03013c61acd9f65d0eaab/scripts/dpkg.updates#L14-L31
-- on the machines where apt-get was hanging, there was no `update-
notifier-common`.
- I don't know if this is 2.4.x related (on Focal we have apt 2.0.x),
but it sure looks like it. I did check a few other Focal machines that
lacked `update-notifier-common`, but they were not having a stalled
apt-get (although _not_ seeing a hung process proves nothing)
Let me know if there's anything I can get you. Should this be filed
elsewhere? (Debian Salsa?)
Cheers,
Walter Doekes
OSSO B.V.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2003851/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2003851] [NEW] occasional hanging 'apt-get update' from daily cronjob since Jammy 22.04
"http", "http::XX.nl"}}, Binary = "http",
SeccompFlags = 6},
authconfs = std::vector of length 1, capacity 1 = {
std::unique_ptr = {get() = 0x5643e5343100}}},
Server = std::unique_ptr = {
get() = 0x5643e534fba0}, NextURI = "",
AllowRedirect = true, Debug = false, PipelineDepth = 10,
static FailFile = {static npos = 18446744073709551615,
_M_dataplus = {> = {<__gnu_cxx::new_allocator> =
{}, },
_M_p = 0x5643e534d650
"/var/lib/apt/lists/partial/apt.osso.nl_ubuntu-security_dists_jammy-security_InRelease"},
_M_string_length = 85, {
_M_local_buf = "\226", '\000' ,
_M_allocated_capacity = 150}}, static FailFd = -1,
static FailTime = 1674071760}
```
Relevant code in parent:
```
pkgAcquire::RunResult pkgAcquire::Run(int PulseInterval)
{
...
// Run till all things have been acquired
struct timeval tv =
SteadyDurationToTimeVal(std::chrono::microseconds(PulseInterval));
while (ToFetch > 0)
...
int Res;
do
{
Res = select(Highest+1,,,0,);
}
while (Res < 0 && errno == EINTR);
```
Relevant code in child:
```
int BaseHttpMethod::Loop()
{
signal(SIGTERM,SigTerm);
signal(SIGINT,SigTerm);
Server = 0;
int FailCounter = 0;
while (1)
{
// We have no commands, wait for some to arrive
if (Queue == 0)
{
if (WaitFd(STDIN_FILENO) == false)
return 0;
```
Versions:
```
Ubuntu 22.04.1 LTS (Jammy Jellyfish)
apt 2.4.8
```
Preliminiary conclusion/notes:
- I don't know why it stalls, but it does. And this was not a single
incident. All the stalling apt processes had stopped at a different
time/day.
- Apparently there is a situation possible where there are no commands
queued from the parent, and the parent isn't planning on sending any
either.
- Our apt-get is invoked by a cron job which calls either `update-
notifier-common` or `apt-get update`: https://github.com/ossobv/zabbix-
agent-
osso/blob/c61aee6087c0d03e66d03013c61acd9f65d0eaab/scripts/dpkg.updates#L14-L31
-- on the machines where apt-get was hanging, there was no `update-
notifier-common`.
- I don't know if this is 2.4.x related (on Focal we have apt 2.0.x),
but it sure looks like it. I did check a few other Focal machines that
lacked `update-notifier-common`, but they were not having a stalled apt-
get (although _not_ seeing a hung process proves nothing)
Let me know if there's anything I can get you. Should this be filed elsewhere?
(Debian Salsa?)
Cheers,
Walter Doekes
OSSO B.V.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2003851
Title:
occasional hanging 'apt-get update' from daily cronjob since Jammy
22.04
Status in apt package in Ubuntu:
New
Bug description:
Hi!
Yesterday I spotted several machines of ours where a period `apt-get
update` was stalled. The `http` children were hanging in `WaitFd`
(waiting for parent instructions/queue). The parent was looping in
`AcquireUpdate` every 500ms.
We have a cronjob that runs every few hours which calls `apt-get update` and
does some post-processing. We noticed that several of them had stalled at some
point in time. Killing the parent (apt-get) got it unstuck, removing the locks.
Example:
```
# apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock. It is held by process 154026
(apt-get)
N: Be aware that removing the lock file is not a solution and may break your
system.
E: Unable to lock directory /var/lib/apt/lists/
```
Task listing:
```
root 153929 \_ /usr/sbin/CRON -f -P
root 153942 \_ /bin/sh -c [ -x /etc/zabbix/scripts/dpkg.updates ]
&& /etc/zabbix/scripts/dpkg.updates --cron
root 153943 \_ /bin/sh /etc/zabbix/scripts/dpkg.updates --cron
root 154026 \_ apt-get update
_apt 154029 \_ /usr/lib/apt/methods/http
_apt 154030 \_ /usr/lib/apt/methods/http
_apt 154031 \_ /usr/lib/apt/methods/http
_apt 154033 \_ /usr/lib/apt/methods/gpgv
```
Open (TCP) sockets. All have 1 item in the Recv-Q (probably a FIN or RST?):
```
# netstat -apn | grep -E '154026|154029|154030|154031|154033'
tcp 1 0 10.x.x.x:60868 217.x.x.x:80 CLOSE_WAIT 154030/http
tcp 1 0 10.x.x.x:40756 178.x.x.x:80 CLOSE_WAIT 154029/http
tcp 1 0 10.x.x.x:56818 185.x.x.x:80 CLOSE_WAIT 154031/http
```
All children (including gpgv) were waiting using pselect6(1, [0], NULL, NULL,
NULL, NULL).
The parent (apt-get) was waiting using pselect6(10, [5 6 7 9], [],
NULL, {tv_sec=0, tv_nsec=5}, N
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
Looking into this again, I found that I had the following line in /etc/environment: FREETYPE_PROPERTIES="truetype:interpreter-version=35 cff:no-stem- darkening=1 autofitter:warping=1" I can't remember why I set this, probably some hinting issues in an old Xubuntu version. Removing it causes v40 of the interpreter to be used, fixing the broken letters. The font is obviously broken when used with v35, but few people are going to notice unless they're as clumsy as me, so you may want to close the ticket. I also found out that `ftview` from the freetype2-demos package is great for investigating these issues, as it lets you cycle through all the relevant settings. Thanks for your help and apologies for not realising that I had a non- standard setup. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fontforge package in Ubuntu: New Status in fonts-dejavu package in Ubuntu: Confirmed Status in gnome-font-viewer package in Ubuntu: Confirmed Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra 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 fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontforge/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
$ gsettings list-recursively org.gnome.desktop.interface | grep font org.gnome.desktop.interface document-font-name 'Cantarell 11' org.gnome.desktop.interface font-antialiasing 'grayscale' org.gnome.desktop.interface font-hinting 'slight' org.gnome.desktop.interface font-name 'Noto Sans 9' org.gnome.desktop.interface font-rgba-order 'rgb' org.gnome.desktop.interface monospace-font-name 'Monospace 10' $ I'm using the integrated graphics processor on an Intel i3-8100 CPU with Xubuntu / xfce4. While I agree that it may not be a problem with the actual font, I clicked through many fonts available in gnome-font-viewer and only saw problems with these: DejaVu Serif, Condensed Bold Italic DejaVu Serif, Bold Italic DejaVu Serif, Italic DejaVu Serif, Condensed Italic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: Invalid Status in gnome-font-viewer package in Ubuntu: Incomplete Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra 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 fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] Re: DejaVu Serif Italic capital letters and digits broken
Added screenshot from Libreoffice, showing it affects multiple applications and font sizes ** Attachment added: "Screenshot from Libreoffice" https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+attachment/5622811/+files/Screenshot_2022-10-10_20-42-54.png ** Description changed: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic - looks quite broken. At least the letters EFHIKLMNT and the digits 1 and - 4 are affected + looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 + are affected Please see the attached screenshot. This was obtained from `gnome-font- viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. - - $ dpkg -l gnome-font-viewer fonts-dejavu-extra + $ dpkg -l gnome-font-viewer fonts-dejavu-extra 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 fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: New Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra 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 fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1992369] [NEW] DejaVu Serif Italic capital letters and digits broken
Public bug reported: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHIKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome-font- viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra 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 fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME ** Affects: fonts-dejavu (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_2022-10-10_20-29-45.png" https://bugs.launchpad.net/bugs/1992369/+attachment/5622810/+files/Screenshot_2022-10-10_20-29-45.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-dejavu in Ubuntu. https://bugs.launchpad.net/bugs/1992369 Title: DejaVu Serif Italic capital letters and digits broken Status in fonts-dejavu package in Ubuntu: New Bug description: After updating from Focal to Jammy, I noticed that DejaVu Serif Italic looks quite broken. At least the letters EFHIKLMNT and the digits 1 and 4 are affected Please see the attached screenshot. This was obtained from `gnome- font-viewer /usr/share/fonts/truetype/dejavu/DejaVuSerif-Italic.ttf` As the font is the default for me in Firefox, it's quite noticeable. $ dpkg -l gnome-font-viewer fonts-dejavu-extra 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 fonts-dejavu-extra 2.37-2build1 all Vera font family derivate with> ii gnome-font-viewer 41.0-2 amd64font viewer for GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-dejavu/+bug/1992369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977652] Re: systemd loops trying to start systemd-ask-password-plymouth
** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1977652 Title: systemd loops trying to start systemd-ask-password-plymouth Status in systemd package in Ubuntu: New Bug description: Short story: - after boot - when a systemd service wants a password - systemd-ask-password is invoked - systemd-ask-password-plymouth.path is reached - systemd-ask-password-plymouth.service is started Except: - the conditions for the latter are (apparently) not met End result: - 40.000x "Condition check resulted in Forward Password Requests to Plymouth being skipped." - 1.5 minutes of 100% cpu usage AFFECTED VERSION systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04 HOW TO REPRODUCE If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and reboot. OpenVPN (calling systemd-ask-password) will trigger the condition. This causes high CPU usage for 1.5 minutes. It looks like /run/plymouth/pid exists (for the .path file) at first, when that is invoked, but then the resultant target (the .service file) checks again, and finds that it is gone. Manually reproducing: # ls /run/systemd/ask-password ask.5hW6rb sck.79cfe1203518610 # mkdir /run/plymouth/pid # systemctl start systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path # systemctl show --value --property=MainPID systemd-ask-password-plymouth.service 24777 # rmdir /run/plymouth/pid ; kill 24777 Result: systemd going into a loop. Stop the loop with: # systemctl stop systemd-ask-password-plymouth.path ANALYSIS It looks like this: https://github.com/systemd/systemd/issues/21025 which is fixed by: https://github.com/systemd/systemd/pull/21030 Alternative bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1919538 Systemd's own analysis of the situation: # systemd-analyze critical-chain systemd-ask-password-plymouth.service ... systemd-ask-password-plymouth.service @1min 35.823s └─systemd-ask-password-plymouth.path @593ms └─plymouth-start.service @571ms +21ms └─systemd-udevd.service @450ms +119ms └─systemd-tmpfiles-setup-dev.service @429ms +18ms └─systemd-sysusers.service @382ms +46ms └─systemd-remount-fs.service @353ms +22ms └─systemd-journald.socket @318ms └─system.slice @264ms └─-.slice @264ms --- WORKAROUNDS --- This works as long as you don't need the plymouth-ask-password: # systemctl disable systemd-ask-password-plymouth.path # systemctl mask systemd-ask-password-plymouth.path Could you get the relevant patches from upstream sorted in Jammy? Thanks! Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977652] Re: systemd loops trying to start systemd-ask-password-plymouth
Funny you should ask. I tempted to ask where you think I got the output from in the first place. But I shall refrain from sarcasm as that won't do any good. This does put me in a bit of a pickle. Because in order for the journalctl output to be more useful than just the 40.000 message I referenced, I should leave it untouched. But I cannot give it to you unsanitized either. I'm attaching the log uniq -c'd, starting just before the issue at hand, so I could inspect it for private details. Observe that the `1501` on the left means 1501x the same message in lines like: 1501 jun 04 15:01:55 myhostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth being skipped. I hope this is convincing enough that I'm not making this up. As for the: > I believe the commit you referenced has been in jammy since 249.9-0ubuntu1. Okay. Well. If I apt-get source systemd, I would assume that I'd get that as a patch file. But grepping for "unit_has_failed_condition_or_assert" in ./debian/patches yields nothing. Grepping for -i "condition": no relevant hits. Are you sure this patch is included? If so, then only parts if it maybe? Regards, Walter ** Attachment added: "journalctl-demonstrating-plymouth-being-skipped-flood.txt" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977652/+attachment/5596096/+files/journalctl-demonstrating-plymouth-being-skipped-flood.txt -- 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/1977652 Title: systemd loops trying to start systemd-ask-password-plymouth Status in systemd package in Ubuntu: Incomplete Bug description: Short story: - after boot - when a systemd service wants a password - systemd-ask-password is invoked - systemd-ask-password-plymouth.path is reached - systemd-ask-password-plymouth.service is started Except: - the conditions for the latter are (apparently) not met End result: - 40.000x "Condition check resulted in Forward Password Requests to Plymouth being skipped." - 1.5 minutes of 100% cpu usage AFFECTED VERSION systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04 HOW TO REPRODUCE If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and reboot. OpenVPN (calling systemd-ask-password) will trigger the condition. This causes high CPU usage for 1.5 minutes. It looks like /run/plymouth/pid exists (for the .path file) at first, when that is invoked, but then the resultant target (the .service file) checks again, and finds that it is gone. Manually reproducing: # ls /run/systemd/ask-password ask.5hW6rb sck.79cfe1203518610 # mkdir /run/plymouth/pid # systemctl start systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path # systemctl show --value --property=MainPID systemd-ask-password-plymouth.service 24777 # rmdir /run/plymouth/pid ; kill 24777 Result: systemd going into a loop. Stop the loop with: # systemctl stop systemd-ask-password-plymouth.path ANALYSIS It looks like this: https://github.com/systemd/systemd/issues/21025 which is fixed by: https://github.com/systemd/systemd/pull/21030 Alternative bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1919538 Systemd's own analysis of the situation: # systemd-analyze critical-chain systemd-ask-password-plymouth.service ... systemd-ask-password-plymouth.service @1min 35.823s └─systemd-ask-password-plymouth.path @593ms └─plymouth-start.service @571ms +21ms └─systemd-udevd.service @450ms +119ms └─systemd-tmpfiles-setup-dev.service @429ms +18ms └─systemd-sysusers.service @382ms +46ms └─systemd-remount-fs.service @353ms +22ms └─systemd-journald.socket @318ms └─system.slice @264ms └─-.slice @264ms --- WORKAROUNDS --- This works as long as you don't need the plymouth-ask-password: # systemctl disable systemd-ask-password-plymouth.path # systemctl mask systemd-ask-password-plymouth.path Could you get the relevant patches from upstream sorted in Jammy? Thanks! Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1955704] Re: systemd/plymouth preventing reboot/shutdown
Hi [~phm2f1alcw69] is this possibly related to #1977652 ? Depends on: - your version of systemd / ubuntu (I don't see any versions in this report) - whether you also saw items looped in the logs (journald -b -1 | tail) Cheers, Walter -- 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/1955704 Title: systemd/plymouth preventing reboot/shutdown Status in systemd package in Ubuntu: New Bug description: Plymouth seems to be busy with trying to show a "Halt" and also a "Reboot" screen during shutdown, and in trying to do so preventing the actual shutdown procedure to succeed. It even continues to do so after forcing the shutdown/reboot procedure as can be seen in the attached screenshot. Systemd then continues the show with waiting for an obscure kwin process, which ceased to exist long before. Of course, systemctl doesn't work at this stage any more either, so log files are useless. p.s. after giving the two processes systemd & plymouth several minutes to finish what they were claiming to do, I had tp pull the plug to end this farce. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1955704/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977652] [NEW] systemd loops trying to start systemd-ask-password-plymouth
Public bug reported: Short story: - after boot - when a systemd service wants a password - systemd-ask-password is invoked - systemd-ask-password-plymouth.path is reached - systemd-ask-password-plymouth.service is started Except: - the conditions for the latter are (apparently) not met End result: - 40.000x "Condition check resulted in Forward Password Requests to Plymouth being skipped." - 1.5 minutes of 100% cpu usage AFFECTED VERSION systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04 HOW TO REPRODUCE If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and reboot. OpenVPN (calling systemd-ask-password) will trigger the condition. This causes high CPU usage for 1.5 minutes. It looks like /run/plymouth/pid exists (for the .path file) at first, when that is invoked, but then the resultant target (the .service file) checks again, and finds that it is gone. Manually reproducing: # ls /run/systemd/ask-password ask.5hW6rb sck.79cfe1203518610 # mkdir /run/plymouth/pid # systemctl start systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path # systemctl show --value --property=MainPID systemd-ask-password-plymouth.service 24777 # rmdir /run/plymouth/pid ; kill 24777 Result: systemd going into a loop. Stop the loop with: # systemctl stop systemd-ask-password-plymouth.path ANALYSIS It looks like this: https://github.com/systemd/systemd/issues/21025 which is fixed by: https://github.com/systemd/systemd/pull/21030 Alternative bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1919538 Systemd's own analysis of the situation: # systemd-analyze critical-chain systemd-ask-password-plymouth.service ... systemd-ask-password-plymouth.service @1min 35.823s └─systemd-ask-password-plymouth.path @593ms └─plymouth-start.service @571ms +21ms └─systemd-udevd.service @450ms +119ms └─systemd-tmpfiles-setup-dev.service @429ms +18ms └─systemd-sysusers.service @382ms +46ms └─systemd-remount-fs.service @353ms +22ms └─systemd-journald.socket @318ms └─system.slice @264ms └─-.slice @264ms --- WORKAROUNDS --- This works as long as you don't need the plymouth-ask-password: # systemctl disable systemd-ask-password-plymouth.path # systemctl mask systemd-ask-password-plymouth.path Could you get the relevant patches from upstream sorted in Jammy? Thanks! Walter Doekes OSSO B.V. ** 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/1977652 Title: systemd loops trying to start systemd-ask-password-plymouth Status in systemd package in Ubuntu: New Bug description: Short story: - after boot - when a systemd service wants a password - systemd-ask-password is invoked - systemd-ask-password-plymouth.path is reached - systemd-ask-password-plymouth.service is started Except: - the conditions for the latter are (apparently) not met End result: - 40.000x "Condition check resulted in Forward Password Requests to Plymouth being skipped." - 1.5 minutes of 100% cpu usage AFFECTED VERSION systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04 HOW TO REPRODUCE If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and reboot. OpenVPN (calling systemd-ask-password) will trigger the condition. This causes high CPU usage for 1.5 minutes. It looks like /run/plymouth/pid exists (for the .path file) at first, when that is invoked, but then the resultant target (the .service file) checks again, and finds that it is gone. Manually reproducing: # ls /run/systemd/ask-password ask.5hW6rb sck.79cfe1203518610 # mkdir /run/plymouth/pid # systemctl start systemd-ask-password-plymouth.service systemd-ask-password-plymouth.path # systemctl show --value --property=MainPID systemd-ask-password-plymouth.service 24777 # rmdir /run/plymouth/pid ; kill 24777 Result: systemd going into a loop. Stop the loop with: # systemctl stop systemd-ask-password-plymouth.path ANALYSIS It looks like this: https://github.com/systemd/systemd/issues/21025 which is fixed by: https://github.com/systemd/systemd/pull/21030 Alternative bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1919538 Systemd's own analysis of the situation: # systemd-analyze critical-chain systemd-ask-password-plymouth.service ... systemd-ask-password-plymouth.service @1min 35.823s └─systemd-ask-password-plymouth.path @593ms └─plymouth-start.service @571ms +21ms └─systemd-udevd.service @450ms +119ms └─systemd-tmpfiles-setu
[Touch-packages] [Bug 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail
Created PR at Debian: https://salsa.debian.org/debian/gpgme/-/merge_requests/4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1977645 Title: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail Status in gpgme1.0 package in Ubuntu: New Bug description: The python version of the gpgme version contains "unknown" and is therefore not PEP440 order compatible. See this example: # pip3 freeze | grep gpg gpg===1.16.0-unknown # pip3 install pstore ... Successfully installed gpg-1.10.0 Successfully installed pstore-2.0.0 # pip3 freeze | grep gpg gpg==1.10.0 Key takeways from that example: - pstore depends on gpg>=1.10 - 1.16 SHOULD be higher than 1.10 - pip installs 1.10 even though 1.16 exists - the triple-= (gpg===1.16.0-unknown) means that the version exists, but cannot be version compared: https://peps.python.org/pep-0440/#arbitrary-equality Suggested fix: - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with a '+'; that will compare as expected; - fix so "-unknown" isn't appended. Apparently, this is caused by insufficient fixes in 0001-avoid-identifying-as-beta.patch I've attached a FIXED version, which should fix things. Before: $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown. After: $ quilt push Applying patch 0001-avoid-identifying-as-beta-FIXED.patch $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0. Versions: $ lsb_release -a 2>/dev/null| grep Codename Codename: jammy $ apt-cache policy python3-gpg | grep Installed Installed: 1.16.0-1.2ubuntu4 Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1977645] [NEW] python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail
Public bug reported: The python version of the gpgme version contains "unknown" and is therefore not PEP440 order compatible. See this example: # pip3 freeze | grep gpg gpg===1.16.0-unknown # pip3 install pstore ... Successfully installed gpg-1.10.0 Successfully installed pstore-2.0.0 # pip3 freeze | grep gpg gpg==1.10.0 Key takeways from that example: - pstore depends on gpg>=1.10 - 1.16 SHOULD be higher than 1.10 - pip installs 1.10 even though 1.16 exists - the triple-= (gpg===1.16.0-unknown) means that the version exists, but cannot be version compared: https://peps.python.org/pep-0440/#arbitrary- equality Suggested fix: - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with a '+'; that will compare as expected; - fix so "-unknown" isn't appended. Apparently, this is caused by insufficient fixes in 0001-avoid-identifying-as-beta.patch I've attached a FIXED version, which should fix things. Before: $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown. After: $ quilt push Applying patch 0001-avoid-identifying-as-beta-FIXED.patch $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0. Versions: $ lsb_release -a 2>/dev/null| grep Codename Codename: jammy $ apt-cache policy python3-gpg | grep Installed Installed: 1.16.0-1.2ubuntu4 Cheers, Walter Doekes OSSO B.V. ** Affects: gpgme1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "0001-avoid-identifying-as-beta-FIXED.patch" https://bugs.launchpad.net/bugs/1977645/+attachment/5594802/+files/0001-avoid-identifying-as-beta-FIXED.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1977645 Title: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail Status in gpgme1.0 package in Ubuntu: New Bug description: The python version of the gpgme version contains "unknown" and is therefore not PEP440 order compatible. See this example: # pip3 freeze | grep gpg gpg===1.16.0-unknown # pip3 install pstore ... Successfully installed gpg-1.10.0 Successfully installed pstore-2.0.0 # pip3 freeze | grep gpg gpg==1.10.0 Key takeways from that example: - pstore depends on gpg>=1.10 - 1.16 SHOULD be higher than 1.10 - pip installs 1.10 even though 1.16 exists - the triple-= (gpg===1.16.0-unknown) means that the version exists, but cannot be version compared: https://peps.python.org/pep-0440/#arbitrary-equality Suggested fix: - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with a '+'; that will compare as expected; - fix so "-unknown" isn't appended. Apparently, this is caused by insufficient fixes in 0001-avoid-identifying-as-beta.patch I've attached a FIXED version, which should fix things. Before: $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown. After: $ quilt push Applying patch 0001-avoid-identifying-as-beta-FIXED.patch $ autoreconf -ivf $ grep Generated.*gpgme configure # Generated by GNU Autoconf 2.71 for gpgme 1.16.0. Versions: $ lsb_release -a 2>/dev/null| grep Codename Codename: jammy $ apt-cache policy python3-gpg | grep Installed Installed: 1.16.0-1.2ubuntu4 Cheers, Walter Doekes OSSO B.V. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1910273] Re: Upgrade to groovy breaks DNS resolution
*** This bug is a duplicate of bug 1907878 *** https://bugs.launchpad.net/bugs/1907878 I am getting DOMAINS in /etc/resolve.conf: DOMAINS is initialized with "DOMAINS" in `/etc/network/if-up.d/resolved` and set in /run/systemd/resolve/netif/* ```bash $ cat /run/systemd/resolve/netif/3 # This is private data. Do not parse. LLMNR=yes MDNS=no SERVERS=DNS DOMAINS=DOMAINS ``` systemd-resolved adds DOMAINS to domains-searchlist: ```bash cat /etc/resolv.conf # This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 127.0.0.1 nameserver 192.168.2.1 search DOMAINS lan ``` DOMAINS=$DOMAINS would have no effect and could be omitted, As there are further errors form the if-down script (resolved: 12: mystatedir: not found), i've removed both `/etc/network/if-up.d/resolved` and `/etc/network/if- down.d/resolved`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1910273 Title: Upgrade to groovy breaks DNS resolution Status in ifupdown package in Ubuntu: Confirmed Bug description: ~# lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 ~# apt-cache policy ifupdown ifupdown: Instalēts: 0.8.35ubuntu2 Kandidāts: 0.8.35ubuntu2 Versiju tabula: *** 0.8.35ubuntu2 500 500 http://mirrors.digitalocean.com/ubuntu groovy/universe amd64 Packages 100 /var/lib/dpkg/status ~# Problem: Upon upgrade from Ubuntu 20.04 to Ubuntu 20.10, I expected name resolution upon reboot to work as usual. What happened: a) /var/log/syslog sprinkled with error messages: - /etc/network/if-up.d/resolved: 12: mystatedir: not found - /etc/network/if-up.d/resolved: 70: DNS: not found - /etc/network/if-up.d/resolved: 1: /run/network/ifupdown-inet-eth0: DNS=8.8.8.8 8.8.4.4: not found b) resolvectl dns returning no name servers Investigation: Recently changed /etc/network/if-up.d/resolved and /etc/network/if-down.d/resolved files contain programming errors. See https://git.launchpad.net/ubuntu/+source/ifupdown/commit/?id=54fec5eedfd59adaffe9021c271914578dd05d1b . Fix: $ diff /Users/pklavins/Downloads/ifupdown-0.8.35ubuntu2/debian/if-down.d/resolved if-down.d_resolved 12c12 < mystatedir statedir ifindex interface --- > # local mystatedir statedir ifindex interface $ diff /Users/pklavins/Downloads/ifupdown-0.8.35ubuntu2/debian/if-up.d/resolved if-up.d_resolved 12c12 < mystatedir statedir ifindex interface --- > # local mystatedir statedir ifindex interface 39,40c39,40 < DNS=DNS < DOMAINS=DOMAINS --- > DNS=$DNS > DOMAINS=$DOMAINS 42,43c42,43 < DNS=DNS6 < DOMAINS=DOMAINS6 --- > DNS=$DNS6 > DOMAINS=$DOMAINS6 47c47 < "$DNS"="$NEW_DNS" --- > DNS="$NEW_DNS" 51c51 < "$DOMAINS"="$NEW_DOMAINS" --- > DOMAINS="$NEW_DOMAINS" 70c70 < DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE --- > # local DNS DNS6 DOMAINS DOMAINS6 DEFAULT_ROUTE $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1910273/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
Michal, that's not how patching works, unfortunately. You can put all
that in a file and use the `patch` command. The easy way is to go to the
folder containing the file and run `sudo patch < /path/to/diff`.
Or you could simply edit the file (/usr/lib/python3/dist-
packages/softwareproperties/qt/SoftwarePropertiesQt.py) according to the
instructions given by the diff:
1. Starting at line 709, look at it and the following 7 lines for a total of
eight lines (this is what "-709,8" refers to in the original)
2. Note, too, that after the change, the same hunk is referenced as "+709,7"
meaning that the end result is one less line.
3. Remove the definition of the "url" variable in line 712.
4. In the next line (which is now 712) which defines the "filename" variable,
change it from using the KFileDialog.getOpenFileName method to the
QFileDialog.getOpenFileName method. Note that the arguments and their order are
different.
5. Save it and try again.
** Tags added: groovy hirsute
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
P.S. added Hirsute and Groovy tags since the latest dupe shows it
affects Hirsute and thus should affect Groovy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1914461] Re: Unable to import key file in "authentication" in Software sources"
*** This bug is a duplicate of bug 1795278 ***
https://bugs.launchpad.net/bugs/1795278
Were you to `lxqt-sudo software-propreties-qt` you would see that this
is a duplicate of the other bug. Technically, it's got a fix. You might
want to try testing it and maybe we can actually get this resolved once
and for all.
** This bug has been marked a duplicate of bug 1795278
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1914461
Title:
Unable to import key file in "authentication" in Software sources"
Status in software-properties package in Ubuntu:
New
Bug description:
Running test on Lubuntu Hirsute daily ISO from QA testing tracker
http://cdimage.ubuntu.com/lubuntu/daily-live/20210203/hirsute-desktop-
amd64.iso
Unable to import key file in "authentication tab" - no error message
received
Steps to produce the bug
1. Open Software Sources from Preferences menu
2. Go to "Authentication" tab
3. Select/Click on "+Import Key File"
4. Nothing happens and no error message is received
The file manager should have opened and browsed for the key to import
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: software-properties-qt 0.99.5
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu57
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Wed Feb 3 18:37:11 2021
InstallationDate: Installed on 2021-02-03 (0 days ago)
InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210203)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1914461/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
There are no PyKDE imports anymore, only PyQt. That said, replacing
`KUrl.fromPath` with just `QUrl` should resolve that.
But that's not our only issue:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 713, in add_key_clicked
filename = KFileDialog.getOpenFileName(url, 'application/pgp-keys',
self.userinterface, _("Import key"))
NameError: name 'KFileDialog' is not defined
So we replace `KFileDialog` with `QFileDialog` and move some arguments
around:
filename = QFileDialog.getOpenFileName(self.userinterface, _("Import
key"), url, 'application/pgp-keys')
The only other thing missing is that KFileDialog wanted a KUrl while
QFileDialog wants a string. So we should cast our QUrl call:
url = str(QUrl(home))
Maybe there's a prettier/better way to do this, but that's what I got
for 10 minutes which is more progress than I can say this bug has had in
the past XD If people can test those changes, it would be greatly
appreciated.
** Changed in: software-properties (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Triaged
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795278] Re: software-properties-{qt, kde} attempts to use KUrl but it doesn't exist
According to the dupe, this affects more recent versions, too. And not
just Kubuntu.
** Summary changed:
- software-properties-kde attempts to use KUrl but it doesn't exist
+ software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
** Tags added: eoan focal kubuntu lubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1795278
Title:
software-properties-{qt,kde} attempts to use KUrl but it doesn't exist
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
Release: Kubuntu 18.04
Version: 0.96.24.32.1
When clicking the "Import Key" button in the "Authentication" section
of the panel it throws this error:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py",
line 667, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
While this doesn't crash the program it causes nothing to happen when
clicking the button. Running the program in a terminal reveals the
error being printed to stderr.
After debugging it appears KUrl doesn't exist anywhere and I'm not
sure if's a python module that has changed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1795278/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865906] Re: software-properties-{qt, kde} import key issue
*** This bug is a duplicate of bug 1795278 ***
https://bugs.launchpad.net/bugs/1795278
** Summary changed:
- software-properties-* import key issue
+ software-properties-{qt,kde} import key issue
** This bug has been marked a duplicate of bug 1795278
software-properties-kde attempts to use KUrl but it doesn't exist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1865906
Title:
software-properties-{qt,kde} import key issue
Status in software-properties package in Ubuntu:
Confirmed
Bug description:
My system: Lubuntu 19.04 run from Live-CD (from the original ISO
image)
Note: Followig issue apply to both software-properties: Qt and KDE run from
LiveCD.
After opening thru the console (as root) the software-properties,
switching to the "Authentication" tab and pressing the "Import key
file", I recieve following error output:
# software-properties-qt
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
Trackback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 712, in add_key_clicked
url = KUrl.fromPath(home)
NameError: name 'KUrl' is not defined
=
same happens with software-properties-kde.
When I'm trying to check their version, I'll get following output:
# software-properties-qt -v
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-
root'
software-properties-qt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1865906/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1865906] Re: software-properties-* import key issue
** No longer affects: lubuntu-meta (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1865906 Title: software-properties-* import key issue Status in software-properties package in Ubuntu: Confirmed Bug description: My system: Lubuntu 19.04 run from Live-CD (from the original ISO image) Note: Followig issue apply to both software-properties: Qt and KDE run from LiveCD. After opening thru the console (as root) the software-properties, switching to the "Authentication" tab and pressing the "Import key file", I recieve following error output: # software-properties-qt QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Trackback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 712, in add_key_clicked url = KUrl.fromPath(home) NameError: name 'KUrl' is not defined = same happens with software-properties-kde. When I'm trying to check their version, I'll get following output: # software-properties-qt -v QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime- root' software-properties-qt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1865906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288786] Re: pkexec does not launch graphical authentication
That last comment is correct and can be further verified in the docs: https://help.ubuntu.com/community/RootSudo "gksu has been replaced by pkexec, but even pkexec is being deprecated by the mainline Ubuntu developers. They have taken the position that file manipulation and editing under root should be restricted to the command line. We can only surmise what the motives were behind this decision: perhaps there are just too many users who run into problems running graphical apps as root. In any case, running graphical apps as root now requires workarounds and additional steps." ** Changed in: policykit-1 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1288786 Title: pkexec does not launch graphical authentication Status in policykit-1 package in Ubuntu: Won't Fix Bug description: Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop. In buth desktops, I tried to launch synaptic to install some packages. If I try to launch from menu, nothing seems to happen. From a terminal, I ran pkexec "/usr/sbin/synaptic" and saw that it asks for password in the terminal window, instead of popping up an authentication window like previous Ubuntu version did. That was why I saw no authentication request when launching from menu.. I have a workaround)launching from Terminal window), but this should be fixed before release. ralph@minnie:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" ralph@minnie:~$ pkexec --version pkexec version 0.105 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1288786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1549310] Re: Removing or causing lubuntu-desktop to be removed marks packages for autoremove
Lubuntu's metapackages depend on the behavior that Julian describes, so this *is* normal and will not be changing. ** Changed in: lubuntu-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1549310 Title: Removing or causing lubuntu-desktop to be removed marks packages for autoremove Status in apt package in Ubuntu: Invalid Status in lubuntu-meta package in Ubuntu: Invalid Bug description: Ex. $ sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. lubuntu@lubuntu:~$ sudo apt-get remove lubuntu-desktop Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: abiword abiword-common apturl apturl-common evolution-data-server-common gecko-mediaplayer gnome-mplayer language-selector-gnome liba52-0.7.4 libabiword-3.0 libass4 libavresample1 libbluray1 libcamel-1.2-45 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libclutter-1.0-0 libclutter-gtk-1.0-0 libcogl-pango15 libcogl15 libdca0 libdirectfb-1.2-9 libdiscid0 libdvdread4 libebook-contacts-1.2-0 libedataserver-1.2-18 libenca0 libfs6 libgbm1 libgda-5.0-4 libgda-5.0-common libglu1-mesa libgmlib1 libgmtk1 libgmtk1-data libgpod4 libical1 libjs-jquery libloudmouth1-0 liblua5.2-0 libmad0 libmhash2 libmusicbrainz3-6 libots0 libpostproc52 libquvi-scripts libquvi7 libraptor2-0 librasqal3 librdf0 libtelepathy-glib0 libtidy-0.99-0 libts-0.0-0 libvdpau1 libwmf0.2-7 libwpd-0.9-9 libwpg-0.2-2 libwps-0.2-2 libwv-1.2-4 libyajl2 lubuntu-core mplayer2 tsconf x11-apps x11-session-utils x11-xfs-utils xinit xorg Use 'apt-get autoremove' to remove them. The following packages will be REMOVED: lubuntu-desktop 0 upgraded, 0 newly installed, 1 to remove and 6 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.11 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CasperVersion: 1.340.2 CurrentDesktop: LXDE Date: Wed Feb 24 14:32:13 2016 LiveMediaBuild: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1549310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
The fix is now released. Spinning up a new ISO as we speak. calamares-settings-ubuntu (1:19.10.2) eoan; urgency=medium * Fix initramfs job failing. Thanks to TJ for the fix! (LP: #1829805) * Move before_bootloader_mkdirs process before initramfs. * Workaround bug in update-initramfs::get_sorted_versions() with shellprocess. -- Walter Lapchynski Wed, 19 Jun 2019 19:32:14 -0700 ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Fix Released ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Critical ** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Walter Lapchynski (wxl) -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) 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 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 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/1829805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
We got a potential fix thanks to TJ that seems to be working wonderfully from what I can ascertain: https://phab.lubuntu.me/D15 Download the raw diff, cd /etc/calamares, sudo patch --strip 2 < /path/to/diff, and install like normal. Done! -- 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) 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 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 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/1829805/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
** Description changed: - GTK2 applications randomly crash or freeze with same error. See attached - files. + GTK2 applications randomly crash or freeze with error like: + + [xcb] Unknown sequence number while processing queue + [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called + [xcb] Aborting, sorry about that. + : ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. + + where is the name of the executable, e.g. audacious, + soffice.bin, etc. + + RELATED BUGS + LibreOffice: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161 + PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 + Audacious: https://redmine.audacious-media-player.org/issues/798 + FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084 + + OTHER APPLICATIONS + SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems. ** Description changed: GTK2 applications randomly crash or freeze with error like: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. : ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. where is the name of the executable, e.g. audacious, soffice.bin, etc. RELATED BUGS LibreOffice: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161 PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 Audacious: https://redmine.audacious-media-player.org/issues/798 FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084 + ClawsMail: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 OTHER APPLICATIONS SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: GTK2 applications randomly crash or freeze with error like: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. : ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. where is the name of the executable, e.g. audacious, soffice.bin, etc. RELATED BUGS LibreOffice: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161 PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 Audacious: https://redmine.audacious-media-player.org/issues/798 FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084 ClawsMail: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 OTHER APPLICATIONS SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
Looks like there's an upstream bug against Claws Mail, too: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 ** Bug watch added: Claws Mail bugzilla #4203 http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: GTK2 applications randomly crash or freeze with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793876] Re: software-properties-qt/kde does not show in menus
Between these changes, should be sorted: software-properties (0.97.11) disco; urgency=medium * Added software-properties-lxqt.desktop and software-properties- drivers-lxqt.desktop to software-properties-qt.install -- Hans P Moller Thu, 11 Apr 2019 12:04:11 -0400 software-properties (0.97.10) disco; urgency=medium * Remove lxqt-sudo from exec line in software-properties-qt.desktop (LP: #1823306) * Make invisible software-properties-qt.desktop * Create software-properties-lxqt.desktop with lxqt-sudo and shown only in LXQt * Rename software-properties-drivers-qt.desktop to software-properties-drivers-lxqt.desktop -- Hans P Möller Wed, 10 Apr 2019 16:38:53 -0400 ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1793876 Title: software-properties-qt/kde does not show in menus Status in software-properties package in Ubuntu: Fix Released Bug description: Cosmic and Bionic Desktop file sets: NoDisplay=true resulting in no software sources menu entry in KDE menu. This was probably just about ok when Plasma Discover was able to launch this via a menu item in its options, but at least for Plasma 5.13 this is currently broken, and Discover's built-in source selection has further issues. Plus many users decide not to use Discover at all, and even uninstall it altogether. Not withstanding all that, it is just desirable that someone can just type "software" or "sources" in to the search box in Plasma's main menu and find the menu item/launcher for this and use software- properties without having to go a more complicated path. Solution is simply removing the "NoDisplay=true" line from the .desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1793876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor
** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #54 https://gitlab.gnome.org/GNOME/glib/issues/54 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/issues/54 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/378783 Title: xdg-open *.desktop opens text editor Status in GLib: Unknown Status in gvfs: New Status in glib2.0 package in Ubuntu: Triaged Bug description: Binary package hint: xdg-utils In order to reproduce it execute "xdg-open *.desktop" (choose any .desktop file, e.g. one from /usr/share/applications). Actually your favorite text editor will open the file. Expected result: It'll be executed. Because of this bug, desktop entries with the new "#!/usr/bin/env xdg- open" shebang feature were opened in the text editor when executed from command line. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/378783/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1824002] [NEW] python3-launchpadlib needs promotion from suggests
Public bug reported: If one wants to apport-collect, one gets an error about python3-launchpadlib needing to be installed. One can easily install it, but it really should be a Recommend, if not a Depend so one doesn't have to go through this trouble. Right now, it's a Suggest. It seems that during the whole Python2/3 transition some things got switched around, but it had been a Depend for a long time before that. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1824002 Title: python3-launchpadlib needs promotion from suggests Status in apport package in Ubuntu: New Bug description: If one wants to apport-collect, one gets an error about python3-launchpadlib needing to be installed. One can easily install it, but it really should be a Recommend, if not a Depend so one doesn't have to go through this trouble. Right now, it's a Suggest. It seems that during the whole Python2/3 transition some things got switched around, but it had been a Depend for a long time before that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
** Description changed: - Some gkt2 applications randomly crash with same error. See attached + GTK2 applications randomly crash or freeze with same error. See attached files. ** Changed in: gtk+2.0 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: GTK2 applications randomly crash or freeze with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
** Summary changed: - !xcb_xlib_threads_sequence_lost error + !xcb_xlib_threads_sequence_lost error with GTK2 applications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: Some gkt2 applications randomly crash with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error
Related pcmanfm bug https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1808710 Title: !xcb_xlib_threads_sequence_lost error Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: Some gkt2 applications randomly crash with same error. See attached files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1801439] Re: Unable to add PPA's via the software-properties
Also fails for the example "deb http://archive.ubuntu.com/ubuntu cosmic main" ** Changed in: software-properties (Ubuntu) Importance: Undecided => High ** Changed in: software-properties (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - Unable to add PPA's via the software-properties + Unable to add software sources via the software-properties ** Description changed: Test - 1. Start Software-properties. E.g. sudo software-properties-qt + 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA - 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " + 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked - self.add_source_from_line(line) - File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line - enable_source_code=enable_source_code) - File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut - worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) - File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut - self.options.keyserver)}) + File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked + self.add_source_from_line(line) + File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line + enable_source_code=enable_source_code) + File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut + worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) + File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut + self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52 2018 InstallationDate: Installed on 2018-10-19 (14 days ago) InstallationMedia: Lubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1801439 Title: Unable to add software sources via the software-properties Status in software-properties package in Ubuntu: Triaged Bug description: Test 1. Start Software-properties. E.g. sudo software-properties-qt 2. Navigate to Other Software (Tab), Add -> Add, to add a PPA 3. Insert the PPA string. E.g. "deb http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu cosmic main " (or even the example repo given in the dialog, which is not a PPA) 4. Click Okay. The software sources list does not contain the new field. Executing in terminal results in the following error message. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 627, in on_add_clicked self.add_source_from_line(line) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 752, in add_source_from_line enable_source_code=enable_source_code) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 769, in add_source_from_shortcut worker = self.check_and_add_key_for_whitelisted_shortcut(shortcut) File "/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 709, in check_and_add_key_for_whitelisted_shortcut self.options.keyserver)}) AttributeError: type object 'OptionParsed' has no attribute 'keyserver' ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: software-properties-qt 0.96.27 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: LXQt Date: Sat Nov 3 09:59:52
[Touch-packages] [Bug 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
Result of: dpkg -l > dpkgl.txt ** Attachment added: "dpkgl.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1793640/+attachment/5204898/+files/dpkgl.txt ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Confirmed ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]
OK, I undup, the sound card is the same, though. -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370] Status in pulseaudio package in Ubuntu: Incomplete Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
** This bug is no longer a duplicate of bug 1781294 No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370] -- 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/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370]
Daniel, I did what you suggest in #10 and no change. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360/9370] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
Bug #1784485 is also reporting sound problems with the same audio card as the systems in this bug, but I'm not sure if it can be duplicated to this bug. -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
In my case if I do: sudo alsa force-reload the sound card is detected. If I'm plugged into the Dell dock station it keeps detecting only a USB headphone (and it works through that both with pulseaudio and alsa). -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
I have a XPS 13 9370 with the same card and I'm seeing exactly the same. My card was being detected correctly in Ubuntu 18.04 but stopped being detected when I upgraded to the Ubuntu 18.10 development version. -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1741591] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1781294 *** https://bugs.launchpad.net/bugs/1781294 ** This bug has been marked a duplicate of bug 1781294 No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] -- 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/1741591 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I have an HP 15-CC129TX Laptop with Intel Corporation Sunrise Point-LP HD Audio. But Ubuntu 17.10 is not detecting my sound card and is displaying dummy output in my sound settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 09:07:37 2018 InstallationDate: Installed on 2018-01-05 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1741591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1781294 *** https://bugs.launchpad.net/bugs/1781294 I've changed the title because according to lspci the audio device is actually Intel Corporation Sunrise Point-LP HD Audio (rev 21) ** Summary changed: - [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card + [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card ** This bug has been marked a duplicate of bug 1781294 No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] -- 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/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1793640] [NEW] [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic regression-update ** Tags added: regression-update -- 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/1793640 Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1793640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
Can anybody please nominate this bug for bionic because it produces an error when trying to upgrade from 18.04 to 18.10? See: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1790693 and https://bugs.launchpad.net/ubuntu/+source/ubuntu-release- upgrader/+bug/1793164 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
bodhi, having the Technical Board review Phillip's posts might be completely reasonable so as to finally end this conversation once and for all. That has no bearing on the moderation, though. The entire Ubuntu Community is bound by the terms of the Code of Conduct, which, in short, means being nice to one another, regardless of our points of view. So, I'm sorry, you don't just get to treat people however you want just because you disagree with them. There is no moderation as it concerns your attempts to correct a confusing technical situation. Where the moderation exists is where it no longer remains technical and especially where it becomes a personal attack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround:
[Touch-packages] [Bug 1790244] [NEW] Ubuntu dots won't stop appearing/blank screen when unsuspending
Public bug reported: I have two persistent problems that I haven't been able to resolve with Ubuntu 18.04: 1) the Ubuntu splash screen "dots" that turn white then red then white again don't stop appearing after I've booted up and even after I logged in. They keep appearing as I try to do stuff. They don't seem to stop anything from working, but they sure are annoying. 2) when I unsuspend my computer, it wakes up based on the disk etc. LEDs but the monitor screen remains black. I know my machine supports suspend because it worked under 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 31 17:31:13 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation 82915G/GV/910GL Integrated Graphics Controller [8086:2582] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 82915G/GV/910GL Integrated Graphics Controller [103c:300c] InstallationDate: Installed on 2016-12-03 (636 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP Compaq dc5100 MT(PZ583UA) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=c8c2f5c1-ae82-41ac-bd05-9f22b78dbead ro nomodeset=1 vesafb.invalid=1 mem_sleep_default=deep nomodeset=1 plymouth:debug=1 quiet splash vesafb.invalid=1 mem_sleep_default=deep vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786C2 v01.09 dmi.board.name: 09E0h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: MXL54202Q2 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786C2v01.09:bd08/06/2008:svnHewlett-Packard:pnHPCompaqdc5100MT(PZ583UA):pvr:rvnHewlett-Packard:rn09E0h:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq dc5100 MT(PZ583UA) dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Aug 31 17:25:57 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech M525MOUSE, id 8 inputMicrosoft LifeCam VX-5000: Micr KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1790244 Title: Ubuntu dots won't stop appearing/blank screen when unsuspending Status in xorg package in Ubuntu: New Bug description: I have two persistent problems that I haven't been able to resolve with Ubuntu 18.04: 1) the Ubuntu splash screen "dots" that turn white then red then white again don't stop appearing after I've booted up and even after I logged in. They keep appearing as I try to do stuff. They don't seem to stop anything from working, but they sure are annoying. 2) when I unsuspend my computer, it wakes up based on the disk etc. LEDs but the monitor screen remains black. I know my machine supports suspend because it worked under 16.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Phillip and bodhi, I know this is something we have discussed before, but I'm going to say it again and hopefully for the last time: please keep your comments civil. You can disagree with each other all you want, but do it respectfully, please. If you see yourself using the word "you" (or if it's implied) in a comment, that's a sign you're probably doing something wrong. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: Invalid Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: Fix Released Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386
[Touch-packages] [Bug 1202754] Re: update-manager crashed with SystemExit in exit(): 0
** Changed in: click-update-manager (Ubuntu) Assignee: faiz (starone-faiz) => Walter (s-walter) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-update-manager in Ubuntu. https://bugs.launchpad.net/bugs/1202754 Title: update-manager crashed with SystemExit in exit(): 0 Status in Ubuntu Kylin: Fix Released Status in Software Updater: New Status in click-update-manager package in Ubuntu: Fix Released Bug description: Errors bucket https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:SystemExit:commit:_inline_callbacks:_show_transaction:_inline_callbacks:commit:_action_done:exit I was going to check for updates, but the Update-Manager has closed itself. ProblemType: CrashDistroRelease: Ubuntu 13.10 Package: update-manager 1:0.189 ProcVersionSignature: Ubuntu 3.10.0-3.12-generic 3.10.1 Uname: Linux 3.10.0-3-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu4 Architecture: i386 Date: Thu Jul 18 20:46:05 2013 ExecutablePath: /usr/bin/update-manager InterpreterPath: /usr/bin/python3.3 MarkForUpload: True PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']SourcePackage: update-manager Title: update-manager crashed with SystemExit in exit(): 0 UpgradeStatus: Upgraded to saucy on 2013-03-21 (118 days ago) UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1202754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768970] Re: Bionic: ubuntu-bug / apport not present
Lubuntu Next was never officially released, even though we had beta/alpha versions. Additionally, the idea of having both a LXDE and LXQt image is something we will not be continuing for the Cosmic cycle. Instead, we will be switching over to LXQt entirely. It will most certainly have apport in it, though we will need to do some packaging work on the Qt frontend (apport-kde) as it's a little less Qt and a little more KDE. That said, I've co-opted this bug for that purpose. ** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Simon Quigley (tsimonq2) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1768970 Title: Bionic: ubuntu-bug / apport not present Status in Lubuntu Next: Won't Fix Status in apport package in Ubuntu: Triaged Bug description: [I am not sure if apport was present in the previous (17.10) Lubuntu Next, or that as now, I had to install it...] I wished to report a bug, as I have often done before, and used the terminal to invoke ubuntu-bug. I was informed that I needed to install apport to gain that command. I did so, but then wondered if apport's absence was a mistake, or an intentional decision to omit the package... The ability to report crashes/bugs seems like such an obvious and necessary thing to include, for any distro... To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-next/+bug/1768970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 607999] Re: gsettings-data-convert crashed with signal 5 in g_object_newv()
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Beyond that, I have not seen a bug likes this in many years. If you could provide additional information on how it affects a currently supported release, that would be most helpful. ** Changed in: gconf (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/607999 Title: gsettings-data-convert crashed with signal 5 in g_object_newv() Status in gconf: New Status in gconf package in Ubuntu: Incomplete Bug description: Binary package hint: gconf got this after running updates in maverick ProblemType: Crash DistroRelease: Ubuntu 10.10 Package: gconf2 2.31.6-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-8.13-generic 2.6.35-rc5 Uname: Linux 2.6.35-8-generic x86_64 Architecture: amd64 Date: Tue Jul 20 23:56:30 2010 ExecutablePath: /usr/bin/gsettings-data-convert InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100605) ProcCmdline: gsettings-data-convert ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash Signal: 5 SourcePackage: gconf StacktraceTop: ?? () from /usr/lib/libgio-2.0.so.0 ?? () from /usr/lib/libgio-2.0.so.0 g_object_newv () from /usr/lib/libgobject-2.0.so.0 g_object_new_valist () g_object_new () from /usr/lib/libgobject-2.0.so.0 Title: gsettings-data-convert crashed with signal 5 in g_object_newv() UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/gconf/+bug/607999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761911] Re: Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot
Before I submitted this, I had run the following command, per the web page mentioned above. sudo apt-get install libnl-3-200=3.2.21-1 libnl-route-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 After submitting this, I ran the following commands: sudo apt-get update sudo apt-get install network-manager network-manager was reinstalled, and my server gets connected to the LAN again automatically after I reboot. network-manager-gnome was also reinstalled. I'd like to know if I can safely do sudo apt-mark unhold libnl-3-200 libnl-genl-3-200 libnl-route-3-200 For now, I'll just stick with the downgraded libnl packages as I don't want to have more networking problems. -- 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/1761911 Title: Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot Status in network-manager package in Ubuntu: New Bug description: I did an upgrade with "sudo apt-get dist-upgrade", and it removed network-manager and network-manager-gnome. I could not connect to my LAN afer that. I was able to find instructions for downgrading the libnl packages at https://askubuntu.com/questions/727127/last-upgrade-crashes-network-manager-no-internet-connection-no-applet I am able to get online again by running the following commands sudo ifconfig eth0 up sudo dhclient eth0 (Fortunately, I have a Ethernet I can plug in to.) I have to do this every time I reboot. This is inconvenient as a usually use Desktop Sharing with another computer as the client. I use an SSH tunnel for security. This means that every time I reboot, I have to physically access the computer's console to enter the ifconfig and dhclient commands to get the computer back on the network. I tried to reinstall network-manager and network-manager-gnome, but the command results said there were dependencies that prevented the installation. The fixes in the web page referenced above do not help, so I'm reporting this as a bug. Thanks for your assistance. $ sudo lsb_release -rd [sudo] password for wally: Description: Ubuntu 14.04.1 LTS Release: 14.04 $ $ apt-cache policy network-manager network-manager: Installed: (none) Candidate: 0.9.8.8-0ubuntu7.1 Version table: 0.9.8.8-0ubuntu7.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager (not installed) ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 6 21:21:27 2018 InstallationDate: Installed on 2014-10-22 (1262 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1761911/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761911] [NEW] Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot
Public bug reported: I did an upgrade with "sudo apt-get dist-upgrade", and it removed network-manager and network-manager-gnome. I could not connect to my LAN afer that. I was able to find instructions for downgrading the libnl packages at https://askubuntu.com/questions/727127/last-upgrade-crashes-network-manager-no-internet-connection-no-applet I am able to get online again by running the following commands sudo ifconfig eth0 up sudo dhclient eth0 (Fortunately, I have a Ethernet I can plug in to.) I have to do this every time I reboot. This is inconvenient as a usually use Desktop Sharing with another computer as the client. I use an SSH tunnel for security. This means that every time I reboot, I have to physically access the computer's console to enter the ifconfig and dhclient commands to get the computer back on the network. I tried to reinstall network-manager and network-manager-gnome, but the command results said there were dependencies that prevented the installation. The fixes in the web page referenced above do not help, so I'm reporting this as a bug. Thanks for your assistance. $ sudo lsb_release -rd [sudo] password for wally: Description:Ubuntu 14.04.1 LTS Release:14.04 $ $ apt-cache policy network-manager network-manager: Installed: (none) Candidate: 0.9.8.8-0ubuntu7.1 Version table: 0.9.8.8-0ubuntu7.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager (not installed) ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 6 21:21:27 2018 InstallationDate: Installed on 2014-10-22 (1262 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1761911 Title: Have to manually "sudo ifconfig eth0 up" and "sudo dhclient eth0" after every reboot Status in network-manager package in Ubuntu: New Bug description: I did an upgrade with "sudo apt-get dist-upgrade", and it removed network-manager and network-manager-gnome. I could not connect to my LAN afer that. I was able to find instructions for downgrading the libnl packages at https://askubuntu.com/questions/727127/last-upgrade-crashes-network-manager-no-internet-connection-no-applet I am able to get online again by running the following commands sudo ifconfig eth0 up sudo dhclient eth0 (Fortunately, I have a Ethernet I can plug in to.) I have to do this every time I reboot. This is inconvenient as a usually use Desktop Sharing with another computer as the client. I use an SSH tunnel for security. This means that every time I reboot, I have to physically access the computer's console to enter the ifconfig and dhclient commands to get the computer back on the network. I tried to reinstall network-manager and network-manager-gnome, but the command results said there were dependencies that prevented the installation. The fixes in the web page referenced above do not help, so I'm reporting this as a bug. Thanks for your assistance. $ sudo lsb_release -rd [sudo] password for wally: Description: Ubuntu 14.04.1 LTS Release: 14.04 $ $ apt-cache policy network-manager network-manager: Installed: (none) Candidate: 0.9.8.8-0ubuntu7.1 Version table: 0.9.8.8-0ubuntu7.1 0 500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 Packages 100 /var/lib/dpkg/status 0.9.8.8-0ubuntu7 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages $ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager (not installed) ProcVersionSignature: Ubuntu 3.13.0-144.193-generic 3.13.11-ckt39 Uname: Linux 3.13.0-144-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 6 21:21:27 2018 InstallationDate: Installed on 2014-10-22 (1262 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
** Description changed: + READ ME FIRST + = + This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. + + --- + Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial - ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: synaptic (Ubuntu) Importance: Medium => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749670] Re: Display Arrangement is changed after changing the Display Mode
Also includes other properties like "Scale". Changing between "Join Display" and "External Only" switches the scale to 100%. -- 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/1749670 Title: Display Arrangement is changed after changing the Display Mode Status in xorg package in Ubuntu: Confirmed Bug description: The Display Arrangement is changed after changing the Display Mode (single display, mirror, join displays). I have a notebook connected to an external display which is physically placed on the right side of the notebook and which I typically is as my primary display. The default seems to be that the primary display is the notebook ones on the left and the joined external on the right. In the Gnome display settings I can change both to make the external display the primary one and move it to the right. So far all perfect. However I often disable my notebook display. Typically using the %SUPER%-P shortcut but also using the Gnome display settings. Unfortunately when I switch back to joined displays the placement gets messed up. While it is remembered that my external was chosen as the primary one (opposed to the default) the placement gets reset and the primary display is assumed to be on the right despite having it arranged it the Gnome Display settings to the right before. As a result I have to re-arrange it manually using the Gnome Display settings every time I switch back to joined displays. Is there anyway to make Ubuntu/Gnome/Xorg remember the display arrangement? Or as a workaround switch the arrangement with another shortcut? P.S. I'm using Xorg and NVIDIA 390.25 drivers from the graphics PPA in case that's important in any way. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.25 Wed Jan 24 20:02:43 PST 2018 GCC version: gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3) ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 10:52:43 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-31-generic, x86_64: installed bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed nvidia-390, 390.25, 4.13.0-32-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP104M [GeForce GTX 1070 Mobile] [10de:1be1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070 Mobile] [1558:65a4] InstallationDate: Installed on 2018-01-16 (29 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Notebook P65_67HSHP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=5b2c0693-6cca-4666-9bfc-7ecb40dee064 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04RTR1 02/21/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: P65_67HSHP dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RTR102/21/2017:bd02/21/2017:svnNotebook:pnP65_67HSHP:pvrNotApplicable:rvnNotebook:rnP65_67HSHP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: P65_67HSHP dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications
[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
Same for me. I really don't understand how /etc/resolv.conf should be managed in Ubuntu 17.04. I have the setup described in comment #7. I tried to have only network-manager manage /etc/resolv.conf, but then I loose name resolution in containers. I think we should open a new bug report, as this one marked with "Fix released" will never get attention. It may also something worth investigating upstream. -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: Fix Released Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ 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 # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ 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 # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET53W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2FK00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET53W(1.27):bd07/13/2017:svnLENOVO:pn20FRS2FK00:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2FK00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2FK00 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1717995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
We need to talk about software here, not personal issues. You both are going to stop attacking each other, defending yourself against each other, and talk about software. If you cannot talk about the software without getting these other issues intermingled here, do not comment at all. Since you seem to be concerned about the user experience, please recognize the user experience for all the people looking at this bug reports. Be nice. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in Settings editor for LightDM GTK+ Greeter: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: Won't Fix Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Again: let's keep any further discussion about people directed towards community-coun...@lists.ubuntu.com and let's keep the bug report for talking about the actual software. In other words, no more comments about the CoC violations in this bug report. Let's get back to talking about the software. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: New Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink /run/systemd/system/-.mount → /dev/null. Created symlink /run/systemd/system/run-user-1000.mount → /dev/null. Created symlink /run/systemd/system/run-user-121.mount → /dev/null. Created symlink /run/systemd/system/tmp.mount → /dev/null. No protocol specified (gpartedbin:12831): Gtk-WARNING **: cannot open display: :0 Removed /run/systemd/system/-.mount. Removed /run/systemd/system/run-user-1000.mount. Removed /run/systemd/system/run-user-121.mount. Removed /run/systemd/system/tmp.mount. $ pkexec backintime-qt4 Back In Time Version: 1.1.12 Back In Time comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions; type `backintime --license' for details. No protocol specified app.py: cannot connect to X server :0 Expected results: * backintime-qt4 may be run as root Actual results: * unable to run backintime-qt4 as root Workaround: * setting "xhost +si:localuser:root" helps. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: backintime-qt4 1.1.12-2 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic i686 ApportVersion: 2.20.6-0ubuntu7 Architecture: i386 CurrentDesktop: GNOME Date: Sun Aug 27 14:23:14 2017 InstallationDate: Installed on 2017-08-26 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark"
[Touch-packages] [Bug 1713313] Re: Unable to launch pkexec'ed applications on Wayland session
Speaking as a member of the Ubuntu Community Council, I'm going to have to ask that we dial down the tone here. As you know, the Code of Conduct (https://www.ubuntu.com/about/about-ubuntu/conduct) means that we should act with respect and consideration, act collaboratively and work towards consensus and clarity. That's sadly not what I'm seeing in this discussion and we need to put an end to it. I will also comment that if anyone sees a violation of this, the appropriate action is not to escalate the language, but to take it down a notch. If you don't feel like you can do that, that's what the Community Council is for. Discussing someone's personal history publicly not to mention speculating about someone's medical conditions, however appropriate it is in regards to a violation of the CoC, is not in any way respectful or considerate. That said, let's keep any further discussion about people directed towards community-coun...@lists.ubuntu.com and let's keep the bug report for talking about the actual software. Speaking of the bug, some things to point out: 1. I note that this is a known issue in the 17.10 release (https://wiki.ubuntu.com/ArtfulAardvark/ReleaseNotes#Desktop) with a note suggesting that Fedora is the upstream. That said, if the problem is an issue of upstream Wayland security policy, then, this is a bug report that should be filed upstream. In other words, it is not an Ubuntu problem. 2. If the issue is how Ubuntu deals with this, there are currently several documented workaround to fixing the problem as above, and it's clear that other work is being done (PolicyKit, admin URIs, etc.) to try to solve this problem once and for all. Thank you all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1713313 Title: Unable to launch pkexec'ed applications on Wayland session Status in Back In Time: Fix Released Status in Boot-Info: Fix Committed Status in Boot-Repair: Fix Committed Status in GNOME Terminal: New Status in OS-Uninstaller: Fix Committed Status in Y PPA Manager: New Status in apport package in Ubuntu: New Status in apt-offline package in Ubuntu: New Status in backintime package in Ubuntu: Confirmed Status in budgie-welcome package in Ubuntu: Invalid Status in caja-admin package in Ubuntu: New Status in cinnamon package in Ubuntu: Invalid Status in ettercap package in Ubuntu: Confirmed Status in gdebi package in Ubuntu: Confirmed Status in gdm3 package in Ubuntu: New Status in gnunet-gtk package in Ubuntu: Confirmed Status in gparted package in Ubuntu: Invalid Status in gui-ufw package in Ubuntu: Confirmed Status in guidedog package in Ubuntu: New Status in hplip package in Ubuntu: Confirmed Status in italc package in Ubuntu: New Status in laptop-mode-tools package in Ubuntu: New Status in lightdm-gtk-greeter-settings package in Ubuntu: Confirmed Status in nautilus-admin package in Ubuntu: New Status in needrestart-session package in Ubuntu: Confirmed Status in nemo package in Ubuntu: Confirmed Status in policykit-1 package in Ubuntu: Invalid Status in scanmem package in Ubuntu: New Status in scap-workbench package in Ubuntu: Confirmed Status in sirikali package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Confirmed Status in thunar package in Ubuntu: New Status in tuned package in Ubuntu: New Status in ubuntustudio-controls package in Ubuntu: New Status in ubuntustudio-default-settings package in Ubuntu: Invalid Status in update-notifier package in Ubuntu: New Status in xdiagnose package in Ubuntu: Confirmed Status in xubuntu-default-settings package in Ubuntu: Invalid Status in zulucrypt package in Ubuntu: Fix Released Bug description: * Main upstream discussion & fixes example to deal with wayland: https://bugzilla.gnome.org/show_bug.cgi?id=776437 * Steps to reproduce: 1. Install Ubuntu 17.10 2. Install backintime-qt4 or gparted application from above list (full may be acquired from https://codesearch.debian.net/search?q=pkexec+filetype%3Adesktop+path%3A*%2Fapplications%2F*=1=4 ) 3a. Try to launch backintime-qt4 from shortcut "Back In Time (root)" (located in /usr/share/applications/backintime-qt4-root.desktop, it uses pkexec ($ cat /usr/share/applications/backintime-qt4-root.desktop | grep Exec Exec=pkexec backintime-qt4) 3b. Try to launch Gparted from shortcut "GParted" (located in /usr/share/applications/gparted.desktop, it uses gparted-pkexec) 4a.1. Back In Time does not start from GUI. 4a.2. Back In Time shows error message in console: 4b. gparted-pkexec does not start, reports error $ gparted-pkexec Created symlink
[Touch-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up
I think I found the issue: #cat /etc/resolvconf.conf # Use the local name server name_servers=127.0.0.1 # added for dnscrypt + dnssec options edns0 The options edns0 is clearly invalid, so, once I commented it, it now works. I can restart NetworkManager as often as I like and it appears to come up just fine. -- 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/1728013 Title: NetworkManager segfaults when starting and an interface is up Status in network-manager package in Ubuntu: New Bug description: This is the kernel output I get when restarting NetworkManager with an interface being up. This is reproducible across all of my machines. I am running Funtoo with gentoo sources 4.13.9 and have been able to reproduce this problem for over 6 months. [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up
I see this repeatedly in the logs. Just prior to the segfault, NetworkManager is clearing out DNS information. Oct 26 22:40:37 localhost NetworkManager[484]: [1509072037.0735] dns-mgr: Removing DNS information from /sbin/resolvconf Oct 26 22:40:37 localhost kernel: NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] -- 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/1728013 Title: NetworkManager segfaults when starting and an interface is up Status in network-manager package in Ubuntu: New Bug description: This is the kernel output I get when restarting NetworkManager with an interface being up. This is reproducible across all of my machines. I am running Funtoo with gentoo sources 4.13.9 and have been able to reproduce this problem for over 6 months. [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728013] Re: NetworkManager segfaults when starting and an interface is up
I am also running NetworkManager 1.4.4-r1. -- 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/1728013 Title: NetworkManager segfaults when starting and an interface is up Status in network-manager package in Ubuntu: New Bug description: This is the kernel output I get when restarting NetworkManager with an interface being up. This is reproducible across all of my machines. I am running Funtoo with gentoo sources 4.13.9 and have been able to reproduce this problem for over 6 months. [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728013] [NEW] NetworkManager segfaults when starting and an interface is up
Public bug reported: This is the kernel output I get when restarting NetworkManager with an interface being up. This is reproducible across all of my machines. I am running Funtoo with gentoo sources 4.13.9 and have been able to reproduce this problem for over 6 months. [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000] ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1728013 Title: NetworkManager segfaults when starting and an interface is up Status in network-manager package in Ubuntu: New Bug description: This is the kernel output I get when restarting NetworkManager with an interface being up. This is reproducible across all of my machines. I am running Funtoo with gentoo sources 4.13.9 and have been able to reproduce this problem for over 6 months. [Thu Oct 26 22:40:36 2017] NetworkManager[484]: segfault at 8 ip 00479ef7 sp 7fffb903eb60 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:46:40 2017] NetworkManager[9577]: segfault at 8 ip 00479ef7 sp 7fffefab0200 error 4 in NetworkManager[40+23b000] [Thu Oct 26 22:48:37 2017] NetworkManager[9936]: segfault at 8 ip 00479ef7 sp 7ffd46445950 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:16:19 2017] NetworkManager[4029]: segfault at 8 ip 00479ef7 sp 7fff07455bc0 error 4 in NetworkManager[40+23b000] [Thu Oct 26 23:17:23 2017] NetworkManager[4474]: segfault at 8 ip 00479ef7 sp 7ffd73cca230 error 4 in NetworkManager[40+23b000] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1728013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717995] Re: extra domains not removed from resolv.conf when VPN disconnects
I'm experiencing this same issue. A workaround that works for me is to remove my vpn domain from /etc/resolv.conf. The last line of this file looks as follows after a successful VPN connection: search Home myvpndomain where the last term is the domain of my vpn (vpn.bla.com). The workaround is to remove it and leave: search Home then restart the network-manager service and the VPN reconnects. Otherwise I have to restart the computer to be able to connect to the VPN after a successful connection. I mean: after a computer restart, VPN always connects, but if I disconnect I cannot reconnect to the VPN unless I restart the computer or do the workaround. I have a big confusion on how /etc/resolv.conf is managed nowadays in Ubuntu. I have at least three different system processes generating a resolv.conf. systemd-resolved: /run/systemd/resolve/resolv.conf network-manager: /run/NetworkManager/resolv.conf and resolvconf: /run/resolvconf/resolv.conf My actual /etc/resolv.conf is a symbolic link to this last one. At some point I tried to have only network-manager manage /etc/resolv.conf. Everything works fine, but when I connect to VPN it can't resolve any DNS outside of the private network. The resolv.conf generated by systemd-resolved has the same problem as the one generated by resolvconf, when the VPN reconnects the VPN domain is not removed from the "search" line. -- 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/1717995 Title: extra domains not removed from resolv.conf when VPN disconnects Status in systemd package in Ubuntu: In Progress Bug description: I use a VPN (network manager "vpnc" config) to connect to my work network. The gateway is "webvpn.purestorage.com". When I connect, I get "purestorage.com" added to the "search" line in my /etc/resolv.conf (and /run/resolvconf/interface/systemd-resolved) - which makes perfect sense, the VPN passes this info to me and then I can connect to systems within the work network without having to use a FQDN. The bug (which is a regression from older versions of Ubuntu) is that when I lose my connection to the VPN (either because I disconnect explicitly, or because the network goes down or I suspend my laptop), the "purestorage.com" domain is not removed from those "search" lines. And for some reason this prevents me from resolving webvpn.purestorage.com (which prevents me from reconnecting to the VPN). In particular, if I connect and disconnect my VPN, I get: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: resolve call failed: No appropriate name servers or networks for name found If I then edit /etc/resolv.conf by hand to remove all the purestorage.com entries from the search line - in other words, change $ 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 # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org purestorage.com dev.purestorage.com to $ 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 # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search home.digitalvampire.org and change nothing else, then: $ systemd-resolve webvpn.purestorage.com webvpn.purestorage.com: 192.30.189.1 (vpn.purestorage.com) -- Information acquired via protocol DNS in 25.9ms. -- Data is authenticated: no I'm not sure if the bug is in systemd, network manager, or some other package, but I'm happy to try any debugging that is helpful to resolve this (no pun intended). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu10 ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10 Uname: Linux 4.12.0-13-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 11:20:17 2017 InstallationDate: Installed on 2016-09-01 (381 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160901) MachineType: LENOVO 20FRS2FK00 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.12.0-13-generic root=UUID=30d5ada5-835d-4cf7-96cf-3329c0316107 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to artful on 2017-07-26 (53 days ago) dmi.bios.date: 07/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version:
[Touch-packages] [Bug 1577879] Re: File save as dialog doesn't switch to keyed in path anymore when pressing enter
I have tried this functionality in Ubuntu 17.10 with Unity and the original behavior seems to be back. Can anybody confirm if this is still an issue? ** Changed in: gtk Importance: Medium => Undecided ** Changed in: gtk Status: Expired => New ** Changed in: gtk Remote watch: GNOME Bug Tracker #766696 => None ** Changed in: gtk Status: New => Incomplete ** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1577879 Title: File save as dialog doesn't switch to keyed in path anymore when pressing enter Status in GTK+: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: Not sure if this is in Nautilus or a GTK package or something else.. I run Unity as my desktop environment at the moment. With a recent update, the file save dialog presented to me by Firefox appears to have changed. I'm pretty sure it's an OS dialog and not a Firefox specific control, but please feel free to bounce this to whichever package is responsible for the File Save As dialog generated by Firefox 46.0 in Ubuntu now. In the past, when the save dialog came up, I was able to enter a path (absolute or relative) in the filename field: * If it was a directory path that existed, the directory contents would be shown inside the window, allowing me to then specify a name * If it was a directory path that didn't exist, it'd take me to the deepest part of the path that did match * If it was a directory that did exist, and a filename that didn't, it'd save as that filename in that folder The last is still true, but the others aren't anymore.. Say I have structure: home .../folder ../sub2 ../sub3 ... and I last saved into sub3 and I want to save into sub2, if I remove the filename from the name box, and I type ../sub2 and press enter, it doesn't navigate to the folder anymore.. The auto-complete function seems more reliable now, and it knows the folder exists, but the only way to actually show its contents now would be to click through the tree.. This feels like a functionality downgrade. I should be able to type a pathname into the filename area of the dialog, press enter, and have it take me to that particular folder. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: nautilus 1:3.14.2-0ubuntu13 ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5 Uname: Linux 4.2.0-35-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 4 03:29:09 2016 GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'group', 'where', 'mime_type', 'owner', 'permissions', 'date_accessed']" InstallationDate: Installed on 2016-01-21 (103 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1577879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1645687] Re: 50unattended-upgrades.ucf-dist
upgrade from 14.04 to 16.04 did this. I copy file to documents. I removed said file from apt dir. sudo rm... ok, then apt worked with no more N: msg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1645687 Title: 50unattended-upgrades.ucf-dist Status in unattended-upgrades package in Ubuntu: New Bug description: During a refresh procedure of Ubuntu-Mate 16.04 (on 29th November, 2016) the following notice appeared in the first line of the terminal. (Refreshing among others the linux- image-4.4.0-51-generic_4.4.0-51.72_i386.deb package): N: "50unattended-upgrades.ucf-dist" file(s) has/have been left out of consideration in the "/etc/apt/apt.conf.d/ map having invalid file extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1645687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689528] [NEW] package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1688721 *** https://bugs.launchpad.net/bugs/1688721 Public bug reported: hello. When I try to install google chrome on my ubuntu 17 PC, it fail to install. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Tue May 9 03:51:17 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1689528 Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in gconf package in Ubuntu: New Bug description: hello. When I try to install google chrome on my ubuntu 17 PC, it fail to install. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: gconf2-common 3.2.6-3ubuntu7 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Tue May 9 03:51:17 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-09 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: gconf Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1689528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1659339] Re: "libmtp error: Could not send object" when copying a file to MTP folder
I get this when I copy ripped mp3 files from my pc tp my phone. Most files will tranfer correctly, but on average one in five won't. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1659339 Title: "libmtp error: Could not send object" when copying a file to MTP folder Status in Linux Mint: New Status in mtp package in Ubuntu: Confirmed Bug description: Linux Mint 17.2/17.3/18/18.1 (problem arises in all of these). I connect my Android phone over MTP, LM opens the folder (for example "mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono"), then I try to copy a file from my filesystem to the phone. I get a window that says: Error while copying "foo.png".//There was an error copying the file into mtp://[usb:001,005]/Almacenamiento%20del%20tel%C3%A9fono/.//libmtp error: Could not send object info.//Cancel/Skip. I think that the copy operation should proceed and having my file "foo.png" in phone's memory. The problem happens always, indeed the copy never worked for me in any of the LM versions mentioned above, that is, from the very first time I used LM. I can read (copy) files from the phone to the laptop, and I can delete files from the phone. $ lsusb Bus 002 Device 002: ID 13b1:0041 Linksys Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Asus Integrated Webcam Bus 001 Device 005: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo (Debug) Bus 001 Device 002: ID 0458:00f2 KYE Systems Corp. (Mouse Systems) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/linuxmint/+bug/1659339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
I reflashed eventually and did not have sound, so this is clearly a hardware problem. Since my phone was still under warranty, I sent it for repair. So closing this bug as invalid, if anybody has a similar problem please open a new bug with the information of his/her device. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Invalid -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Invalid Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373255] Re: Bluetooth indicator is shown twice in the upper panel
Thanks @dobey, indeed, I don't see this any more, so closing the bug. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: indicator-bluetooth (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1373255 Title: Bluetooth indicator is shown twice in the upper panel Status in One Hundred Papercuts: Invalid Status in indicator-bluetooth package in Ubuntu: Invalid Bug description: Bluetooth indicator is shown two times in the panel. After disabling bluetooth in System -> Settings, there is still one indicator being shown. Should this come from some ubuntu-touch bluetooth package? I have also ubuntu8 installed. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-bluetooth 0.0.6+14.10.20140922-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Sep 24 08:50:17 2014 InstallationDate: Installed on 2013-11-28 (299 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: indicator-bluetooth UpgradeStatus: Upgraded to utopic on 2014-09-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1373255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
pat-mcgowan: I installed a couple of games exactly for what you way, trying to turn the volume on and off to see if I got back the sound, but it didn't work out. I wait a couple of days more and reflash. -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
And here there are the output of "pacmd list-sink-inputs", first while playing. ** Attachment added: "pacmd-while-playing.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+attachment/4802717/+files/pacmd-while-playing.txt -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
And now while not playing. -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
** Attachment added: "pacmd-while-playing-not-playing.txt" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+attachment/4802718/+files/pacmd-while-playing-not-playing.txt -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
** Attachment added: "media-hub.log" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+attachment/4802716/+files/media-hub.log -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
Thanks pat-mcgowan, I attach the two files. "syslog" I truncated to the last lines. I started playing music in youtube to see if any message is logged, before that I took a quick look and I think there were only the usual messages related to starting device and such. I checked and the device does not think it is paired by bluetooth. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+attachment/4802715/+files/syslog -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: Confirmed Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] Re: Ubuntu Touch: No sound on speakers but OK on headset
ubuntu-phablet-stream-volumes.tdb file as it was before removing .config/pulse and restarting ** Attachment added: "ubuntu-phablet-stream-volumes.tdb" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+attachment/4801147/+files/ubuntu-phablet-stream-volumes.tdb -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: New Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654722] [NEW] Ubuntu Touch: No sound on speakers but OK on headset
Public bug reported: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf vivid -- 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/1654722 Title: Ubuntu Touch: No sound on speakers but OK on headset Status in pulseaudio package in Ubuntu: New Bug description: Since a couple of days ago I have lost all sound on the speakers of the phone (no application plays any sound, no ringtones, notifications), but sounds can be heard normally with a headset. Sound configuration looks OK, and restarting does not help. I tried to remove .config/pulse completely and restart, but no progress. I attach the file ubuntu-phablet-stream-volumes.tdb which was there before removing the folder and restarting. BQ E5, OTA 14. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu9.25 Uname: Linux 3.4.67 armv7l AlsaInfo: This script requires lspci. Please install it, and re-run this script. ApportVersion: 2.17.2-0ubuntu1.3touch1 Architecture: armhf AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser' CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sat Jan 7 09:30:00 2017 InstallationDate: Installed on 2016-11-18 (49 days ago) InstallationMedia: Ubuntu 15.04 - armhf (20161118-171123) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1654722/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643148] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
No one, Grazie -- 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/1643148 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: New Bug description: I Don't Know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CupsErrorLog: E [15/Nov/2016:06:58:25 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [19/Nov/2016:08:55:00 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [19/Nov/2016:09:10:24 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Sat Nov 19 09:10:16 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-24 (1213 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer, inc. TravelMate 6292 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=679e7295-5aca-41d8-b107-fddf660e15f3 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=679e7295-5aca-41d8-b107-fddf660e15f3 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: Upgraded to xenial on 2016-07-30 (111 days ago) dmi.bios.date: 03/03/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3601 dmi.board.name: Victoria dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.asset.tag: ACER dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3601:bd03/03/2008:svnAcer,inc.:pnTravelMate6292:pvrNotApplicable:rvnAcer,Inc.:rnVictoria:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: TravelMate 6292 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-08-14T09:49:36.458881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1643148/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643148] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I Don't Know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CupsErrorLog: E [15/Nov/2016:06:58:25 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [19/Nov/2016:08:55:00 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [19/Nov/2016:09:10:24 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Sat Nov 19 09:10:16 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-24 (1213 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer, inc. TravelMate 6292 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=679e7295-5aca-41d8-b107-fddf660e15f3 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=679e7295-5aca-41d8-b107-fddf660e15f3 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: Upgraded to xenial on 2016-07-30 (111 days ago) dmi.bios.date: 03/03/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3601 dmi.board.name: Victoria dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.asset.tag: ACER dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3601:bd03/03/2008:svnAcer,inc.:pnTravelMate6292:pvrNotApplicable:rvnAcer,Inc.:rnVictoria:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: TravelMate 6292 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-08-14T09:49:36.458881 ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check xenial -- 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/1643148 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: New Bug description: I Don't Know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic i686 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: i386 CupsErrorLog: E [15/Nov/2016:06:58:25 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [19/Nov/2016:08:55:00 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. E [19/Nov/2016:09:10:24 +0100] Unknown directive BrowseAddress on line 26 of /etc/cups/cupsd.conf. Date: Sat Nov 19 09:10:16 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-07-24 (1213 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 (20130213) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: Acer, inc. TravelMate 6292 Papersize: a4 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=679e7295-5aca-41d8-b107-fddf660e15f3 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic root=UUID=679e7295-5aca-41d8-b107-fddf660e15f3 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: Upgraded to xenial on 2016-07-30 (111 days ago) dmi.bios.date: 03/03/2008 dmi.bios.vendor: Acer dmi.bios.version: v1.3601 dmi.board.name: Victoria dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.asset.tag: ACER dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1630599] Re: unity8 crashed with SIGSEGV in begin()
** Information type changed from Private to Public -- 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/1630599 Title: unity8 crashed with SIGSEGV in begin() Status in unity8 package in Ubuntu: New Bug description: I got this crash after trying the Unity 8 session and loggin out. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: unity8 8.14+16.10.20160922-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Wed Oct 5 16:02:06 2016 ExecutablePath: /usr/bin/unity8 InstallationDate: Installed on 2015-10-17 (353 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: unity8 --mode=full-shell Signal: 11 SourcePackage: unity8 StacktraceTop: qtmir::ApplicationManager::findApplicationWithPid(int) const () from /usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so qtmir::SessionManager::onSessionStarting(std::shared_ptr const&) () from /usr/lib/x86_64-linux-gnu/qt5/qml/Unity/Application/libunityapplicationplugin.so QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QCoreApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 Title: unity8 crashed with SIGSEGV in qtmir::ApplicationManager::findApplicationWithPid() UpgradeStatus: Upgraded to yakkety on 2016-09-01 (34 days ago) UserGroups: adm cdrom dip lpadmin mail plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1630599/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1625437] Re: systemd-resolved crashed with SIGSEGV in sd_event_source_unref()
** Information type changed from Private to Public -- 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/1625437 Title: systemd-resolved crashed with SIGSEGV in sd_event_source_unref() Status in systemd package in Ubuntu: New Bug description: I'm getting this crash when starting the computer. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: systemd 231-6 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Sat Sep 17 20:21:42 2016 ExecutablePath: /lib/systemd/systemd-resolved InstallationDate: Installed on 2013-11-28 (1026 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Dell Inc. Latitude E6530 ProcCmdline: /lib/systemd/systemd-resolved ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=409b2104-0062-403c-8b6b-f07948051f69 ro quiet splash vt.handoff=7 Signal: 11 SourcePackage: systemd StacktraceTop: sd_event_source_unref () from /lib/systemd/libsystemd-shared-231.so ?? () ?? () ?? () ?? () from /lib/systemd/libsystemd-shared-231.so Title: systemd-resolved crashed with SIGSEGV in sd_event_source_unref() UpgradeStatus: Upgraded to yakkety on 2016-08-31 (19 days ago) UserGroups: dmi.bios.date: 08/27/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA13:bd08/27/2013:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1618845] [NEW] signon-ui problem at login
Public bug reported: After entering my user session, a blank windos pops up produced by signon-ui. It gets reopened three times after closing it, and then signon-ui crashes. The same window is opened when System settings -> Online Accounts is opened. It is also blank. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: signon-ui 0.17+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 31 13:30:49 2016 InstallationDate: Installed on 2013-11-28 (1006 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: signon-ui UpgradeStatus: Upgraded to yakkety on 2016-08-31 (0 days ago) ** Affects: signon-ui (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 signon-ui in Ubuntu. https://bugs.launchpad.net/bugs/1618845 Title: signon-ui problem at login Status in signon-ui package in Ubuntu: New Bug description: After entering my user session, a blank windos pops up produced by signon-ui. It gets reopened three times after closing it, and then signon-ui crashes. The same window is opened when System settings -> Online Accounts is opened. It is also blank. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: signon-ui 0.17+16.04.20160406-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 31 13:30:49 2016 InstallationDate: Installed on 2013-11-28 (1006 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: signon-ui UpgradeStatus: Upgraded to yakkety on 2016-08-31 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon-ui/+bug/1618845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1582494] [NEW] package openssh-server 1:6.6p1-2ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Public bug reported: I updated xubuntu with systemctl and tried to reinstall ssh and dependencies but it will not install. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openssh-server 1:6.6p1-2ubuntu2.7 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Mon May 16 22:40:47 2016 DuplicateSignature: package:openssh-server:1:6.6p1-2ubuntu2.7:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-04-28 (18 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.13 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:6.6p1-2ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1582494 Title: package openssh-server 1:6.6p1-2ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in openssh package in Ubuntu: New Bug description: I updated xubuntu with systemctl and tried to reinstall ssh and dependencies but it will not install. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openssh-server 1:6.6p1-2ubuntu2.7 ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19 Uname: Linux 3.19.0-59-generic i686 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: i386 Date: Mon May 16 22:40:47 2016 DuplicateSignature: package:openssh-server:1:6.6p1-2ubuntu2.7:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2016-04-28 (18 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) RelatedPackageVersions: dpkg 1.17.5ubuntu5.6 apt 1.0.1ubuntu2.13 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:6.6p1-2ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1582494/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573333] [NEW] package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv
Public bug reported: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 09:31:25 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2012-07-07 (1384 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/157 Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv Status in systemd package in Ubuntu: New Bug description: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre- dependency problem - not installing systemd-sysv ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd-sysv 229-4ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 21 09:31:25 2016 ErrorMessage: pre-dependency problem - not installing systemd-sysv InstallationDate: Installed on 2012-07-07 (1384 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: systemd Title: package systemd-sysv 229-4ubuntu4 failed to install/upgrade: pre-dependency problem - not installing systemd-sysv UpgradeStatus: Upgraded to xenial on 2016-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571351] [NEW] package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0
Public bug reported: desconozco el error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 17 12:13:18 2016 ErrorMessage: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-06-25 (296 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-04-15 (1 days ago) ** Affects: libjpeg8-empty (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg8-empty in Ubuntu. https://bugs.launchpad.net/bugs/1571351 Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 Status in libjpeg8-empty package in Ubuntu: New Bug description: desconozco el error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-progs 8c-2ubuntu8 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 17 12:13:18 2016 ErrorMessage: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 InstallationDate: Installed on 2015-06-25 (296 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: libjpeg8-empty Title: package libjpeg-progs 8c-2ubuntu8 failed to install/upgrade: intentando sobreescribir `/usr/bin/rdjpgcom', que está también en el paquete libjpeg-turbo-progs 1.3.0-0ubuntu2 UpgradeStatus: Upgraded to xenial on 2016-04-15 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg8-empty/+bug/1571351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
