[Touch-packages] [Bug 1813122] [NEW] "ubuntu-bug linux" command on PowerPC will ask for authentication
Public bug reported: On Bionic, when reporting bug with "ubuntu-bug linux" command in a terminal, you will be asked to enter password on a PowerPC: $ ubuntu-bug linux *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. tar: Removing leading `/' from member names AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: But with other arch like AMD64, you won't be asked for the authentication. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el Date: Thu Jan 24 07:07:36 2019 PackageArchitecture: all ProcLoadAvg: 882.90 268.29 93.65 1281/2696 24907 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (User Name 7.3.0-16ubuntu3)) #46-User Name SMP Thu Dec 6 14:43:28 UTC 2018 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_smt: SMT=4 ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic ppc64el uec-images -- 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/1813122 Title: "ubuntu-bug linux" command on PowerPC will ask for authentication Status in apport package in Ubuntu: New Bug description: On Bionic, when reporting bug with "ubuntu-bug linux" command in a terminal, you will be asked to enter password on a PowerPC: $ ubuntu-bug linux *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. tar: Removing leading `/' from member names AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: But with other arch like AMD64, you won't be asked for the authentication. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apport 2.20.9-0ubuntu7.5 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.5 Architecture: ppc64el Date: Thu Jan 24 07:07:36 2019 PackageArchitecture: all ProcLoadAvg: 882.90 268.29 93.65 1281/2696 24907 ProcLocks: 1: POSIX ADVISORY WRITE 3876 00:17:569 0 EOF 2: FLOCK ADVISORY WRITE 3556 00:17:497 0 EOF 3: FLOCK ADVISORY WRITE 4090 00:17:596 0 EOF 4: POSIX ADVISORY WRITE 3955 00:17:571 0 EOF 5: POSIX ADVISORY WRITE 1823 00:17:348 0 EOF ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.15.0-43-generic (buildd@bos02-ppc64el-020) (gcc version 7.3.0 (User Name 7.3.0-16ubuntu3)) #46-User Name SMP Thu Dec 6 14:43:28 UTC 2018 SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 40 cpu_coreson: Number of cores online = 40 cpu_smt: SMT=4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1813122/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib
>>> So for mime types to distinguish, "file" needs to grow reporting of
the INTERP presence.
Distinguish between shared libraries and PIC executables based on INTERP
ELF header is not always correct. Consider following 2 exceptions:
GLIBC main library libc-2.24.so
This shared object has an INTERP header, which is /lib64/ld-linux-x86-64.so.2
in my system. However we usually considering it a shared library, not an
executable.
GLIBC dynamic linker ld-2.24.so
This shared object doesn't have INTERP header because this object itself is an
interpreter. It should be considered as an executable since it is useful to
load and run GLIBC linked dynamic executables.
This indicates a clear boundary between shared libraries and PIC
executables just does not exist.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1747711
Title:
file mis-identifies modern executables as application/x-sharedlib
Status in file package in Ubuntu:
Confirmed
Bug description:
file doesn't recognize modern PIE (Position Independent Executable)
x86 executables as such, reporting them as “application/x-sharedlib”.
Consequently, only non-PIE executables can be opened in graphical file
managers such as nautilus. This may cause a minor (?) security risk if
a commonly-published workaround is attempted.
Expected behaviour:
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo foo.c
$ file foo
foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0,
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
$ file --mime-type foo
foo: application/x-executable
Actual behaviour:
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo foo.c
$ file foo
foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0,
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
$ file --mime-type foo
foo: application/x-sharedlib
Workaround (unsafe?):
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo-nopie foo.c -no-pie
$ file foo-nopie
foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
$ file --mime-type foo-nopie
foo-nopie: application/x-executable
gcc now defaults to building with PIE enabled for security reasons.
Also affects: nautilus (and likely other graphical file managers like
those on Lubuntu) - because nautilus uses mime-type to determine if a
file is executable, double-click to run a program no longer works.
Also noted on: Gnome Bugs -
https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
became the default build option.
This may be an upstream issue. This may not affect architectures
outside x86.*
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: file 1:5.32-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Feb 6 11:21:20 2018
InstallationDate: Installed on 2017-05-11 (270 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: file
UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1747711/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1747711] Re: file mis-identifies modern executables as application/x-sharedlib
>>> Yes, this is very much a bug. While ELF position independent
executables are ELF shared objects, they weren't being recognized as
executables by desktop launchers. So they wouldn't run.
So those launchers should accept shared objects
(application/x-sharedlib) as executables from now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to file in Ubuntu.
https://bugs.launchpad.net/bugs/1747711
Title:
file mis-identifies modern executables as application/x-sharedlib
Status in file package in Ubuntu:
Confirmed
Bug description:
file doesn't recognize modern PIE (Position Independent Executable)
x86 executables as such, reporting them as “application/x-sharedlib”.
Consequently, only non-PIE executables can be opened in graphical file
managers such as nautilus. This may cause a minor (?) security risk if
a commonly-published workaround is attempted.
Expected behaviour:
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo foo.c
$ file foo
foo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0,
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
$ file --mime-type foo
foo: application/x-executable
Actual behaviour:
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo foo.c
$ file foo
foo: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically
linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0,
BuildID[sha1]=6e7749f995a89a53f74ec29d3c16fcf3f56be90f, not stripped
$ file --mime-type foo
foo: application/x-sharedlib
Workaround (unsafe?):
$ echo "int main() { return 0; }" > foo.c
$ gcc -o foo-nopie foo.c -no-pie
$ file foo-nopie
foo-nopie: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux
3.2.0, BuildID[sha1]=3eb8c581f43c19997e3c828f5a9730dbdc794470, not stripped
$ file --mime-type foo-nopie
foo-nopie: application/x-executable
gcc now defaults to building with PIE enabled for security reasons.
Also affects: nautilus (and likely other graphical file managers like
those on Lubuntu) - because nautilus uses mime-type to determine if a
file is executable, double-click to run a program no longer works.
Also noted on: Gnome Bugs -
https://bugzilla.gnome.org/show_bug.cgi?id=737849 (2014) - before PIE
became the default build option.
This may be an upstream issue. This may not affect architectures
outside x86.*
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: file 1:5.32-1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Feb 6 11:21:20 2018
InstallationDate: Installed on 2017-05-11 (270 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: file
UpgradeStatus: Upgraded to artful on 2017-10-21 (108 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1747711/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813112] Re: avahi-discover failed to display selected service details with UnicodeDecodeError
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1813112 Title: avahi-discover failed to display selected service details with UnicodeDecodeError Status in avahi package in Ubuntu: New Bug description: ## Bug reproduce instruction (As this is a Unicode decode issue it might not be reproducible in all network environments) 1. Launch avahi-discover 2. Select certain service ## Expected behavior The service details properly rendered on the bottom pane ## Current behavior The service details remain "No service currently selected" with the following error traceback: ``` Found service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0. Service data for service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0: Host Buo-ren-TS453A.local (192.168.1.10), port 8080, TXT data: ['accessType=http,accessPort=8080,model=TS-X53II,displayModel=TS-453A,fwVer=4.3.4,fwBuildNum=20180830,serialNum=Q169I13903,myCloudNASName=LinBuoRenNAS,myCloudNASDomain=myqnapcloud.com,webAdmPort=0,webAdmSslPort=0,webPort=0,webSslPort=0'] Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/bin/avahi-discover", line 113, in service_resolved self.update_label(interface, protocol, name, stype, domain, host, aprotocol, address, port, avahi.txt_array_to_string_array(txt)) File "/usr/bin/avahi-discover", line 246, in update_label infos = infos % (stype, name, domain, self.siocgifname(interface), self.protoname(protocol), host, address, port, txts.strip()) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 6: ordinal not in range(128) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1813112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813112] [NEW] avahi-discover failed to display selected service details with UnicodeDecodeError
Public bug reported: ## Bug reproduce instruction (As this is a Unicode decode issue it might not be reproducible in all network environments) 1. Launch avahi-discover 2. Select certain service ## Expected behavior The service details properly rendered on the bottom pane ## Current behavior The service details remain "No service currently selected" with the following error traceback: ``` Found service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0. Service data for service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0: Host Buo-ren-TS453A.local (192.168.1.10), port 8080, TXT data: ['accessType=http,accessPort=8080,model=TS-X53II,displayModel=TS-453A,fwVer=4.3.4,fwBuildNum=20180830,serialNum=Q169I13903,myCloudNASName=LinBuoRenNAS,myCloudNASDomain=myqnapcloud.com,webAdmPort=0,webAdmSslPort=0,webPort=0,webSslPort=0'] Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/bin/avahi-discover", line 113, in service_resolved self.update_label(interface, protocol, name, stype, domain, host, aprotocol, address, port, avahi.txt_array_to_string_array(txt)) File "/usr/bin/avahi-discover", line 246, in update_label infos = infos % (stype, name, domain, self.siocgifname(interface), self.protoname(protocol), host, address, port, txts.strip()) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 6: ordinal not in range(128) ``` ** Affects: avahi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1813112 Title: avahi-discover failed to display selected service details with UnicodeDecodeError Status in avahi package in Ubuntu: New Bug description: ## Bug reproduce instruction (As this is a Unicode decode issue it might not be reproducible in all network environments) 1. Launch avahi-discover 2. Select certain service ## Expected behavior The service details properly rendered on the bottom pane ## Current behavior The service details remain "No service currently selected" with the following error traceback: ``` Found service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0. Service data for service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0: Host Buo-ren-TS453A.local (192.168.1.10), port 8080, TXT data: ['accessType=http,accessPort=8080,model=TS-X53II,displayModel=TS-453A,fwVer=4.3.4,fwBuildNum=20180830,serialNum=Q169I13903,myCloudNASName=LinBuoRenNAS,myCloudNASDomain=myqnapcloud.com,webAdmPort=0,webAdmSslPort=0,webPort=0,webSslPort=0'] Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/bin/avahi-discover", line 113, in service_resolved self.update_label(interface, protocol, name, stype, domain, host, aprotocol, address, port, avahi.txt_array_to_string_array(txt)) File "/usr/bin/avahi-discover", line 246, in update_label infos = infos % (stype, name, domain, self.siocgifname(interface), self.protoname(protocol), host, address, port, txts.strip()) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 6: ordinal not in range(128) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1813112/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813103] Re: Xorg crash of a sort
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1769383, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1769383 Ubuntu dock/launcher is shown on the lock screen -- 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/1813103 Title: Xorg crash of a sort Status in xorg package in Ubuntu: New Bug description: Problem started after last upgrade. Usually happens when I attempt to end the screen saver and start processing again. I see a solid screen with icon bar on the left and the power off button on the upper right but nothing else. The mouse still appears and works but nothing happens on the screen if I click on an application on the left. The power off button works and shuts down the PC. when I reboot everything picks up where I left off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 22:11:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid: /apps/compiz-1/plugins/grid/screen0: /apps/compiz-1/plugins/grid/screen0/options: top_edge_action = 0 GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2713] InstallationDate: Installed on 2018-09-07 (138 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=56cc0abb-f0c5-41da-9704-c934188702fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786391] Re: libasan0 : AddressSanitizer CHECK failed
er, libasan0 Version: 4.8.5-4ubuntu9 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1786391 Title: libasan0 : AddressSanitizer CHECK failed Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gcc-4.8 UpgradeStatus: Upgraded to bionic on 2018-04-27 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1786391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385013] Re: proper fix for apparmor mediation of lower (encrypted) filesystem
https://www.ambeingeneric.us -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1385013 Title: proper fix for apparmor mediation of lower (encrypted) filesystem Status in apparmor package in Ubuntu: Confirmed Status in ecryptfs-utils package in Ubuntu: Confirmed Bug description: This is the proper fix for LP: #359338 which is needed for user data encryption. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1385013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786391] Re: libasan0 : AddressSanitizer CHECK failed
Still a problem in Ubuntu 18.10, mp3gain version 1.5.2-r2-6 ii mp3gain1.5.2-r2-6 amd64Lossless mp3 normalizer with stat moses@jolyne:~$ mp3gain --help ==16547== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1786391 Title: libasan0 : AddressSanitizer CHECK failed Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gcc-4.8 UpgradeStatus: Upgraded to bionic on 2018-04-27 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1786391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package wget - 1.20.1-1ubuntu3 --- wget (1.20.1-1ubuntu3) disco; urgency=medium * Revert switching to pcre3 since pcre2 is in main (LP: #1792544) -- Jeremy Bicha Wed, 23 Jan 2019 11:56:34 -0500 ** Changed in: wget (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1719579] Comment bridged from LTC Bugzilla
--- Comment From balamuruh...@in.ibm.com 2019-01-23 23:48 EDT--- (In reply to comment #68) > TBH - I haven't taken the former comment as a call for further action. > It was more of a summary how docs and output could be better. > > Let me answer: > > 1. document that --bypass-cache would help > > Yeah it might be nice, but then it is just such a general thing. > It only affects apparmor users (not all libvirt users). > It only affects /tmp wi > I wonder how such a hint might look like. > Checking the doc there is a Note on disk corruption for virsh restore - > maybe there as another Note entry. > But I'm still not all in for this. Okay, fine. > > 2. on older releases "error out or warn in Libvirt when performing save in > denial paths" > > It is not really possible to predetect and differentiate if such a denial > was the reason. > Looking into the future I think we might use per-guest overrides. > > I was thinking on that more, the fact that all other but /tmp (for the > explicit deny) just work, like: > $ virsh save xenial-testshutdown-0 /var/anythingbuttmp.state > $ virsh restore /var/anythingbuttmp.state > That annoys me a lot. > > I'd suggest otherwise, we keep the past as it is without modifying man pages > or anything like it (after all it is no regression I can SRU and a very > special case choosing /tmp only). > But I want to make it better thinking forward. > I thought about it again and again, and revisited the old bug that added > those deny rules. > I think it is time to take them out in the next release. Agree with you on this. > > That would mean it would generally work, and even if there is a deny it > would at least be in the log. > See also: > - https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1403648/comments/6 > - https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1403648/comments/12 > > I think the old assumptions don't hold true. > So for the current and stable-releases we keep it as is, to not regress > anyone (with too much logs). > But forward I'd drop the deny rules and then all of this (and similar things > where users WANT e.g. images in /tmp) would work. ACK > > Part of it would be to check (way more modern and recent) openstack that it > no more has those issues and if it has as part of the fix look for something > better e.g. adapt how openstack sets the ceph config to no more trigger /tmp > /tmp/var access. > > There are also rules like owner /tmp/pulse-*/ rw, in the meantime which get > trumped by the deny. > TL;DR - taking out the deny and making the save/restore case of this bug no > more a special case would be much better IMHO. > > If you are ok with that I'd create a new bug to: > 1. take out the deny rules to /tmp early in Ubuntu 18.10 Yes, I am okay on it. > 2. do an analysis with recent openstack+ceph if they still trigger access > there well, I am not working on openstack and ceph. so could not comment on it. > > So are you ok with that approach? :+1: for 1 > > P.S. If you really really (...really*) want/need a man page entry for this > special case we could work something out, but I think that would not qualify > as an SRU [1] so thinking forward is much better anyway. As you have mentioned earlier, I think it is not necessary. > > [1]: https://wiki.ubuntu.com/StableReleaseUpdates Thank you for your support. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1719579 Title: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save Status in The Ubuntu-power-systems project: Fix Released Status in apparmor package in Ubuntu: Invalid Status in libvirt package in Ubuntu: Fix Released Bug description: == Comment: #1 - SEETEENA THOUFEEK - 2017-01-17 00:09:16 == Bala, Please mail me the machine information. == Comment: #3 - SEETEENA THOUFEEK - 2017-01-17 02:14:06 == 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on '/var/tmp/bala' 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on '/var/tmp/bala' to '0:0' 2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : failed to restore save state label on /var/tmp/bala 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala) 2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca535c0 2017-01-16 12:09:37.707+: 7024:
[Touch-packages] [Bug 1813103] [NEW] Xorg crash of a sort
Public bug reported: Problem started after last upgrade. Usually happens when I attempt to end the screen saver and start processing again. I see a solid screen with icon bar on the left and the power off button on the upper right but nothing else. The mouse still appears and works but nothing happens on the screen if I click on an application on the left. The power off button works and shuts down the PC. when I reboot everything picks up where I left off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 22:11:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid: /apps/compiz-1/plugins/grid/screen0: /apps/compiz-1/plugins/grid/screen0/options: top_edge_action = 0 GraphicsCard: NVIDIA Corporation GK208 [GeForce GT 710B] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GK208B [GeForce GT 710] [3842:2713] InstallationDate: Installed on 2018-09-07 (138 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=56cc0abb-f0c5-41da-9704-c934188702fd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A58M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF1:bd03/24/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A58M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash ubuntu ** Attachment added: "dmesg" https://bugs.launchpad.net/bugs/1813103/+attachment/5231879/+files/kernel_log.txt -- 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/1813103 Title: Xorg crash of a sort Status in xorg package in Ubuntu: New Bug description: Problem started after last upgrade. Usually happens when I attempt to end the screen saver and start processing again. I see a solid screen with icon bar on the left and the power off button on the upper right but nothing else. The mouse still appears and works but nothing happens on the screen if I click on an application on the left. The power off button works and shuts down the PC. when I reboot everything picks up where I left off. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 23 22:11:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GconfCompiz: /apps/compiz-1/plugins: /apps/compiz-1/plugins/grid:
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Also affects: ubuntu-core-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] Re: ssh-agent fails for ssh-add -c: agent refused operation
Sorry, the combination of ssh-agent and "log out and log back in" made me immediately think of bug 1789523. ** Package changed: gnome-session (Ubuntu) => openssh (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-agent fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813076] Re: goa crashes when trying to authenticate against google & DUO
Wait a second - is goa based on Safari code? Is that why it's being shut-out from DUO? And, I'm not suggesting that anyone lie - I suspect that DUO is misreading goa as Safari. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1813076 Title: goa crashes when trying to authenticate against google & DUO Status in gnome-online-accounts package in Ubuntu: New Bug description: My google eMAIL account is managed by my organisation. They recently required everyone to validate their sign-ons (sign-ins) via a central authentication server (CAS) using the 2FA from DUO. When attempting to connect using goa, I am now re-directed to my organisation's CAS and when the DUO login page refreshes, it states that login could not proceed because I am using a SAFARI browser that is more than one year out of date. Of course, I'm not using SAFARI, but rather goa. Is there a way to deed the proper header (a more recent version of SAFARI in goa) to be able to complete 2FA with DUO? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-online-accounts 3.28.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 23 15:20:45 2019 InstallationDate: Installed on 2019-01-15 (8 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1813076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] [NEW] ssh-agent fails for ssh-add -c: agent refused operation
You have been subscribed to a public bug: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt-get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh- add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- ssh-agent fails for ssh-add -c: agent refused operation https://bugs.launchpad.net/bugs/1812247 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786391] Re: libasan0 : AddressSanitizer CHECK failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-4.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1786391 Title: libasan0 : AddressSanitizer CHECK failed Status in gcc-4.8 package in Ubuntu: Confirmed Bug description: Code that worked in Ubuntu 16.04 LTS does not work in Ubuntu 18.04.1. (I tried to report this bug for package "libasan0" but bugs.launchpad.net sends me hto gcc-4.8) $ mp3gain --help ==8893== AddressSanitizer CHECK failed: ../../../../src/libsanitizer/asan/asan_rtl.cc:411 "((!asan_init_is_running && "ASan init calls itself!")) != (0)" (0x0, 0x0) #0 0x7f287806d0cd (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x120cd) #1 0x7f2878073eb3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x18eb3) #2 0x7f287806e088 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x13088) #3 0x7f2878063fb9 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x8fb9) #4 0x7f28780701f2 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x151f2) #5 0x7f287b001aa7 (/lib/x86_64-linux-gnu/ld-2.27.so+0x17aa7) #6 0x7f287aff53eb (/lib/x86_64-linux-gnu/ld-2.27.so+0xb3eb) #7 0x7f2877a32da5 (/lib/x86_64-linux-gnu/libc-2.27.so+0x166da5) #8 0x7f28774aa0e3 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x10e3) #9 0x7f2877a332de (/lib/x86_64-linux-gnu/libc-2.27.so+0x1672de) #10 0x7f2877a3336e (/lib/x86_64-linux-gnu/libc-2.27.so+0x16736e) #11 0x7f28774aa734 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1734) #12 0x7f28774aa165 (/lib/x86_64-linux-gnu/libdl-2.27.so+0x1165) #13 0x7f2878078b3b (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x1db3b) #14 0x7f287806bff3 (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x10ff3) #15 0x7f287806da3a (/usr/lib/x86_64-linux-gnu/libasan.so.0.0.0+0x12a3a) #16 0x7f287affa805 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10805) #17 0x7f287afeb0c9 (/lib/x86_64-linux-gnu/ld-2.27.so+0x10c9) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libasan0 4.8.5-4ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Aug 9 23:04:04 2018 Dependencies: gcc-4.8-base 4.8.5-4ubuntu8 gcc-8-base 8-20180414-1ubuntu2 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 InstallationDate: Installed on 2016-06-05 (795 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: gcc-4.8 UpgradeStatus: Upgraded to bionic on 2018-04-27 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1786391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813076] Re: goa crashes when trying to authenticate against google & DUO
Excellent question. If we lie about the version of Safari it might cause other tools to emit HTML etc that it can't parse. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1813076 Title: goa crashes when trying to authenticate against google & DUO Status in gnome-online-accounts package in Ubuntu: New Bug description: My google eMAIL account is managed by my organisation. They recently required everyone to validate their sign-ons (sign-ins) via a central authentication server (CAS) using the 2FA from DUO. When attempting to connect using goa, I am now re-directed to my organisation's CAS and when the DUO login page refreshes, it states that login could not proceed because I am using a SAFARI browser that is more than one year out of date. Of course, I'm not using SAFARI, but rather goa. Is there a way to deed the proper header (a more recent version of SAFARI in goa) to be able to complete 2FA with DUO? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-online-accounts 3.28.0-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Wed Jan 23 15:20:45 2019 InstallationDate: Installed on 2019-01-15 (8 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1813076/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
Still happening for me on 18.04 LTS... -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
Also, I notice you seem to be using this Bluetooth adapter: Bus 003 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Unfortunately we do find that brand (Cambridge Silicon Radio) of Bluetooth adapter to be unreliable and buggy. So please also try a different Bluetooth adapter. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812984] Re: package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1812984 Title: package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in ca-certificates package in Ubuntu: New Status in debconf package in Ubuntu: New Bug description: I have no idea about the error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ca-certificates 20170717~14.04.2 ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Jan 23 15:59:29 2019 DuplicateSignature: package:ca-certificates:20170717~14.04.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-09-01 (143 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.19 SourcePackage: ca-certificates Title: package ca-certificates 20170717~14.04.2 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/ca-certificates/+bug/1812984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
Can you please run this command and send us the output? dpkg -s pulseaudio ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812918] Re: Bluetooth Sound disjoined 18.04
Wow, OK. That is indeed disjoint/disjoined. ** Summary changed: - Bluetooth Sound disjoined 18.04 + Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 ** Changed in: bluez (Ubuntu) Status: Incomplete => New ** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 Status in bluez package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813097] Re: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package li
** Tags removed: need-duplicate-check -- 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/1813097 Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: New Bug description: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:36ec] InstallationDate: Installed on 2014-12-08 (1507 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Supermicro X10SRA-F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=7439bd5c-2c10-4e9d-8ccc-144a158d3318 ro radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 audio=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: X10SRA-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd01/28/2016:svnSupermicro:pnX10SRA-F:pvr0123456789:rvnSupermicro:rnX10SRA-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1813097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813097] [NEW] package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package
Public bug reported: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK208B [GeForce GT 710] [1458:36ec] InstallationDate: Installed on 2014-12-08 (1507 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) MachineType: Supermicro X10SRA-F ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=UUID=7439bd5c-2c10-4e9d-8ccc-144a158d3318 ro radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 audio=1 nomdmonddf nomdmonisw nomdmonddf nomdmonisw Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mesa Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0 dmi.board.asset.tag: Default string dmi.board.name: X10SRA-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0:bd01/28/2016:svnSupermicro:pnX10SRA-F:pvr0123456789:rvnSupermicro:rnX10SRA-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA-F dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic package-conflict ubuntu -- 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/1813097 Title: package libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 failed to install/upgrade: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 Status in mesa package in Ubuntu: New Bug description: keeps crashing on my system. Using cinnamon ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jan 23 17:06:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DuplicateSignature: package:libgl1-mesa-dri:18.0.0~rc4-1ubuntu3 Unpacking libgl1-mesa-dri:amd64 (18.0.5-0ubuntu0~18.04.1) over (18.0.0~rc4-1ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-B5P550/50-libgl1-mesa-dri_18.0.5-0ubuntu0~18.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64 ErrorMessage: trying to overwrite shared '/etc/drirc', which is different from other instances of package libgl1-mesa-dri:amd64
[Touch-packages] [Bug 1560286] Re: Evince displays pdf file fine, but prints colors inverted
This fixed the bug for me.
I did not enable -proposed, just downloaded and upgraded this packages:
{{{
$ dpkg -l \*cairo\* | grep ^ii | grep 1.15.10
ii libcairo-gobject2:amd641.15.10-2ubuntu0.1 amd64Cairo 2D
vector graphics library (GObject library)
ii libcairo-script-interpreter2:amd64 1.15.10-2ubuntu0.1 amd64Cairo 2D
vector graphics library (script interpreter)
ii libcairo2:amd641.15.10-2ubuntu0.1 amd64Cairo 2D
vector graphics library
ii libcairo2-dev:amd641.15.10-2ubuntu0.1 amd64
Development files for the Cairo 2D graphics library
}}}
Thanks!
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1560286
Title:
Evince displays pdf file fine, but prints colors inverted
Status in cairo package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
Fix Committed
Status in cairo source package in Cosmic:
Fix Committed
Bug description:
* Impact
In some files images are printed with inverted colors
* Test case
open
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
in evince, click on the print preview, the colors should be right
* Regression potential
it's a change in the code dealing with specific adobe file, test opening the
example in different document viewer and try with some other files (the bug has
several example), they should display the correct image/colors
I have several pdf files that when opened by evince, they appear to be fine
until I try to print them. When I do, they print with the colors inverted (the
printout looks like a photograph negative). This color inversion also occurs
when viewed in the print preview screen. If I click on File > Properties, I
get some information...
Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
Creator : Adobe Acrobat 15.10
...
Format : PDF-1.6
...
I am running ubuntu 14.04 LTS
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: evince 3.10.3-0ubuntu10.2
ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
Uname: Linux 3.13.0-83-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 21 21:01:45 2016
ExecutablePath: /usr/bin/evince
InstallationDate: Installed on 2012-07-24 (1336 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64
(20120425)
ProcEnviron:
LANGUAGE=en_US
PATH=(custom, user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)
Or is there anything going to happen wrt to https/TLS? I, personally, are not convinced of doing this... In this specific case, and rogue mirror could have still exploited the hole, and I'd assume there is nothing done to check the trustworthiness of mirror operators (there's no real way to do so). Also, the X.509 trust model is inherently broken. 150 root CAs alone in the mozilla bundle (many of them which cannot be trusted per se by any sane person) and even more sub CAs... all of which can issue literally any certificate. Using TLS would IMO only help (a tiny bit) if Debian (respectively the derivates) would operate their own CA (and only accept that for services they offer, like mirrors, BTS, gitlab, etc.). -- 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/1812353 Title: content injection in http method (CVE-2019-3462) Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: apt, starting with version 0.8.15, decodes target URLs of redirects, but does not check them for newlines, allowing MiTM attackers (or repository mirrors) to inject arbitrary headers into the result returned to the main process. If the URL embeds hashes of the supposed file, it can thus be used to disable any validation of the downloaded file, as the fake hashes will be prepended in front of the right hashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812353] Re: content injection in http method (CVE-2019-3462)
Hmm that's pretty bad then (which is not to be read as blaming you or anyone else here). Are there going to be any… "consequences"? I mean trying to find out whether systems have been compromised is probably impossible... an attacker could have used this long ago to basically do everything, from silently taking over end user systems to secretly injecting code in development repos. Sure one can argue that this might have been noticed - but it also might have been not. But is there a chance to e.g. get full audits of apt done by security experts? I'd assume that aptitude was also fully affected by this, right? -- 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/1812353 Title: content injection in http method (CVE-2019-3462) Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Status in apt source package in Cosmic: Fix Released Status in apt source package in Disco: Fix Released Bug description: apt, starting with version 0.8.15, decodes target URLs of redirects, but does not check them for newlines, allowing MiTM attackers (or repository mirrors) to inject arbitrary headers into the result returned to the main process. If the URL embeds hashes of the supposed file, it can thus be used to disable any validation of the downloaded file, as the fake hashes will be prepended in front of the right hashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1812353/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account
Yes, that wouldn't be a problem. Steps: 1 - Open the GNOME Control Center (Ubuntu Settings, or Configurations); 2 - Select "Network" on the left sidebar; 3 - Press the small cog-wheel (Network Configurations); 4 - Select the IPv6 tab; 5 - On IPv6 Method, select disabled (on my system, it is on Automatic); After that, GOA doesn't load the login screens that I've detailed on earlier comments. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1805426 Title: Not able to log in into Google Account, aswell as Microsoft account Status in gnome-initial-setup package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: New Bug description: After the first boot up of Ubuntu 18.10, it invites me to log-in into several accounts, including Google and Microsoft accounts. After I log-in into Ubuntu One, my next step is to log in my Google Account, but the log-in page never loads, and when it does (after a couple of minutes), and I insert my log in credentials, it fails the log-in process, all of this happens with the Microsoft account too. The Ubuntu One account logs-in without a hitch, but the rest does not. 1) Description: Ubuntu 18.10 Release: 18.10 2) gnome-initial-setup: Instalado: 3.30.0-1ubuntu3 Candidato: 3.30.0-1ubuntu3.1 Tabela de versão: 3.30.0-1ubuntu3.1 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.0-1ubuntu3 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-initial-setup 3.30.0-1ubuntu3 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 27 11:12:31 2018 ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup InstallationDate: Installed on 2018-11-27 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-initial-setup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1805426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
libslang2-modules is in universe although it's built from the slang2 source. I guess that means we can mark it invalid here? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
quagga was another false Build-Depends so I filed a Debian bug requesting they drop the pcre3 Build-Depends. ** Changed in: quagga (Ubuntu) Status: Incomplete => Invalid ** Description changed: + https://people.canonical.com/~ubuntu- + archive/transitions/html/pcre2-main.html + demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. - aide - apache2 - apr-util - clamav - exim4 - freeradius - git - glib2.0 - grep - haproxy - libpam-mount - libselinux - nginx - nmap - php7.2 - postfix - python-pyscss - quagga - rasqal - slang2 - sssd - wget - zsh - -- - - For clarification: pcre2 is actually newer than pcre3. pcre3 is just - poorly named (according to jbicha). + For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package clamav - 0.100.2+dfsg-2ubuntu1 --- clamav (0.100.2+dfsg-2ubuntu1) disco; urgency=medium * Sync with Debian. Remaining change: - clamav-daemon may fail to start due to options removed in new version and manually edited configuration file. (LP: #1783632) + debian/patches/Deprecate-unused-options-instead-of-removing-it.patch: add patch from Debian stretch to simply warn about removed options. * Dropped change: - Build-Depend on pcre3-dev (pcre2 is now in Ubuntu main) (LP: #1792544) clamav (0.100.2+dfsg-2) unstable; urgency=medium * Increase clamd socket command read timeout to 30 seconds (Closes: #915098) clamav (0.100.2+dfsg-1) unstable; urgency=medium * Import new upstream - Bump symbol version due to new version. - CVE-2018-15378 (Closes: #910430). * add NEWS.md and README.md from upstream * Fix infinite loop in dpkg-reconfigure, Patch by Santiago Ruano Rincón (Closes: #905044). -- Jeremy Bicha Wed, 23 Jan 2019 12:08:48 -0500 ** Changed in: clamav (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15378 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Also affects: anope (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: New Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807262] Fix included in openstack/sqlalchemy-migrate 0.12.0
This issue was fixed in the openstack/sqlalchemy-migrate 0.12.0 release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1807262 Title: stein unit tests fail with sqlalchemy.exc.NoSuchTableError: migration_tmp Status in sqlalchemy-migrate: Fix Released Status in cinder package in Ubuntu: Fix Released Status in migrate package in Ubuntu: Fix Released Status in nova package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Invalid Bug description: Several tests that use sqlite fail with: "sqlalchemy.exc.NoSuchTableError: migration_tmp". I'm currently hitting this with nova and cinder packages in disco. Note this started sometime after 11/19 when nova 2:19.0.0~b1~git2018111953.3e756ff674-0ubuntu1 was uploaded (and built successfully at the time). After doing some digging this appears to occur with libsqlite3-0 3.26.0-1 but does not occur with libsqlite3-0 3.25.3-1. Here are some more details on that, shown by running a failing unit test from the cinder package: https://paste.ubuntu.com/p/hsnQFQD572/ Update: The test in the paste above also works successfully with libsqlite3-0 3.25.3-2. To manage notifications about this bug go to: https://bugs.launchpad.net/sqlalchemy-migrate/+bug/1807262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754828] Re: Ubuntu 18.04 LTS fails to PXE boot
*** This bug is a duplicate of bug 1755863 *** https://bugs.launchpad.net/bugs/1755863 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: Ubuntu 18.04 LTS fails to PXE boot Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: i just downloaded the daily-live image from: http://cdimage.ubuntu.com/daily-live/current/bionic-desktop-amd64.iso and added it to my PXE server project (for more information see: https://github.com/beta-tester/RPi-PXE-Server/tree/testing). when i try to PXE boot the PC or VirtualBox from that ISO daily-live image, i run into the emergency mode console. earlier ISO images of Ubuntu (16.04.04, 17.10.1) are PXE booting this way correctly to the UI on both, PC and VirtualBox. when i burm the ISO of Ubuntu 18.04 LTS daily-live to a media and boot from it, it boots correctly. this are the PXE boot menu parameters: LABEL Ubuntu x64 Daily-Live KERNEL /nfs/ubuntu-daily-x64/casper/vmlinuz.efi APPEND initrd=/nfs/ubuntu-daily-x64/casper/initrd.lz netboot=nfs nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro file=/cdrom/preseed/ubuntu.seed boot=casper -- TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT this is the log i could grab from the emergency mode console: see attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754828] Re: Ubuntu 18.04 LTS fails to PXE boot
*** This bug is a duplicate of bug 1755863 *** https://bugs.launchpad.net/bugs/1755863 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: casper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754828 Title: Ubuntu 18.04 LTS fails to PXE boot Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: i just downloaded the daily-live image from: http://cdimage.ubuntu.com/daily-live/current/bionic-desktop-amd64.iso and added it to my PXE server project (for more information see: https://github.com/beta-tester/RPi-PXE-Server/tree/testing). when i try to PXE boot the PC or VirtualBox from that ISO daily-live image, i run into the emergency mode console. earlier ISO images of Ubuntu (16.04.04, 17.10.1) are PXE booting this way correctly to the UI on both, PC and VirtualBox. when i burm the ISO of Ubuntu 18.04 LTS daily-live to a media and boot from it, it boots correctly. this are the PXE boot menu parameters: LABEL Ubuntu x64 Daily-Live KERNEL /nfs/ubuntu-daily-x64/casper/vmlinuz.efi APPEND initrd=/nfs/ubuntu-daily-x64/casper/initrd.lz netboot=nfs nfsroot=192.168.1.1:/srv/nfs/ubuntu-daily-x64 ro file=/cdrom/preseed/ubuntu.seed boot=casper -- TEXT HELP Boot to Ubuntu x64 Daily-Live User: ubuntu ENDTEXT this is the log i could grab from the emergency mode console: see attached log. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754828/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU
Also happening to me after 16.04 -> 18.04 LTS upgrade (via do-release-
upgrade)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Status in dnsmasq package in Ubuntu:
Confirmed
Status in systemd package in Ubuntu:
Confirmed
Bug description:
Sometimes systemd-resolved process is using 100% CPU.
After a while it changes back to normal.
It happens usually after connecting to the (wifi) network, like
starting the OS.
strace output:
sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}],
msg_flags=0}, 0) = 81
sendmsg(3, {msg_name(0)=NULL,
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589),
sin_addr=inet_addr("127.0.0.1")},
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP,
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"),
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}},
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0)
= 53
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\365I", 2, GRND_NONBLOCK)= 2
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
getrandom("\203;", 2, GRND_NONBLOCK)= 2
clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such
file or directory)
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
connect(18, {sa_family=AF_INET, sin_port=htons(53),
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576,
u64=94565471566608}}) = 0
write(18,
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
53) = 53
clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0
close(18) = 0
journalctl output:
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS
queries reached (max: 150)
As you can see, I would use it together with dnsmasq.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: systemd 232-18ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
Date: Wed Mar 8 08:20:18 2017
MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
SourcePackage: systemd
UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
dmi.bios.date: 03/09/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M77 Ver. 01.05
dmi.board.name: 2271
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.4C
dmi.chassis.asset.tag: CNU51199KV
dmi.chassis.type: 10
dmi.chassis.vendor:
[Touch-packages] [Bug 1728246] Re: Apport shows the window without details, regularly
Ubuntu 17.10 has reached its End of Life and as such is no longer supported. Please upgrade to a supported release of Ubuntu and see if this is still happening. ** Changed in: apport (Ubuntu) Status: New => Won't Fix -- 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/1728246 Title: Apport shows the window without details, regularly Status in apport package in Ubuntu: Won't Fix Bug description: Apport shows the window without details, on a regular basis. Missing the ability to hide the replay and report an error. The program automatically shuts down without sending error report. When you try to use ubuntu-bug -w displays a message "cannot report a problem: this package is installed not correctly" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 28 20:02:54 2017 InstallationDate: Installed on 2015-08-27 (792 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1728246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728246] Re: Apport shows the window without details, regularly
** Package changed: evince (Ubuntu) => apport (Ubuntu) -- 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/1728246 Title: Apport shows the window without details, regularly Status in apport package in Ubuntu: New Bug description: Apport shows the window without details, on a regular basis. Missing the ability to hide the replay and report an error. The program automatically shuts down without sending error report. When you try to use ubuntu-bug -w displays a message "cannot report a problem: this package is installed not correctly" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 28 20:02:54 2017 InstallationDate: Installed on 2015-08-27 (792 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1728246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728246] [NEW] Apport shows the window without details, regularly
You have been subscribed to a public bug: Apport shows the window without details, on a regular basis. Missing the ability to hide the replay and report an error. The program automatically shuts down without sending error report. When you try to use ubuntu-bug -w displays a message "cannot report a problem: this package is installed not correctly" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 28 20:02:54 2017 InstallationDate: Installed on 2015-08-27 (792 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: evince UpgradeStatus: Upgraded to artful on 2017-10-25 (3 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- Apport shows the window without details, regularly https://bugs.launchpad.net/bugs/1728246 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812271] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231800/+files/CRDA.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231809/+files/WifiSyslog.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231801/+files/CurrentDmesg.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231807/+files/PulseList.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231808/+files/UdevDb.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231806/+files/ProcModules.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231804/+files/ProcCpuinfoMinimal.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231805/+files/ProcInterrupts.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231802/+files/Lspci.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231803/+files/ProcCpuinfo.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1812271] Re: Ubuntu 18.04.1, "Bad packet length nnnn."
The same issue happened on another DELL desktop model OptiPlex 7060. Running apport-collect 1812271 now. ** Description changed: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ywu2238 F pulseaudio + /dev/snd/controlC1: ywu2238 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + IwConfig: + eno1 no wireless extensions. + + lono wireless extensions. + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard + Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Dell Inc. OptiPlex 7060 + Package: openssh + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=57306e0b-a893-4ac1-ad8f-3359578e7e83 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.3 +
[Touch-packages] [Bug 1812271] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1812271/+attachment/5231799/+files/AlsaInfo.txt -- 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/1812271 Title: Ubuntu 18.04.1, "Bad packet length ." Status in linux package in Ubuntu: Confirmed Status in openssh package in Ubuntu: New Bug description: It happens when fetching Android project files by "repo sync" through ssh. More logs: Bad packet length 38201470. Finished discarding for 10.65.180.40 port 29418^M packet_process_incoming: Connection to 10.65.180.40 port 29418: message authentication code incorrect^M fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed I realized the error message like "Bad packet length 230911661." comes from ssh source file packet.c thus tried different SSH version but the issue is still there. $ ssh -V OpenSSH_7.6p1 Ubuntu-4ubuntu0.1, OpenSSL 1.0.2n 7 Dec 2017 ... $ ssh -V OpenSSH_7.5p1 Ubuntu-10, OpenSSL 1.1.0g 2 Nov 2017 In addition, I've tried workaround for NIC as: $ sudo ethtool -K enp3s0 rx off ... $ sudo ethtool -K enp3s0 rx off tx off but this doesn't work either. Here is the Network card information: $ sudo lshw -c network *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:03:00.0 logical name: enp3s0 version: 0c serial: f8:b1:56:d0:39:fd size: 1Gbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=full firmware=rtl8168g-2_0.0.1 02/06/13 ip=10.42.20.117 latency=0 link=yes multicast=yes port=MII speed=1Gbit/s resources: irq:44 ioport:e000(size=256) memory:f7b0-f7b00fff memory:f000-f0003fff No aware of any warning message from dmesg. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ywu2584 F pulseaudio /dev/snd/controlC0: ywu2584 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Dell Inc. XPS 8700 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro splash quiet vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/05/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0KWVT8 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd02/05/2018:svnDellInc.:pnXPS8700:pvr:rvnDellInc.:rn0KWVT8:rvrA02:cvnDellInc.:ct3:cvr: dmi.product.family: To be filled by O.E.M. dmi.product.name: XPS 8700 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ywu2238 F pulseaudio /dev/snd/controlC1: ywu2238 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IwConfig: eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 001 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 7060 Package: openssh ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine:
[Touch-packages] [Bug 1787729] Re: apport-autoreport.service fails if whoopsie isn't running
I just did an apt purge apport and reinstalled and it fixed the issue for me. -- 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/1787729 Title: apport-autoreport.service fails if whoopsie isn't running Status in apport package in Ubuntu: Fix Released Status in apport source package in Cosmic: In Progress Bug description: Impact -- If automatic crash reporting is enabled and apport-autoreport.service starts before whoopsie on boot then crash reports that happened during shutdown or start up will not be automatically uploaded to the error tracker. Test Case - 1) install apport-noui 2) sudo service apport stop 3) modify /usr/share/apport/whoopsie-upload-all to exit(1) thereby recreating the situation where whoopsie isn't running. I did this by copying lines 159,160 to 161,162 and unindenting them. N.B. this isn't necessary if you are on a system where whoopsie is starting after apport. 4) touch /var/crash/my.crash 5) reboot 5) run 'systemctl status apport-autoreport.service' and observe it failed because whoopsie isn't running When testing the proposed version of apport you'll want to revert the changes you made to whoopsie-upload-all. With the version of apport from -proposed you should no longer see the failure message for the apport-autoreport.service. The best test case is just having an affected system test the package from -proposed though. Regression Potential We are clearly fixing something that was a mistake in the original service so there is little chance for regression. ProblemType: BugDistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu7 Uname: Linux 4.18.3-041803-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 18 11:48:00 2018 InstallationDate: Installed on 2017-10-13 (308 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: allSourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1787729/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791283] Re: Cannot open files in required application with double click or open with in ftp Nautilus
That's still an issue and "gio open" does the sale ** Package changed: nautilus (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- 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/1791283 Title: Cannot open files in required application with double click or open with in ftp Nautilus Status in glib2.0 package in Ubuntu: Confirmed Bug description: For more information, see https://askubuntu.com/questions/964747 /cannot-open-text-editor-with-double-click-in-ftp- nautilus/1067423#1067423 When an FTP server is open in Nautilus and a file is either double clicked or right clicked and opened with (and app chosen from the menu), it always downloads the files with the default browser, rather than open in the requested application. One of the times this becomes a massive issue is when you are connected to an ftp web server and want to test changes in code live. This means you now have to download the file, open it, edit it, and re-upload. In the past for minor changes or in a test environment, it has been WAY faster to open the file directly in a txt editor, then just save and see the changes instantly. This is still working in Ubuntu 16.04. I have it failing in 18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 20:57:42 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+217+129'" InstallationDate: Installed on 2018-08-25 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1791283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791283] [NEW] Cannot open files in required application with double click or open with in ftp Nautilus
You have been subscribed to a public bug: For more information, see https://askubuntu.com/questions/964747/cannot- open-text-editor-with-double-click-in-ftp-nautilus/1067423#1067423 When an FTP server is open in Nautilus and a file is either double clicked or right clicked and opened with (and app chosen from the menu), it always downloads the files with the default browser, rather than open in the requested application. One of the times this becomes a massive issue is when you are connected to an ftp web server and want to test changes in code live. This means you now have to download the file, open it, edit it, and re-upload. In the past for minor changes or in a test environment, it has been WAY faster to open the file directly in a txt editor, then just save and see the changes instantly. This is still working in Ubuntu 16.04. I have it failing in 18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 20:57:42 2018 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'196' b'org.gnome.nautilus.window-state' b'geometry' b"'890x541+217+129'" InstallationDate: Installed on 2018-08-25 (13 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: glib2.0 (Ubuntu) Importance: Low Status: Confirmed ** Tags: amd64 apport-bug bionic -- Cannot open files in required application with double click or open with in ftp Nautilus https://bugs.launchpad.net/bugs/1791283 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
We are using lxc Ubuntu 18.04 on proxmox -5.3-7. Network configuration obtain through DHCP. We have desactivate /etc/resolv.conf modification over proxmox to get DHCP DNS use: touch .pve-ignore.resolv.conf Everything line in /etc/resolv.conf is comment: # cat /etc/resolv.conf # --- BEGIN PVE --- #search digicom.ca #nameserver 8.8.8.8 # --- END PVE --- Network status shown DNS entry is OK: #networkctl status ●State: routable Address: 172.16.8.23 on eth0 fe80::a0c5:bbff:fe4f:bc on eth0 Gateway: 172.16.8.1 (ICANN, IANA Department) on eth0 DNS: 104.192.16.1 NTP: 172.16.8.3 104.192.20.4 66.70.172.17 systemd-resolve works fine: #systemd-resolve go.com go.com: 23.236.60.174 -- Information acquired via protocol DNS in 1.3ms. -- Data is authenticated: no But resolve name using ping command or host failed: # ping go.com ping: go.com: Temporary failure in name resolution # host go.com ;; connection timed out; no servers could be reached The work around is to manually create a link to the systemd-resolve conf file: mv /etc/resolv.conf /etc/resolv.conf.orig ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Artful: Won't Fix Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813052] Re: who returns no results
Attempting to diagnose, I had added /var/run/utmp and /var/run/utmpx as
directories. I just removed those, same empty result:
# who
# who;echo $?
0
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x1726000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0bce
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7efc0bcdf000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7efc0b70e000
mprotect(0x7efc0b8ce000, 2097152, PROT_NONE) = 0
mmap(0x7efc0bace000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7efc0bace000
mmap(0x7efc0bad4000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7efc0bad4000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7efc0bcde000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7efc0bcdd000
arch_prctl(ARCH_SET_FS, 0x7efc0bcde700) = 0
mprotect(0x7efc0bace000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7efc0bcfd000, 4096, PROT_READ) = 0
munmap(0x7efc0bce, 117369) = 0
brk(NULL) = 0x1726000
brk(0x1747000) = 0x1747000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7efc0b436000
close(3)= 0
access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or directory)
open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
access("/var/run/utmpx", F_OK) = -1 ENOENT (No such file or directory)
open("/var/run/utmp", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or
directory)
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
#
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in coreutils package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
[Touch-packages] [Bug 1813052] [NEW] who returns no results
Public bug reported:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and an
strace on a system that works (an unupdated xenial or a bionic system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\t\2\0\0\0\0\0"...,
832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1868984, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eed000
mmap(NULL, 3971488, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f225391c000
mprotect(0x7f2253adc000, 2097152, PROT_NONE) = 0
mmap(0x7f2253cdc000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1c) = 0x7f2253cdc000
mmap(0x7f2253ce2000, 14752, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f2253ce2000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eec000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f2253eeb000
arch_prctl(ARCH_SET_FS, 0x7f2253eec700) = 0
mprotect(0x7f2253cdc000, 16384, PROT_READ) = 0
mprotect(0x60a000, 4096, PROT_READ) = 0
mprotect(0x7f2253f0b000, 4096, PROT_READ) = 0
munmap(0x7f2253eee000, 117369) = 0
brk(NULL) = 0x9f9000
brk(0xa1a000) = 0xa1a000
open("/usr/lib/locale/locale-archive", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2981280, ...}) = 0
mmap(NULL, 2981280, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253644000
close(3)= 0
access("/var/run/utmpx", F_OK) = 0
open("/var/run/utmpx", O_RDONLY|O_CLOEXEC) = 3
lseek(3, 0, SEEK_SET) = 0
alarm(0)= 0
rt_sigaction(SIGALRM, {0x7f2253a5d380, [], SA_RESTORER, 0x7f22539514b0},
{SIG_DFL, [], 0}, 8) = 0
alarm(10) = 0
fcntl(3, F_SETLKW, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
read(3, 0x7f2253ce5120, 384)= -1 EISDIR (Is a directory)
fcntl(3, F_SETLKW, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
alarm(0)= 10
rt_sigaction(SIGALRM, {SIG_DFL, [], SA_RESTORER, 0x7f22539514b0}, NULL, 8) = 0
close(3)= 0
close(1)= 0
close(2)= 0
exit_group(0) = ?
+++ exited with 0 +++
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: coreutils 8.25-2ubuntu3~16.04
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Wed Jan 23 10:39:00 2019
InstallationDate: Installed on 2016-07-08 (929 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1813052
Title:
who returns no results
Status in coreutils package in Ubuntu:
New
Bug description:
Who returns no results on xenial.
Here's an strace. I don't see any obvious difference between it and
an strace on a system that works (an unupdated xenial or a bionic
system).
# strace who
execve("/usr/bin/who", ["who"], [/* 21 vars */]) = 0
brk(NULL) = 0x9f9000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=117369, ...}) = 0
mmap(NULL, 117369, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f2253eee000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3,
[Touch-packages] [Bug 1764848] Re: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found
** Changed in: ca-certificates (Debian) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1764848 Title: Upgrade to ca-certificates to 20180409 causes ca-certificates.crt to be removed if duplicate certs found Status in Ubuntu Single Sign On Client: New Status in ca-certificates package in Ubuntu: Invalid Status in openssl package in Ubuntu: Fix Released Status in ca-certificates source package in Bionic: Invalid Status in openssl source package in Bionic: Fix Released Status in ca-certificates package in Debian: Fix Released Bug description: The certificate /usr/share/ca- certificates/mozilla/Go_Daddy_Class_2_CA.crt in package ca- certificates is conflicting with /etc/ssl/certs/UbuntuOne- Go_Daddy_Class_2_CA.pem from package python-ubuntu-sso-client. This results in the postinst trigger for ca-certificates to remove the /etc/ssl/certs/ca-certificates.crt file. This happens because the postinst trigger runs update-ca-certificates --fresh. If I run update-ca-certificates without the --fresh flag, the conflict is a non-issue and the ca-certificates.crt file is restored. If I understand some of the postinst code correctly, --fresh should only be run if called directly or if upgrading from a ca-certificates version older than 2011. Running bionic with daily -updates channel and ran into this this morning due to the release of ca-certificates version 20180409. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-sso-client/+bug/1764848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810840] Re: whoopsie can't remember "always report" setting
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: whoopsie-preferences (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie-preferences in Ubuntu. https://bugs.launchpad.net/bugs/1810840 Title: whoopsie can't remember "always report" setting Status in whoopsie-preferences package in Ubuntu: Confirmed Bug description: After ticking the checkbox for whoopsie to automatically always send crash reports, I get the following error dialog (screenshot attached): *Can't remember send report status settings* Saving crash report state failed. Can't set auto or never reporting mode. Command '['/usr/bin/gdbus', 'call', '-y', '-d', 'com.ubuntu.WhoopsiePreferences', '-o', '/com/ubuntu/WhoopsiePreferences', '-m', 'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']' returned non-zero exit status 1. I'm pretty sure this error happens because whoopsie-preferences was not installed; afterwards I installed whoopsie-preferences and manually ran in a terminal: $ /usr/bin/gdbus call -y -d com.ubuntu.WhoopsiePreferences -o /com/ubuntu/WhoopsiePreferences -m com.ubuntu.WhoopsiePreferences.SetReportCrashes true and got a return value of () but no errors or warnings. This computer was freshly-installed with Xubuntu 18.04 less than 2 weeks ago... I've kept a record of everything I changed since then, and I've only removed five packages (sgt-puzzles, gnome-sudoku, gnome- mines, pidgin, mousepad). If whoopsie-preferences is not included in a fresh install of (X)ubuntu, then perhaps it should be; in any case, if it isn't installed then the checkbox for making crash reporting automatic should not be visible. $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 $ apt-cache policy whoopsie whoopsie: Installed: 0.2.62 Candidate: 0.2.62 Version table: *** 0.2.62 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy whoopsie-preferences whoopsie-preferences: Installed: (none) Candidate: 0.19 Version table: 0.19 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie-preferences/+bug/1810840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751006] Re: Journalctl compiled without pattern matching support, pcre2 is not in main
pcre2 was promoted to main today for Ubuntu 19.04. ** No longer affects: pcre2 (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751006 Title: Journalctl compiled without pattern matching support, pcre2 is not in main Status in systemd package in Ubuntu: Triaged Bug description: Please add pattern matching support to journalctl. At the moment, the -g (--grep) option as described in the man page doesn't work: ╰─▶ journalctl --grep=xhci-hcd Compiled without pattern matching support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package libpam-mount - 2.16-9ubuntu2 --- libpam-mount (2.16-9ubuntu2) disco; urgency=medium * Revert remaining Ubuntu changes now that pcre2 is in main (LP: #1792544) -- Jeremy Bicha Wed, 23 Jan 2019 11:19:59 -0500 ** Changed in: libpam-mount (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Committed Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: clamav (Ubuntu) Status: Triaged => Fix Committed ** Package changed: php7.3 (Ubuntu) => php-defaults (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Committed Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1807761] Re: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi
That's still an issue in disco/with gnome-shell-extension-desktop-icons -- 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/1807761 Title: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi Status in gdebi package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 18.04 LTS or Ubuntu 18.10 2. Download some deb-file to the desktop - for with help of terminal: cd ~/Desktop apt-get download meld 3. Install GDebi package installer with sudo apt install gdebi 4. Select deb-file on desktop, make right click on it, select *Open With Other Application* select *GDebi Package Installer*, click *Select*, in opened window select *Install Package* Expected results: * GDebi asks user (sudo-able) password and installs the package Actual results: * GDebi do not ask user for password and do not install the package Notes: * first seen on AskUbuntu ( https://askubuntu.com/q/1099387/66509 ) * you can view my screencast to get first person view :) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 10 23:14:16 2018 GsettingsChanges: SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1807761/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: wget (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: libpam-mount (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Committed Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Won't Fix Status in php7.3 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Committed Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460038] Re: libarchive extracts zip as corrupt files but no warning or error
The fix got included in newer versions since ** Changed in: libarchive (Ubuntu) Importance: Undecided => Low ** Changed in: libarchive (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1460038 Title: libarchive extracts zip as corrupt files but no warning or error Status in libarchive package in Ubuntu: Fix Released Bug description: The attached zip file is produced by AirDroid and can be extracted successfully by unzip 6.00, ASUS File Manager for Android, and Windows 8.1. However libarchive13 version 3.1.2-7ubuntu2.1, in Linux Mint KDE 17.1 amd64, while extracts the files without any warning or error, results in corrupt files. These are all JPG files which cannot be viewed when extracted by Ark. Tested using both: * Ark 2.19 (4:4.14.2-0ubuntu1~ubuntu14.04~ppa1) * bsdcpio 3.1.2-7ubuntu2.1 Reproducible: Always Steps to Reproduce: 1. Extract Actual Results: Corrupt JPGs Expected Results: Proper JPGs For complete thread/diagnostics history please see https://bugs.kde.org/show_bug.cgi?id=348357 Upstream bug: https://github.com/libarchive/libarchive/issues/554 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1460038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794909] Re: Memory corruption in RAR decoder
Looks like those fixed landed now, https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-1000877.html ** CVE added: https://cve.mitre.org/cgi- bin/cvename.cgi?name=2018-1000877 ** Changed in: libarchive (Ubuntu) Importance: Undecided => High ** Changed in: libarchive (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive in Ubuntu. https://bugs.launchpad.net/bugs/1794909 Title: Memory corruption in RAR decoder Status in libarchive package in Ubuntu: Fix Released Bug description: Hi, There are some crashes and memory corruption issues in libarchive's RAR decoder. Most notably, I have observed some double-frees and heap use-after-frees, both reading and writing. These have not been detected by previous fuzzing runs because of the CRC checks in the RAR parser. The memory corruption seems to arise in ppmd7 decoding. The code can be made to read and write addresses that are at least partially attacker controlled, but the decoder is complex and I don't have the time to investigate fully whether the level of control is sufficient to lead to code execution. My gut feeling is that someone more skilled than I could cause arbitrary code execution, but I cannot say for certain. This bug can be used to crash bsdtar and other programs that use libarchive, such as file-roller. I have attached some test cases that demonstrate this. They run as follows: xxd -r testcase.rar.txt testcase.rar bsdtar -Oxf testcase.rar The test cases are: - oob-read.txt - Ppmd7_DecodeSymbol does an out-of-bounds read and crashes. (No UAF.) - uaf-read.txt - this heap UAF causes an out-of-bounds read in Ppmd7_DecodeSymbol and crashes. - double-free.txt - this test case causes a double-free - uaf-rw.txt - this shows reads and writes into a previously freed heap region. I've tested all of these on the version of bsdtar that ships with Ubuntu 18.04 Bionic and also with a build of libarchive from git. My analysis of their behaviour comes from running them under valgrind and ASAN. If you have any trouble reproducing them let me know. The crashes were found with afl-fuzz and the FairFuzz extension. I've also reported this to the OSS-Fuzz contacts for the upstream project. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1794909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1440157] Re: WARNING **: Could not connect to geoname lookup server: Operation was cancelled
Closing as all other tasks are showing fixed or invalid. ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libtimezonemap in Ubuntu. https://bugs.launchpad.net/bugs/1440157 Title: WARNING **: Could not connect to geoname lookup server: Operation was cancelled Status in One Hundred Papercuts: Fix Released Status in libtimezonemap package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Invalid Status in libtimezonemap source package in Vivid: Fix Released Status in unity-control-center source package in Vivid: Invalid Bug description: * Impact the dialog to add location doesn't work in a reliable way * Test Case open Date & Time panel > Clock Enable Time in other locations Click Choose Locations... Try to add a location, delete the name and type it again, it should work every time * Regression potential The entry to add location should work every time To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1440157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
** Changed in: vte2.91 (Ubuntu) Status: Triaged => Fix Committed ** Changed in: haproxy (Ubuntu) Status: Triaged => Fix Committed ** Changed in: haproxy (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: vte2.91 (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: git (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: New Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Triaged Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Committed Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Triaged Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php7.2 package in Ubuntu: Won't Fix Status in php7.3 package in Ubuntu: Triaged Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Incomplete Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Incomplete Status in zsh package in Ubuntu: Incomplete Bug description: demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. aide apache2 apr-util clamav exim4 freeradius git glib2.0 grep haproxy libpam-mount libselinux nginx nmap php7.2 postfix python-pyscss quagga rasqal slang2 sssd wget zsh -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named (according to jbicha). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796501] Re: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1796501 Title: systemd-resolved tries to mitigate DVE-2018-0001 even if DNSSEC=yes Status in systemd package in Ubuntu: Confirmed Bug description: I ask systemd-resolved through dig to resolve the SOA of test.asdf. (doesn't exist) but it returns SERVFAIL instead of NXDOMAIN. It seems to do the following steps: 1. Ask upstream for SOA of test.asdf. with EDNS0, DO-bit and 4k size. 2. Ask upstream for SOA of test.asdf. with EDNS0 and DO-bit. 3. Ask upstream for SOA of test.asdf. with EDNS0. 4. Ask upstream for SOA of test.asdf. without EDNS0. 5. Repeat 1-4 for DS of test.asdf. 6. Repeat 1-5 for asdf. 7. Ask upstream for SOA of . with EDNS0, DO-bit and 4k size. 8. Ask upstream for DNSKEY of . with EDNS0, DO-bit and 4k size. The upstream returns an unfragmented NXDOMAIN response for steps 1-6, an unfragmented NOERROR response for step 7 and a fragmented NOERROR response for step 8 which is the correct behaviour. DNSSEC records are included in the response if the DO-bit in the request was set. systemd-resolved should take the response from step 1 and start with validation instead of starting useless retries with reduced feture set. Step 3 and 4 are completely useless and probably lead to the SERVFAIL because I have configured it with DNSSEC=yes to prevent downgrade attacks. This regression seems to be caused by the patch resolved-Mitigate- DVE-2018-0001-by-retrying-NXDOMAIN-with.patch. The downgrade logic should only be executed if it is configured as DNSSEC=allow-downgrade or DNSSEC=no. See also https://github.com/systemd/systemd/pull/8608#issuecomment-396927885. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812760] Re: networkd: [Route] PreferredSource not working in *.network files
** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Bionic) Status: New => In Progress ** Changed in: systemd (Ubuntu Cosmic) Status: New => In Progress ** Changed in: systemd (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Importance: Undecided => Medium ** Also affects: systemd (Ubuntu Disco) Importance: Undecided Assignee: Daniel Axtens (daxtens) Status: In Progress ** Changed in: systemd (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: systemd (Ubuntu Cosmic) Assignee: (unassigned) => Daniel Axtens (daxtens) ** Changed in: systemd (Ubuntu Bionic) Assignee: (unassigned) => Daniel Axtens (daxtens) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1812760 Title: networkd: [Route] PreferredSource not working in *.network files Status in systemd package in Ubuntu: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] Users cannot create IPv6 routes that specify PreferredSource. This means that users cannot specify a number of valid IPv6 routes that are useful in some circumstances. These routes can be created with the 'ip' tool, just not with systemd. This was reported upstream in systemd issue #5882 is fixed by pulling in the changes in systemd PR #11375 - https://github.com/systemd/systemd/pull/11375 [Test Case] Start a Bionic or Cosmic VM. Add the following netplan yaml (adjust for ethernet card and MAC): network: version: 2 ethernets: ens3: dhcp4: true match: macaddress: 52:54:00:e2:c2:d7 set-name: ens3 addresses: ["fd8f:1d7d:b141::2/64", "fd8f:1d7d:b141::200/64"] routes: - to: "a::/16" via: "fd8f:1d7d:b141::1" from: "fd8f:1d7d:b141::2" - to: "fd8f:1d7d:b141::/64" scope: link from: "fd8f:1d7d:b141::2" metric: 255 Run netplan apply or reboot. Wait ~10s. Currently, ip -6 route will not include a route to "a::/16", and will not include the route to "fd8f:1d7d:b141::/64" that has "fd8f:1d7d:b141::2" as the source address - both those addresses will be missing. Correct behaviour is for ip -6 route to report the following: ubuntu@b-np:~$ ip -6 route a::/16 via fd8f:1d7d:b141::1 dev ens3 proto static src fd8f:1d7d:b141::2 metric 1024 pref medium fd8f:1d7d:b141::/64 dev ens3 proto static src fd8f:1d7d:b141::2 metric 255 pref medium fd8f:1d7d:b141::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium [Regression Potential] This changes the state machine in systemd which configures the links. It passes systemd's internal tests, and has been approved by systemd maintainers, but it remains possible that the changes will break the configuration of obscure network setups. The backport requires pulling in two further commits that also change behaviour: currently systemd deletes all addresses and routes that were attached to an interface. With this change, it will only delete those that are not specified in the configuration files. I do not know how this could cause issues - it moves from a surprising behaviour to a less surprising behaviour, but it's worth pointing out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1812760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813020] Re: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: alsa-driver (Ubuntu) Importance: Undecided => Low ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1813020 Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Incomplete Bug description: Suddenly my headphone stopped working. It is being detected when I plugged in. But there is no voice in headphone. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 23 19:15:32 2019 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 2018-07-29 (177 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-22T23:58:18.387600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option
This is blocked from processing due to missing SRU information as requested by Brian in comment 9 above. If you'd like to get this bug fixed, please help. See https://wiki.ubuntu.com/StableReleaseUpdates#Procedure for details. Otherwise the proposed fix will get rejected from the SRU queue. -- 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/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: In Progress Bug description: initramfs-tools ignores the FRAMEBUFFER option. This means that the framebuffer hook will always include the drm modules, regardless of whether it is dealing with an encrypted system or not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 24 18:06:24 2016 InstallationDate: Installed on 2016-02-16 (37 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160209) PackageArchitecture: all SourcePackage: initramfs-tools 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/1561643/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started
So, is anyone going to fix this? It is in LTS now and causing havoc. Fwiw, I support that it should allow split resolution just like it used to do. This change was a major breaking one that shouldn't have been forced on people. Security opinions don't belong in implementation, only configuration. -- 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/1726124 Title: DNS domain search paths not updated when VPN started Status in network-manager package in Ubuntu: Confirmed Status in network-manager-openvpn package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: I connect to work with openvpn through network-manager-openvpn. I'm selecting automatic (DHCP) to get an IP address, and "Use this connection only for resources on its network" to support split tunneling. In the last few versions of Ubuntu I used, this all worked fine. In Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both my VPN network and the internet, BUT I have to use FQDN for my VPN network hosts: the updates to the DNS search path provided by my VPN DHCP server are never being applied. Investigating the system I see that /etc/resolv.conf is pointing to /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not have any of the VPN's search path settings in it: # This file is managed by man:systemd-resolved(8). Do not edit. # # 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 In previous versions of Ubuntu, where NetworkManager controlled the resolver not systemd, /etc/resolv.conf pointed to /run/NetworkManager/resolv.conf and there was a local dnsmasq instance that managed all the complexity. In Ubuntu 17.10 when I look in /run/NetworkManager/resolv.conf file, I see that the search paths ARE properly updated there: $ cat /run/NetworkManager/resolv.conf # Generated by NetworkManager search internal.mycorp.com other.mycorp.com home nameserver 127.0.1.1 However this file isn't being used, and also there's no dnsmasq running on the system so if I switch my /etc/resolv.conf to point to this file instead, then all lookups fail. Strangely, if I look at the systemd-resolv status I see that in theory systemd-resolve does seem to know about the proper search paths: $ systemd-resolve --status ... Link 3 (tun0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 10.3.0.10 10.8.42.2 DNS Domain: ~internal.mycorp.com ~other.mycorp.com but for whatever reason the search domains are not getting put into the resolv.conf file: $ host mydesk ;; connection timed out; no servers could be reached $ host mydesk.internal.mycorp.com mydesk.internal.mycorp.com has address 10.8.37.74 (BTW, the timeout in the failed attempt above takes 10s: it is SUPER frustrating when all your host lookups are taking that long just to fail). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: systemd 234-2ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 22 15:08:57 2017 InstallationDate: Installed on 2017-10-21 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
@Jurit (juritxyz) I was wrong you need an other versions of systemd (21.11, 21.10 is for 16.04.5) IDK which ones but you can get them from launchpad I assume you need e.g. this architecture: https://launchpad.net/ubuntu/bionic/amd64/systemd/ You need these packages for successful downgrade get the version before the issue occured: libpam-systemd libsystemd0 systemd systemd-sysv Are you even on Armbian? What is your distribution! If you are on Armbian please proceed to this thread https://forum.armbian.com/topic/8852-ssh-doesnt-work-on-orange-pi- zero/?page=2 @Dimitri John Ledkov (xnox) I assume he is not on Armbian because nothing indicates that but however the issue still persists on certain kernel versions, obviously. -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
@Jurit (juritxyz) Stop thinking about the Armbian (ARM) kernel, it has nothing to with your kernel and you won't be able to update to my kernel because as already said it is for ARM7-based SOCs. You are on x86_x64 which needs a proper kernel for your architecture. You can check what kernels are available for your platform and verify if there is a newer one which maybe solves the issue for you. However IDK if there is one. And no you should in no case update to Armbian kernel ... I assume it will break everything. Another option would be to downgrade to systemd 21.11 or 21.10 and hold the packages until the bug is fixed. -- 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/1804603 Title: systemd-tmpfiles-setup.service fails on btrfs Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Disco: Fix Released Bug description: [Impact] * Last security update introduced a regression on btrfs based systems, causing systemd-tmpfiles-setup.service to fail to start, resulting in degraded machines. * Cherrypick upstream fixes to resolve this. [Test Case] * Install VM using btrfs for / * Boot, check that systemd-tmpfiles-setup.service is started successfully with: $ systemctl status systemd-tmpfiles-setup.service [Regression Potential] * btrfs fd doesn't support the set of flags that systemd used, with this patch, a compat set of flags is set instead, thus resolving the introduced regression. The worst case scenario is that creating subvolumes/directories is still broken (as in, the current status quo). [Other Info] * Example bad output After update to systemd 237-3ubuntu10.9 systemd-tmpfiles-setup.service fails with: Nov 21 13:44:12 node-blc49 systemd[1]: Starting Create Volatile Files and Directories... Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/var": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/home": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd-tmpfiles[1226]: Failed to create directory or subvolume "/srv": Bad file descriptor Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Nov 21 13:44:12 node-blc49 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Nov 21 13:44:12 node-blc49 systemd[1]: Failed to start Create Volatile Files and Directories. This happens on btrfs root filesystems in real hardware and on our virtualized servers as well. 237-3ubuntu10.6 didnt show this errors and going back to 237-3ubuntu10 removes them as well. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 # apt-cache policy systemd systemd: Installiert: 237-3ubuntu10.9 Installationskandidat: 237-3ubuntu10.9 Versionstabelle: *** 237-3ubuntu10.9 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 237-3ubuntu10 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804603/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813020] [NEW] [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all
Public bug reported: Suddenly my headphone stopped working. It is being detected when I plugged in. But there is no voice in headphone. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 23 19:15:32 2019 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 2018-07-29 (177 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-22T23:58:18.387600 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1813020 Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Suddenly my headphone stopped working. It is being detected when I plugged in. But there is no voice in headphone. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 23 19:15:32 2019 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 2018-07-29 (177 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: parag 1944 F pulseaudio Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Title: [Vostro 15-3568, Realtek ALC3246, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/13/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.0.4 dmi.board.name: 05HRPP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.0.4:bd11/13/2017:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 15-3568 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-01-22T23:58:18.387600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1813020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 263369] Re: Save file reverts to last location used. If not available, error is displayed.
Thunderbird task did not expire due to other other tasks and bug watch No reply from reporter or any comment for over 10 years Issue on Thunderbird was not confirmed by another user Cannot reproduce with Thunderbird 60.2.1 and Ubuntu 18.04 so closing ** Changed in: thunderbird (Ubuntu) Status: Incomplete => Invalid -- 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/263369 Title: Save file reverts to last location used. If not available, error is displayed. Status in The Gimp: Invalid Status in gtk+2.0 package in Ubuntu: Triaged Status in thunderbird package in Ubuntu: Invalid Bug description: Binary package hint: gimp If saving a file, some programs (such as GIMP and Thunderbird) will try to revert to the last location used when saving. If that location no longer exists (disk off line, path name changed, etc.), it warns you that it could not be found. Steps to reproduce: 1) Insert USB key 2) Create file, then save file 3) Unmount USB key 4) Create a new file then save file -ERROR- (Screenshot attached) "Error stating file: No such file or directory" What is expected: Ignore the error, do not display error to user as it is not productive, instead show the user's home directory as the default path to save if the last path used is not available. I will report if this happens under any other applications as well. If anyone has experienced this using another application please report it below. Version Information: Ubuntu Hardy (2.6.24-19-generic) gimp 2.4.5-1ubuntu2 thunderbird 2.0.0.16+nobinonly-0ubuntu0.8.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gimp/+bug/263369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812918] Re: Bluetooth Sound disjoined 18.04
Hi Daniel, Thanks for your answer, sorry for my poor english No relation with bug 1553669 or bug 1620636. I can pair my Bose QC35 with Ubuntu 18.04, but the sound is "jerky" ( untimely cut few sec with sound and few seconds without sound ). It was not the case with Ubuntu 16.04, only since the Ubuntu 18.04 upgrade. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1812918 Title: Bluetooth Sound disjoined 18.04 Status in bluez package in Ubuntu: Incomplete Bug description: Since upgrade Ubuntu 16.04 to 18.04, my bluetooth did not work fine, sound is disjoined 1) Ubuntu 18.04.1 LTS 2) apt-cache policy pkgname N: Impossible de trouver le paquet pkgname 3) With Ubuntu 16.04, my headset ( Bose QC35 ) was working fine by bluetooth connection 4) Sound is disjoined with Ubuntu 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 22 21:47:25 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=53832273-15e8-4b92-b0a3-6b1f2cf57770 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A78M-DS2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd01/08/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A78M-DS2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:1B:10:00:2A:EC ACL MTU: 1017:8 SCO MTU: 64:0 UP RUNNING PSCAN INQUIRY RX bytes:2620674 acl:357 sco:53942 events:1739 errors:0 TX bytes:3630646 acl:4536 sco:0 commands:218 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808109] Re: Upgrade to 1.12
This bug was fixed in the package gpgme1.0 - 1.12.0-4ubuntu1
---
gpgme1.0 (1.12.0-4ubuntu1) disco; urgency=low
* Merge from Debian unstable (LP: #1808109). Remaining changes:
- debian/patch/0007-Python-Versions.patch: Use py{,3}versions detection.
- debian/patches/0006-PIC-and-shared.patch: Libs are -fPIC and -shared.
- Add in libgpgme-dev a libgpgme-pthread.so pointing to libgpgme.so, this
will fix the build failures of kf5-kdepim-apps-libs when built against
this
gpgme package.
- Bump libgpg-error-dev build dependency to 1.28 for new gpgrt API
- Drop versioned python tests - 3.5 is not shipped anymore; and it
makes transitions harder for dubious benefits.
* qt-Use-tofu-conflict-test-keys-without-expiry.patch: Cherry pick
upstream fix for expiry dates in test suite.
gpgme1.0 (1.12.0-4) unstable; urgency=medium
* no need to clean up build-py3.7 any longer
* Fix test suite on arches with 32-bit time_t
gpgme1.0 (1.12.0-3) unstable; urgency=medium
* use upstream patches to build all versions of python
gpgme1.0 (1.12.0-2) unstable; urgency=medium
* clean up residue of older build reorganization
* do out-of-tree builds
* hide HAVE_CXX11 from python bindings
* perform an extra configuration and build to get python 3.7 working
gpgme1.0 (1.12.0-1) unstable; urgency=medium
* New upstream release
* refresh patches
* update .symbols
* refresh gpgmepp6.lintian-overrides
gpgme1.0 (1.11.1-2) unstable; urgency=medium
* acknowledge NMU (thanks, Adrian!)
* allow rebuild with older versions of libgpg-error
* drop python3.5, try to add 3.7
* d/changelog: strip trailing whitespace
* Standards-Version: bump to 4.2.1 (no changes needed)
* use dh_missing explicitly
* avoid shipping gpgme-json yet (we will ship it next release)
gpgme1.0 (1.11.1-1.1) unstable; urgency=medium
* Non-maintainer upload.
* Bump the libgpg-error-dev build dependency to >= 1.28.
(Closes: #898120)
-- Julian Andres Klode Mon, 14 Jan 2019 17:36:53
+0100
** Changed in: gpgme1.0 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1808109
Title:
Upgrade to 1.12
Status in gpgme1.0 package in Ubuntu:
Fix Released
Bug description:
GPGme 1.12 was release with a new json help that allows browsers to
use gpgme for encryption (see
https://www.mailvelope.com/de/blog/mailvelope-3.0 for example).
Debian (buster) already includes 1.12 and so should Ubuntu.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1808109/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813000] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 43
Public bug reported: error occurred when running do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Wed Jan 23 11:27:51 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 43 InstallationDate: Installed on 2013-08-24 (1978 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 (20120424.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 43 UpgradeStatus: Upgraded to bionic on 2019-01-23 (0 days ago) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1813000 Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 43 Status in ca-certificates package in Ubuntu: New Bug description: error occurred when running do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic i686 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 Date: Wed Jan 23 11:27:51 2019 ErrorMessage: installed ca-certificates package post-installation script subprocess returned error exit status 43 InstallationDate: Installed on 2013-08-24 (1978 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 (20120424.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 43 UpgradeStatus: Upgraded to bionic on 2019-01-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1813000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812223] Re: gir test fail on ppc64el
This bug was fixed in the package meson - 0.49.0-2ubuntu1 --- meson (0.49.0-2ubuntu1) disco; urgency=medium * Skip test_generate_gir_with_address_sanitizer on ppc64le. LP: #1812223 -- Dimitri John Ledkov Thu, 17 Jan 2019 15:36:43 + ** Changed in: meson (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gobject-introspection in Ubuntu. https://bugs.launchpad.net/bugs/1812223 Title: gir test fail on ppc64el Status in Meson: New Status in gcc-8 package in Ubuntu: New Status in gobject-introspection package in Ubuntu: New Status in meson package in Ubuntu: Fix Released Bug description: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/ppc64el/m/meson/20190116_031026_4df33@/log.gz ninja explain: genmarshal/genmarshalprog is dirty [1/75] Generating simple-resources_c with a custom command. [2/75] Generating simple-resources_h with a custom command. [3/75] Generating res3 with a meson_exe.py custom command. [4/75] Compiling C object 'resources/41d311a@@simple-resources-test@exe/meson-generated_.._simple-resources.c.o'. [5/75] Compiling C object 'resources/41d311a@@simple-resources-test@exe/simple-main.c.o'. [6/75] Generating simple-resources_gresource with a custom command. [7/75] Generating generated-resources_c with a custom command. [8/75] Generating generated-resources_h with a custom command. [9/75] Linking target resources/simple-resources-test. [10/75] Compiling C object 'resources/41d311a@@generated-resources-test@exe/meson-generated_.._generated-resources.c.o'. [11/75] Generating build-resources_gresource with a custom command. [12/75] Compiling C object 'resources/41d311a@@generated-resources-test@exe/generated-main.c.o'. [13/75] Linking target resources/generated-resources-test. [14/75] Compiling C object 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/dep2.c.o'. [15/75] Linking target gir/dep1/dep2/libdep2lib.so. [16/75] Compiling C object 'gir/dep1/07d7481@@dep1lib@sha/dep1.c.o'. [17/75] Generating symbol file 'gir/dep1/dep2/7cbf35a@@dep2lib@sha/libdep2lib.so.symbols'. [18/75] Linking target gir/dep1/libdep1lib.so. [19/75] Generating symbol file 'gir/dep1/07d7481@@dep1lib@sha/libdep1lib.so.symbols'. [20/75] Compiling C object 'gir/327a146@@gir_lib2@sha/meson-sample2.c.o'. [21/75] Linking target gir/libgir_lib2.so. [22/75] Generating gsettings-compile-schemas with a custom command. [23/75] Compiling C object 'schemas/fd70ea1@@schemaprog@exe/schemaprog.c.o'. [24/75] Linking target schemas/schemaprog. [25/75] Generating generated-gdbus.c with a custom command. [26/75] Generating generated-gdbus.h with a custom command. [27/75] Generating generated-gdbus-docbook with a custom command. [28/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/meson-generated_.._generated-gdbus.c.o'. [29/75] Compiling C object 'gdbus/8d60afc@@gdbus-test@exe/gdbusprog.c.o'. [30/75] Generating MesonDep2-1.0.gir with a custom command. g-ir-scanner: link: cc -o /tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0 /tmp/tmpbrjz1hlu/tmp-introspect81qm411v/MesonDep2-1.0.o -L. -Wl,-rpath,. -Wl,--no-as-needed -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 -Wl,-rpath,/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan -ldep2lib -lgobject-2.0 -lglib-2.0 -lgio-2.0 -lgobject-2.0 -Wl,--export-dynamic -lgmodule-2.0 -pthread -lglib-2.0 [31/75] Linking target gdbus/gdbus-test. [32/75] Generating MesonDep2-1.0.typelib with a custom command. [33/75] Generating enums.h with a meson_exe.py custom command. [34/75] Generating enums.c with a meson_exe.py custom command. [35/75] Compiling C object 'mkenums/75bf728@@enumprog1@exe/meson-generated_.._enums.c.o'. [36/75] Compiling C object 'mkenums/75bf728@@enumprog1@exe/meson-generated_.._main1.c.o'. [37/75] Linking target mkenums/enumprog1. [38/75] Generating MesonDep1-1.0.gir with a custom command. FAILED: gir/dep1/MesonDep1-1.0.gir /usr/bin/g-ir-scanner -pthread -I/usr/include/gobject-introspection-1.0 -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include --no-libtool --namespace=MesonDep1 --nsversion=1.0 --warn-all --output gir/dep1/MesonDep1-1.0.gir --c-include=dep1.h '-I/tmp/autopkgtest.GpLQfj/build.Rq6/src/test cases/frameworks/7 gnome/gir/dep1' -I/tmp/tmpbrjz1hlu/gir/dep1 --filelist=/tmp/tmpbrjz1hlu/gir/dep1/07d7481@@dep1lib@sha/MesonDep1_1.0_gir_filelist --include=GObject-2.0 --include=MesonDep2-1.0 --symbol-prefix=meson --identifier-prefix=Meson --cflags-begin -DMESON_TEST -fsanitize=address -fno-omit-frame-pointer -I/usr/include/glib-2.0 -I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include --cflags-end --add-include-path=/tmp/tmpbrjz1hlu/gir/dep1/dep2 -lasan -L/tmp/tmpbrjz1hlu/gir/dep1/dep2 --extra-library=dep2lib --library dep1lib -L/tmp/tmpbrjz1hlu/gir/dep1
[Touch-packages] [Bug 1812990] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1812990/+attachment/5231713/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1812990 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1812990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812990] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1812990/+attachment/5231714/+files/ThreadStacktrace.txt ** Changed in: packagekit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1812990 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1812990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812990] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libstdc++6 Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1812990/+attachment/5231701/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1812990 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1812990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812990] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1812990/+attachment/5231712/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1812990 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1812990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812990] [NEW] packagekitd crashed with SIGABRT in std::terminate()
Public bug reported: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: packagekit (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-crash disco ** 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 packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1812990 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1812990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812990] packagekitd crashed with SIGABRT in std::terminate()
StacktraceTop: ?? () from /tmp/apport_sandbox_xnlpvj6o/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /tmp/apport_sandbox_xnlpvj6o/usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /tmp/apport_sandbox_xnlpvj6o/usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /tmp/apport_sandbox_xnlpvj6o/usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /tmp/apport_sandbox_xnlpvj6o/usr/lib/x86_64-linux-gnu/libstdc++.so.6 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1812990 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: This crash happens after login. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: packagekit 1.1.12-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Wed Jan 23 07:39:17 2019 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-22 (396 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1812990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812984] [NEW] package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: I have no idea about the error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ca-certificates 20170717~14.04.2 ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Jan 23 15:59:29 2019 DuplicateSignature: package:ca-certificates:20170717~14.04.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-09-01 (143 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.19 SourcePackage: ca-certificates Title: package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1812984 Title: package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in ca-certificates package in Ubuntu: New Bug description: I have no idea about the error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ca-certificates 20170717~14.04.2 ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Jan 23 15:59:29 2019 DuplicateSignature: package:ca-certificates:20170717~14.04.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-09-01 (143 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.19 SourcePackage: ca-certificates Title: package ca-certificates 20170717~14.04.2 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/ca-certificates/+bug/1812984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812984] Re: package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1812984 Title: package ca-certificates 20170717~14.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in ca-certificates package in Ubuntu: New Bug description: I have no idea about the error ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ca-certificates 20170717~14.04.2 ProcVersionSignature: Ubuntu 4.4.0-141.167~14.04.1-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Wed Jan 23 15:59:29 2019 DuplicateSignature: package:ca-certificates:20170717~14.04.2:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2018-09-01 (143 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all RelatedPackageVersions: dpkg 1.17.5ubuntu5.8 apt 1.0.1ubuntu2.19 SourcePackage: ca-certificates Title: package ca-certificates 20170717~14.04.2 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/ca-certificates/+bug/1812984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1724803] Re: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)
I'm sorry but I don't really see the loop in the attached logs. Could you please add some more hint? ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- 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/1724803 Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Fell into command execution loop. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.8 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Tue Oct 17 12:16:36 2017 ErrorMessage: subprocess installed post-installation script was killed by signal (Terminated) InstallationDate: Installed on 2015-07-31 (810 days ago) InstallationMedia: It PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.25 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.8 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated) UpgradeStatus: Upgraded to xenial on 2017-10-17 (1 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "7"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-08-04T07:41:06.559797 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1724803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717247] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (mo
For finishing the configuration of unatetnded-upgrades please try running: apt-get -f install or if that does not help: dpkg --configure -a ** Changed in: unattended-upgrades (Ubuntu) Status: New => Incomplete -- 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/1717247 Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Dieser Fehler kommt immer wieder bei jeder Installation. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Sep 14 11:39:17 2017 ErrorMessage: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) InstallationDate: Installed on 2017-08-19 (25 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: Paket unattended-upgrades ist nicht bereit zur Konfiguration kann nicht konfiguriert werden (momentaner Status »half-installed«) UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1717247/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
** Package changed: gvfs (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Triaged -- 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 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/gvfs/+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 1812867] Re: sound from bluetooth device is like vintage when quiting the hibernate
*** This bug is a duplicate of bug 1789758 *** https://bugs.launchpad.net/bugs/1789758 ** No longer affects: ubuntubudgie -- 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/1812867 Title: sound from bluetooth device is like vintage when quiting the hibernate Status in pulseaudio package in Ubuntu: New Bug description: Hi I've just noticed this today, with my laptop and my desktop, both under Ubuntu Budgie 18.10, all last updates installed if it can help you. Using a USB Bluetooth key for both After using my wireless speaker (JBL GO for more precision if it's needed) within Bluetooth, I lock my computer when I leave my office. then I unlock my computer when I'm back to. Wanna play some music on the said device. Then I start to play music... with somewhat vintage effect on the sound. I shutdown the device, start it up and same thing. To get a working properly BT, I have to - unplug and plug the USB BT key - middle click two time on the Bluetooth logo at the top, likely to disable / enable it and then it work like a charm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1812867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
This bug was fixed in the package openldap - 2.4.47+dfsg-2ubuntu1
---
openldap (2.4.47+dfsg-2ubuntu1) disco; urgency=medium
* Merge from Debian unstable (LP: #1811630). Remaining changes:
- Enable AppArmor support:
- d/apparmor-profile: add AppArmor profile
- d/rules: use dh_apparmor
- d/control: Build-Depends on dh-apparmor
- d/slapd.README.Debian: add note about AppArmor
- Enable GSSAPI support:
- d/patches/gssapi.diff, thanks to Jerry Carter (Likewise):
- Add --with-gssapi support
- Make guess_service_principal() more robust when determining
principal
- d/configure.options: Configure with --with-gssapi
- d/control: Added heimdal-dev as a build depend
- d/rules:
- Explicitly add -I/usr/include/heimdal to CFLAGS.
- Explicitly add -I/usr/lib//heimdal to LDFLAGS.
- Enable ufw support:
- d/control: suggest ufw.
- d/rules: install ufw profile.
- d/slapd.ufw.profile: add ufw profile.
- Enable nss overlay:
- d/rules:
- add nssov to CONTRIB_MODULES
- add sysconfdir to CONTRIB_MAKEVARS
- d/slapd.install:
- install nssov overlay
- d/slapd.manpages:
- install slapo-nssov(5) man page
- d/{rules,slapd.py}: Add apport hook.
- d/slapd.init.ldif: don't set olcRootDN since it's not defined in
either the default DIT nor via an Authn mapping.
- d/slapd.scripts-common:
- add slapcat_opts to local variables.
- Fix backup directory naming for multiple reconfiguration.
- d/{slapd.default,slapd.README.Debian}: use the new configuration style.
- d/rules: Enable -DLDAP_CONNECTIONLESS to build CLDAP (UDP) support
in the openldap library, as required by Likewise-Open
- Show distribution in version:
- d/control: added lsb-release
- d/patches/fix-ldap-distribution.patch: show distribution in version
- d/libldap-2.4-2.symbols: Add symbols not present in Debian.
- CLDAP (UDP) was added in 2.4.17-1ubuntu2
- GSSAPI support was enabled in 2.4.18-0ubuntu2
* Update nssov build and packaging for Debian changes:
- Drop patch nssov-build
- d/rules:
- add nssov to CONTRIB_MODULES
- add sysconfdir to CONTRIB_MAKEVARS
- d/slapd.install:
- install nssov overlay
- d/slapd.manpages:
- install slapo-nssov(5) man page
openldap (2.4.47+dfsg-2) unstable; urgency=medium
* Reintroduce slapi-dev binary package. (Closes: #711469)
Thanks to Florian Schlichting.
* Do not call gnutls_global_set_mutex(). (Closes: #803197)
* Use dh_auto_* to build and install contrib modules.
- Stop patching the clean rule in smbk5pwd's Makefile.
* Explicitly list overlays and man pages installed by slapd package in
slapd.install and slapd.manpages files.
* Set common variables for contrib Makefiles by make(1) command line instead
of patching every Makefile.
* Build and install more contrib plugins in a new slapd-contrib package:
- pw-apr1 and pw-netscape (Closes: #592362)
- pw-pbkdf2 (Closes: #794999)
* Import the slapo-pw-pbkdf2 man page from upstream git master and install
it with the slapd-contrib package.
* Add smbk5pwd to slapd-contrib and turn slapd-smbk5pwd into a transitional
package. Drop smbk5pwd README since it now has a man page which is a
better resource for users.
- Use Breaks to ensure that slapd is not upgraded in between removing the
old smbk5pwd module and installing the new one.
* Include the apr1-atol.pl and apr1-lota.pl helper scripts in the
slapd-contrib package as examples.
* Merge remaining contrib Makefile patches into a single contrib-makefiles
patch.
openldap (2.4.47+dfsg-1) unstable; urgency=medium
* New upstream release.
- reverted GnuTLS handshake change in libldap as it regressed slapd
(Reopens: #861838)
* Update Standards-Version to 4.2.1.
-- Ryan Tandy Sun, 13 Jan 2019 04:47:09 +
** Changed in: openldap (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1811630
Title:
Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
Status in openldap package in Ubuntu:
Fix Released
Bug description:
Hello,
I have prepared the merge of openldap 2.4.47+dfsg-2. This will
probably be the version released in Debian buster unless any release
critical bugs show up.
I made changes in Debian to how the contrib modules are built. I made
the same changes for nssov in this merge and tested it with the
current nss/pam-ldapd. I also added its man page which doesn't seem to
have been included before.
I performed a test build in a PPA:
https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47
Please consider sponsoring this update. Thank you!
To
[Touch-packages] [Bug 378783] [NEW] xdg-open *.desktop opens text editor
You have been subscribed to a public bug: 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. ** Affects: gvfs Importance: Undecided Status: New ** Affects: glib2.0 (Ubuntu) Importance: Low Status: Triaged ** Tags: bionic -- xdg-open *.desktop opens text editor https://bugs.launchpad.net/bugs/378783 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812976] Re: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29
** Tags removed: need-duplicate-check -- 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/1812976 Title: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29 Status in cups package in Ubuntu: New Bug description: fails to install update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-bsd 2.2.7-1ubuntu2.3 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: Date: Sat Jan 19 16:16:52 2019 DuplicateSignature: package:cups-bsd:2.2.7-1ubuntu2.3 Setting up cups (2.2.7-1ubuntu2.3) ... Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 29 ErrorMessage: installed cups-bsd package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2018-10-10 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd MS-7A38 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600-generic root=UUID=cf49e5d3-b698-4d18-9122-55360cb14b83 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600-generic root=UUID=cf49e5d3-b698-4d18-9122-55360cb14b83 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: cups Title: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M BAZOOKA (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.00:bd03/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct10:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1812976/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812976] [NEW] package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29
Public bug reported: fails to install update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-bsd 2.2.7-1ubuntu2.3 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: Date: Sat Jan 19 16:16:52 2019 DuplicateSignature: package:cups-bsd:2.2.7-1ubuntu2.3 Setting up cups (2.2.7-1ubuntu2.3) ... Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 29 ErrorMessage: installed cups-bsd package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2018-10-10 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd MS-7A38 Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600-generic root=UUID=cf49e5d3-b698-4d18-9122-55360cb14b83 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.0-041600-generic root=UUID=cf49e5d3-b698-4d18-9122-55360cb14b83 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: cups Title: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.00 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A320M BAZOOKA (MS-7A38) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.00:bd03/20/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MBAZOOKA(MS-7A38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct10:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7A38 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1812976 Title: package cups-bsd 2.2.7-1ubuntu2.3 failed to install/upgrade: installed cups-bsd package post-installation script subprocess returned error exit status 29 Status in cups package in Ubuntu: New Bug description: fails to install update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups-bsd 2.2.7-1ubuntu2.3 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CupsErrorLog: Date: Sat Jan 19 16:16:52 2019 DuplicateSignature: package:cups-bsd:2.2.7-1ubuntu2.3 Setting up cups (2.2.7-1ubuntu2.3) ... Can't locate object method "new" via package "Text::Iconv" (perhaps you forgot to load "Text::Iconv"?) at /usr/share/perl5/Debconf/Encoding.pm line 65. dpkg: error processing package cups (--configure): installed cups package post-installation script subprocess returned error exit status 29 ErrorMessage: installed cups-bsd package post-installation script subprocess returned error exit status 29 InstallationDate: Installed on 2018-10-10 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 045e:0750 Microsoft Corp. Wired Keyboard 600 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star
[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal
We will notify them if the systemd does not fix the issue. So far, after the systemd upgrade, the server reboots fine in 24h test (reboot once at 5 min). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
> fixed in 11.0.2 in disco. no, it's not openjdk-lts-11.0.2+9$ grep 'int renderFlags =' * -r src/java.desktop/share/native/libfontmanager/freetypeScaler.c:int renderFlags = FT_LOAD_RENDER, target; see http://hg.openjdk.java.net/jdk/jdk12/rev/7ed5edf6ba0c if the fix was included it should be FT_LOAD_DEFAULT ** Changed in: openjdk-lts (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in freetype package in Ubuntu: Confirmed Status in openjdk-lts package in Ubuntu: New Status in freetype source package in Bionic: New Status in openjdk-lts source package in Bionic: New Status in freetype source package in Cosmic: New Status in openjdk-lts source package in Cosmic: New Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
