[Touch-packages] [Bug 1814485] Re: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- 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/1814485 Title: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Apps crashed/froze for a second for whatever reason, then error appeared,this is not a resident install, my first time running an OS from a USB stick. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: initramfs-tools 0.131ubuntu15 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Mon Feb 4 02:26:33 2019 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: initramfs-tools Title: package initramfs-tools 0.131ubuntu15 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
I uploaded these changes for bionic and cosmic. Just waiting on sru
approval now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
In Progress
Status in pulseaudio source package in Cosmic:
In Progress
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713017] Re: Enable MIDI support
Any chance this could be added? I know the last message is from 2017, but there commercial products such as the Yamaha MD-BT01 Bluetooth Wireless MIDI Adaptor that rely on this being enabled. -- 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/1713017 Title: Enable MIDI support Status in bluez package in Ubuntu: Triaged Bug description: Now that bluez has landed with 5.46-0ubuntu2, it would be nice to enable Bluetooth MIDI support. This did not seem to be enabled by default in the build from https://launchpad.net/ubuntu/+source/bluez/5.46-0ubuntu2 (it found BLE MIDI devices, gatttool could talk to them, but no MIDI device was made; also ldd showed no linkage to libasound.so.2). After recompiling it with libasound2-dev installed and --enable-midi in debian/rules, it worked. Suggestion: add libasound2-dev to bluez dependencies, add --enable- midi to rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1713017/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1808664] Re: pulse udio is not starting automatically at boot
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1808664 Title: pulse udio is not starting automatically at boot Status in pulseaudio package in Ubuntu: Expired Bug description: Pulseaudio is not getting loaded at the time of boot and it has to be manually started each time ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-42-generic. ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: murtyvonna 2094 F pulseaudio /dev/snd/controlC0: murtyvonna 2094 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf7f1 irq 34' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,1043841b,00100302 HDA:80862806,80860101,0010' Controls : 65 Simple ctrls : 24 Card1.Amixer.info: Card hw:1 'U0x46d0x825'/'USB Device 0x46d:0x825 at usb-:00:14.0-1, high speed' Mixer name : 'USB Mixer' Components : 'USB046d:0825' Controls : 3 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined Capture channels: Mono Limits: Capture 0 - 15 Mono: Capture 0 [0%] [8.00dB] [on] CurrentDesktop: ubuntu:GNOME Date: Sun Dec 16 08:19:23 2018 InstallationDate: Installed on 2018-08-06 (131 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1402 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1402:bd03/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLK:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1808664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Also affects: openssl (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libio-socket-ssl-perl (Ubuntu) Importance: Undecided Status: New ** Also affects: libnet-ssleay-perl (Ubuntu) Importance: Undecided Status: New ** Also affects: nova (Ubuntu) Importance: Undecided Status: New ** Also affects: python-cryptography (Ubuntu) Importance: Undecided Status: New ** Also affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Also affects: python3.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: python3.7 (Ubuntu) Importance: Undecided Status: New ** Also affects: r-cran-openssl (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby-openssl (Ubuntu) Importance: Undecided Status: New ** Also affects: ruby2.5 (Ubuntu) Importance: Undecided Status: New ** Description changed: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes - * Notable changes are listed here + * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 - * Most common connectivity issues so far: -- client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. + * Most common connectivity issues so far: + - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. -- session negotiation is different in TLSv1.3, existing client code + - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. + + * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 ** Changed in: openssl (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS Status in libio-socket-ssl-perl package in Ubuntu: New Status in libnet-ssleay-perl package in Ubuntu: New Status in nova package in Ubuntu: New Status in openssl package in Ubuntu: In Progress Status in python-cryptography package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in r-cran-openssl package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Status in libio-socket-ssl-perl source package in Bionic: New Status in libnet-ssleay-perl source package in Bionic: New Status in nova source package in Bionic: New Status in openssl source package in Bionic: New Status in python-cryptography source package in Bionic: New Status in python2.7 source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in r-cran-openssl source package in Bionic: New Status in ruby-openssl source package in Bionic: New Status in ruby2.5 source package in Bionic: New Bug description: [Impact]
[Touch-packages] [Bug 1697481] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()
*** This bug is a duplicate of bug 1697234 *** https://bugs.launchpad.net/bugs/1697234 my desktop os is Ubuntu 16.04.5 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1697481 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: Every time I open a folder with MTS video files the video thumbnailer crashes. It would be ok, if it just failed gracefully. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1 ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-54-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Mon Jun 12 16:58:17 2017 ExecutablePath: /usr/bin/totem-video-thumbnailer InstallationDate: Installed on 2016-09-09 (275 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256 file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS /tmp/.gnome_desktop_thumbnail.59DG1Y Signal: 5 SourcePackage: gstreamer1.0 StacktraceTop: g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_buffer_new_allocate () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0 Title: totem-video-thumbnailer crashed with signal 5 in g_malloc() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: lxd sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697481] Re: totem-video-thumbnailer crashed with signal 5 in g_malloc()
*** This bug is a duplicate of bug 1697234 ***
https://bugs.launchpad.net/bugs/1697234
I have same problem,
I figured
~/.cache/upstart/update-notifier-crash-_var_crash__usr_bin_totem-video-thumbnailer.1000.crash.log
like below:
2019. 02. 15. (금) 11:41:51 KST crash report /var/crash/_usr_bin_totem-
video-thumbnailer.1000.crash detected
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget
'GtkSpinner': out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget
'GtkAlignment': out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget
'GtkOverlay': out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkBox':
out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkBox':
out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkBox':
out of memory
(apport-gtk:6303): Gtk-WARNING **: drawing failure for widget 'GtkWindow': out
of memory
ERROR: hook /usr/share/apport/package-hooks/source_totem.py crashed:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 197, in _run_hook
symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/source_totem.py", line 9, in add_info
response = ui.choice("How would you describe the issue?", ["The totem
interface is not working correctly", "No sound is being played", "Some audio
files or videos are not being played correctly"], False)
AttributeError: 'NoneType' object has no attribute 'choice'
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1697481
Title:
totem-video-thumbnailer crashed with signal 5 in g_malloc()
Status in gstreamer1.0 package in Ubuntu:
Confirmed
Bug description:
Every time I open a folder with MTS video files the video thumbnailer
crashes. It would be ok, if it just failed gracefully.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Mon Jun 12 16:58:17 2017
ExecutablePath: /usr/bin/totem-video-thumbnailer
InstallationDate: Installed on 2016-09-09 (275 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
JournalErrors:
Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000']
failed with exit code 1: Hint: You are currently not seeing messages from other
users and the system.
Users in the 'systemd-journal' group can see all messages. Pass -q to
turn off this notice.
No journal files were opened due to insufficient permissions.
ProcCmdline: /usr/bin/totem-video-thumbnailer -s 256
file:///media/username/0123-4567/PRIVATE/AVCHD/BDMV/STREAM/00139.MTS
/tmp/.gnome_desktop_thumbnail.59DG1Y
Signal: 5
SourcePackage: gstreamer1.0
StacktraceTop:
g_malloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_slice_alloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
gst_buffer_new_allocate () from
/usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgstvideo-1.0.so.0
Title: totem-video-thumbnailer crashed with signal 5 in g_malloc()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: lxd sudo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1697481/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814818] Re: Skip enslaved devices during boot
This bug was fixed in the package initramfs-tools - 0.131ubuntu15.1 --- initramfs-tools (0.131ubuntu15.1) cosmic-security; urgency=medium * scripts/functions: include a new option to skip enslaved network devices. (LP: #1814818) Include the new variable NETWORK_SKIP_ENSLAVED. When set to a value different than "0", this variable will cause any enslaved network devices to be skipped from the list of netbootable devices. This variable can be set via the configuration files under /etc/initramfs-tools/ or via any configuration file under the initrd directory /conf/conf.d/ via a hook script. -- Marcelo Henrique Cerri Tue, 05 Feb 2019 20:08:09 + ** Changed in: initramfs-tools (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- 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/1814818 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Cosmic: Fix Released Bug description: [Impact] In some scenarios, we need to skip enslaved network devices from being brought up in initrd. In order to avoid regressions for other users, the new behaviour is being conditioned to the configuration variable NETWORK_SKIP_ENSLAVED. This mechanism enable us to use it only for the required kernels. The target kernel should be responsible to include the configuration via an initramfs-tools hook. [Test Case] Enslaved network devices shouldn't be brought up when the configuration is set by certain kernels. For any other scenario, such as the generic Ubuntu kernel, the behaviour should not be changed. [Regression Potential] The potential for regressions was vastly reduced by conditioning the new behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435452] Re: dh_apparmor has no dh sequencer support
FWIW I went hunting for bug reports about this issue in response to https://github.com/snapcore/snapd/pull/6508 - if this were solved centrally in dh-apparmor, I expect that would benefit a number of packages over the long term. -- 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/1435452 Title: dh_apparmor has no dh sequencer support Status in apparmor package in Ubuntu: Confirmed Bug description: As dh_apparmor timing is critical (it must run before services are started with dh_installinit), it makes sense to provide direct dh sequencer support so that maintainers don't have to remember to run it directly, and cannot mistakenly call it at the wrong point, as happened with MySQL in bug 1421303). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1435452/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815987] [NEW] Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS
Public bug reported: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root 512 Feb 9 17:34 random-seed drwxr-xr-x 2 root root 4096 Jul 10 2018 timers lrwxrwxrwx 1 root root 27 Jul 8 2018 timesync -> ../private/systemd/timesync ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1815987 Title: Systemd-tmpfiles-setup won't launch in Ubuntu 18.04 LTS Status in systemd package in Ubuntu: New Bug description: I am using Ubuntu 18.04LTS, fresh install from the summer, and tmpfiles won't launch since November. $ sudo systemctl start systemd-tmpfiles-setup Job for systemd-tmpfiles-setup.service failed because the control process exited with error code. See "systemctl status systemd-tmpfiles-setup.service" and "journalctl -xe" for details. $ sudo systemctl status systemd-tmpfiles-setup ● systemd-tmpfiles-setup.service - Create Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2019-02-14 19:48:36 EST; 8s ago Docs: man:tmpfiles.d(5) man:systemd-tmpfiles(8) Process: 28934 ExecStart=/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev (code=exited, status=1/FAILURE) Main PID: 28934 (code=exited, status=1/FAILURE) Feb 14 19:48:35 mythserver2018 systemd[1]: Starting Create Volatile Files and Directories... Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/colord/icc, refusing. Feb 14 19:48:35 mythserver2018 systemd-tmpfiles[28934]: Unsafe symlinks encountered in /var/lib/systemd/coredump, refusing. Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Feb 14 19:48:36 mythserver2018 systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. Feb 14 19:48:36 mythserver2018 systemd[1]: Failed to start Create Volatile Files and Directories. Looking at /var/lib/colord/icc: kris@mythserver2018:/var/lib/colord/icc$ ls -a . .. kris@mythserver2018:/var/lib/colord/icc$ I have also deleted these directories and rebuilt them, just to be sure - they are NOT symlinked and have no permission issues: kris@mythserver2018:/var/lib/systemd$ ls -l total 28 drwxr-xr-x 2 root root 4096 Feb 9 16:04 catalog drwxr-xr-x 2 root root 4096 Dec 28 07:04 coredump drwxr-xr-x 2 root root 4096 Jul 8 2018 coredumpold drwxr-xr-x 20 root root 4096 Feb 9 16:08 deb-systemd-helper-enabled drwxr-xr-x 2 root root 4096 Nov 14 18:31 deb-systemd-helper-masked -rw--- 1 root root
[Touch-packages] [Bug 1814818] Re: Skip enslaved devices during boot
Verification performed in cosmic using the generic kernel (4.18.0-15.16) and the previous behaviour was preserved as expected. We currently don't have a kernel in cosmic that enables that feature by default, but I built a custom kernel in order to test it and it worked as expected. In theory it was also possible to manually add the config variable, but the test kernel is as closest as we can get to the real use case. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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/1814818 Title: Skip enslaved devices during boot Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Cosmic: Fix Committed Bug description: [Impact] In some scenarios, we need to skip enslaved network devices from being brought up in initrd. In order to avoid regressions for other users, the new behaviour is being conditioned to the configuration variable NETWORK_SKIP_ENSLAVED. This mechanism enable us to use it only for the required kernels. The target kernel should be responsible to include the configuration via an initramfs-tools hook. [Test Case] Enslaved network devices shouldn't be brought up when the configuration is set by certain kernels. For any other scenario, such as the generic Ubuntu kernel, the behaviour should not be changed. [Regression Potential] The potential for regressions was vastly reduced by conditioning the new behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814818/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
all updates are out. there no more further updates planned for this issue. if you have any issues on your systems, you need to debug what's wrong and open a new bug report, attaching systemd-journal details from a broken boot. most likely something is wrong with your system, forexample unsafe ownership, unsafe permissions, broken host kernel etc. on all up to date ubuntu systems, installed using ubuntu installers, with latest ubuntu kernel there are no issues at all. please open a new bug report, if you have issues with your systems. -- 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 - I tried that months ago as documented in the forums. Didnt fix the issue. I also have run the sudo apt-get upgrade several times as well - still not fixed for me. I also see they did push a new kernel - still occurs. Not sure what else I can do... -- 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 1815956] [NEW] package libperl5.26 5.26.2-7ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different fr
Public bug reported: Error message on system startup ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libperl5.26 5.26.2-7ubuntu0.1 Uname: Linux 4.19.0-041900rc8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Mon Feb 11 21:46:08 2019 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-12-22 (54 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: perl Title: package libperl5.26 5.26.2-7ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1815956 Title: package libperl5.26 5.26.2-7ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 Status in perl package in Ubuntu: New Bug description: Error message on system startup ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libperl5.26 5.26.2-7ubuntu0.1 Uname: Linux 4.19.0-041900rc8-lowlatency x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 Date: Mon Feb 11 21:46:08 2019 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-12-22 (54 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.7-1~18.10 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.2 SourcePackage: perl Title: package libperl5.26 5.26.2-7ubuntu0.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1815956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Triaged
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco
Confirmed, that's fixed with that update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1815774 Title: binutils 2.32 update breaks debug symbols in disco Status in Apport: New Status in binutils package in Ubuntu: Invalid Status in gdb package in Ubuntu: Fix Released Status in binutils source package in Disco: Invalid Status in gdb source package in Disco: Fix Released Bug description: Recently retracing started failing in disco, that seems to be due to the binutils 2.32 update example $ gdb gnome-control-center ... Reading symbols from gnome-control-center...BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: unable to initialize decompress status for section .debug_aranges BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: unable to initialize decompress status for section .debug_aranges warning: File "/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has no build-id, file skipped (no debugging symbols found)...done. Rebuilding the package with binutils 2.31 installed fixes the issue. Googling for the warning lead to an arch bug pointing out that upstream commit as fixing the issue https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1815774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815947] Re: video
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1815947 Title: video Status in xorg package in Ubuntu: Incomplete Bug description: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: /dev/sda1: clean, 323551/19144704 files, 17190727/76570112 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 14 19:14:04 2019 DistUpgraded: 2018-06-22 23:29:57,626 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce GTS 250] [10b0:0401] NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G92 [GeForce GTS 250] [1043:82fb] InstallationDate: Installed on 2018-06-17 (242 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=sl PATH=(custom, no user) LANG=sl_SI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=0bbe53b3-055a-45b3-9588-a717e2462ba9 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-22 (236 days ago) dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 0703 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision0703:bd08/09/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
[Touch-packages] [Bug 1815947] [NEW] video
Public bug reported: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Je imenik: '/proc/driver/nvidia/gpus/:02:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.104 Thu Sep 14 17:13:13 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.11) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: /dev/sda1: clean, 323551/19144704 files, 17190727/76570112 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Feb 14 19:14:04 2019 DistUpgraded: 2018-06-22 23:29:57,626 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology G92 [GeForce GTS 250] [10b0:0401] NVIDIA Corporation G92 [GeForce GTS 250] [10de:0615] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G92 [GeForce GTS 250] [1043:82fb] InstallationDate: Installed on 2018-06-17 (242 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=sl PATH=(custom, no user) LANG=sl_SI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic root=UUID=0bbe53b3-055a-45b3-9588-a717e2462ba9 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-22 (236 days ago) dmi.bios.date: 08/09/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 0703 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision0703:bd08/09/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Feb 13 18:46:13 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: [drm] Failed to open DRM device for (null): -22 open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1815947 Title: video Status in xorg package in Ubuntu: New Bug description: beside_only_pixel_mousebl_nettv_no_lon_same_se_al_?_n_wh_cr_tsp ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
@Guillermo, i have the same issue with ubuntu 19.04 daily (pending) from 2019-02-14 (without using the workaround) when pxe booting. /var/log/syslog shows the folowing lines, when i serch for resolv: ``` Feb 14 17:53:27 ubuntu systemd[1]: Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down... Feb 14 17:53:27 ubuntu systemd[1]: Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down. Feb 14 17:53:27 ubuntu avahi-daemon[1225]: Failed to open /etc/resolv.conf: Invalid argument Feb 14 17:53:27 ubuntu kernel: [6.498832] Key type dns_resolver registered Feb 14 17:53:27 ubuntu kernel: [6.985154] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [6.985719] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [6.986106] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [6.988112] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT2._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [7.347354] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:27 ubuntu kernel: [7.357711] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330) Feb 14 17:53:28 ubuntu sh[1400]: grep: /etc/resolv.conf: No such file or directory Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Positive Trust Anchors: Feb 14 17:53:29 ubuntu systemd-resolved[1604]: . IN DS 19036 8 2 ... Feb 14 17:53:29 ubuntu systemd-resolved[1604]: . IN DS 20326 8 2 ... Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa 168.192.in-addr.arpa d.f.ip6.arpa corp home internal intranet lan local private test Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Using system hostname 'ubuntu'. Feb 14 17:53:29 ubuntu systemd-resolved[1604]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 14 17:53:30 ubuntu NetworkManager[1405]: [1550166810.1729] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 10-globally-managed-devices.conf, 20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (run: netplan.conf) (etc: default-wifi-powersave-on.conf) Feb 14 17:53:30 ubuntu NetworkManager[1405]: [1550166810.4138] dns-mgr[0x55dc42397170]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved Feb 14 17:54:29 ubuntu systemd-resolved[1604]: Using degraded feature set (UDP) for DNS server 192.168.0.1. ``` PS: long time ago i opened a report for that, but never got any reaction there... https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1765765 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: Triaged Status in systemd source package in Disco: Fix Released Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl
[Touch-packages] [Bug 1815172]
Just correcting a wrong comment (#2) I made: > It happens on both 32bit and 64bit installations. I asked the school that reported the issue on 64bit to check again, and they said they have a 32bit installation after all. So the problem has only been reported in 32bit installations; I don't know if it happened on 64bit. And btw everything is fixed now, thanks again to all. :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1815172 Title: Black screen on skylake after 18.0 => 18.2 update Status in Mesa: Fix Released Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in linux source package in Bionic: New Status in mesa source package in Bionic: Fix Committed Status in linux source package in Cosmic: New Status in mesa source package in Cosmic: Fix Committed Bug description: Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 ***
https://bugs.launchpad.net/bugs/1676547
Workaround: in ubuntu 18.4
Create an empty file /etc/NetworkManager/conf.d/10-globally-managed-devices.
Create an file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with
content:
network: {config: disabled}
Work for me,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1638842
Title:
network-manager does not manage ethernet and bluetooth interfaces when
Ubuntu 16.10 is installed using chroot/netboot method
Status in network-manager package in Ubuntu:
Won't Fix
Bug description:
Hello,
I installed Ubuntu 16.10 using a chroot. I use network-manager to
manage connections. My system is up-to-date (so I use network-manager
1.2.4-0ubuntu1).
Wifi works perfectly but I cannot connect to wired networks and using
my phone's Bluetooth connection. Corresponding devices are said to be
unmanaged by network-manager. nmcli dev outputs:
DEVICETYPE STATE CONNECTION
enp1s0ethernet unmanaged --
wlp2s0wifi disconnected --
6C:9B:02:2C:EE:2C btunmanaged --
hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged --
loloopback unmanaged --
The following command has no effect:
sudo nmcli dev set enp1s0 managed yes
I can connect to a wired connection by doing:
ifconfig enp1s0 up
dhclient enp1s0
There is nothing in the file /etc/network/interfaces.
Everything works perfectly if I downgrade network-manager to this
version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
(http://packages.ubuntu.com/xenial-updates/amd64/network-
manager/download). I had to install libreadline6 and downgrade nplan
to meet dependencies.
I don't know what to join to this bug report so please ask in case
anything is needed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814460] Re: systemd-cryptsetup fails during initrd stage of boot
This is interesting. So i'm not sure if our stacks are up to date on bionic to use these things. Most likely our dracut / cryptsetup is too old to use clevis. Ideally, clevis would need initramfs-tools integration to work on ubuntu nicely. If you can, please try this again on disco, if that's any better? but i doubt it. I'm not sure if there are any timelines on getting clevis to work on bionic unfortunately. Maybe in the future. ** Also affects: dracut (Ubuntu) Importance: Undecided Status: New ** Also affects: clevis (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1814460 Title: systemd-cryptsetup fails during initrd stage of boot Status in clevis package in Ubuntu: New Status in dracut package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I use Ubuntu 18.04.1 with systemd version: systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid I use dracut + clevis for automatic decryption of my LUKS encrypted drives during boot. I get the following message from one of the non-root disks: ● systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service - Cryptography Setup for luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 Loaded: loaded (/etc/crypttab; generated) Active: failed (Result: signal) since Sun 2019-02-03 15:04:35 UTC; 5min ago Docs: man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) Process: 589 ExecStart=/lib/systemd/systemd-cryptsetup attach luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1 none luks,discard (code=killed, signal=ABRT) Main PID: 589 (code=killed, signal=ABRT) Feb 03 15:04:26 beta systemd[1]: Starting Cryptography Setup for luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1... Feb 03 15:04:35 beta systemd-cryptsetup[589]: Set cipher aes, mode xts-plain64, key size 256 bits for device /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1. Feb 03 15:04:35 beta systemd-cryptsetup[589]: realloc(): invalid next size Feb 03 15:04:35 beta systemd[1]: systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service: Main process exited, code=killed, status=6/ABRT Feb 03 15:04:35 beta systemd[1]: systemd-cryptsetup@luks\x2data\x2dWDC_WD30EFRX\x2d68EUZN0_WD\x2dWCC4N5DC8C4C\x2dpart1.service: Failed with result 'signal'. Feb 03 15:04:35 beta systemd[1]: Failed to start Cryptography Setup for luks-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5DC8C4C-part1. The systemd issue reporting template told me to not report systemd issues for anything but the two newest versions of systemd, and refered to the distribution bug tracker instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clevis/+bug/1814460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was erroneously marked for verification in bionic; verification is not required and verification-needed-bionic is being removed. ** Tags removed: verification-needed-bionic ** Tags added: kernel-fixup-verification-needed-bionic verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Committed Status in xorg-server source package in Bionic: Fix Released Status in libdrm source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in mesa source package in Cosmic: Fix Committed Status in xorg-server source package in Cosmic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal
> Any other suggestion from your side? The system hang in this bug is really hardware related, so HPE needs to take a deeper look. For someone like us that cannot dig into firmware/hardware and need to find a solution at software level, in general I'll start with disabling runtime power management for all devices. -- 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 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
Yes, I understand that users will not see nemo, but the memory will :) But I get why nautilus is hard to let go. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
@Amr Ah, No. In users eye nemo won't even exist in Unity. We are only using nemo-desktop which is a separate binary to draw icons under unity, nothing else. It's difficult to remove nautilus completely as it is burried deep. It requires work on unity, unity-lens-files, hud, bamf, zeitgeist and in indicators. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
** Attachment added: "coredumpctl.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+attachment/5238665/+files/coredumpctl.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco
gdb 8.2.50.x handles this. ** Also affects: gdb (Ubuntu) Importance: Undecided Status: New ** Changed in: gdb (Ubuntu Disco) Status: New => Fix Released ** Changed in: binutils (Ubuntu Disco) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1815774 Title: binutils 2.32 update breaks debug symbols in disco Status in Apport: New Status in binutils package in Ubuntu: Invalid Status in gdb package in Ubuntu: Fix Released Status in binutils source package in Disco: Invalid Status in gdb source package in Disco: Fix Released Bug description: Recently retracing started failing in disco, that seems to be due to the binutils 2.32 update example $ gdb gnome-control-center ... Reading symbols from gnome-control-center...BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: unable to initialize decompress status for section .debug_aranges BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: unable to initialize decompress status for section .debug_aranges warning: File "/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has no build-id, file skipped (no debugging symbols found)...done. Rebuilding the package with binutils 2.31 installed fixes the issue. Googling for the warning lead to an arch bug pointing out that upstream commit as fixing the issue https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1815774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
Thank you for the effort (I'm adding to my list to check why apport is
not working in that context)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815774] Re: binutils 2.32 update breaks debug symbols in disco
** Also affects: binutils (Ubuntu Disco) Importance: High Status: Confirmed ** Tags removed: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1815774 Title: binutils 2.32 update breaks debug symbols in disco Status in Apport: New Status in binutils package in Ubuntu: Invalid Status in gdb package in Ubuntu: Fix Released Status in binutils source package in Disco: Invalid Status in gdb source package in Disco: Fix Released Bug description: Recently retracing started failing in disco, that seems to be due to the binutils 2.32 update example $ gdb gnome-control-center ... Reading symbols from gnome-control-center...BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: unable to initialize decompress status for section .debug_aranges BFD: /usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug: unable to initialize decompress status for section .debug_aranges warning: File "/usr/lib/debug/.build-id/2a/4367ded6c5ba5f464c762f1576874694053c71.debug" has no build-id, file skipped (no debugging symbols found)...done. Rebuilding the package with binutils 2.31 installed fixes the issue. Googling for the warning lead to an arch bug pointing out that upstream commit as fixing the issue https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5f6c22ae To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1815774/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
It took some effort getting a backtrace (apport didn't pick it up, for
some reason, so I had to resort to systemd-corectl), but anyway, here is
is. I'll add it to the upstream bug, too.
** Attachment added: "backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+attachment/5238664/+files/backtrace.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815480] Re: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
Ok, in fact I can confirm on cosmic and updating libarchive to the current disco version fixes it, https://launchpad.net/ubuntu/+source/libarchive/3.3.3-4/+build/16358983/+files/libarchive13_3.3.3-4_amd64.deb so it's fixed in the current Ubuntu serie. Could be a bug to SRU fix if someone was wanting to find the corresponding libarchive commit ** Package changed: nautilus (Ubuntu) => libarchive (Ubuntu) ** Changed in: libarchive (Ubuntu) Status: Incomplete => 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/1815480 Title: “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud Status in libarchive package in Ubuntu: Fix Released Bug description: For any .zip archive generated by the ownCloud software, it seems that extracting the files using Nautilus results in correctly-named directories/files to be created, but all files are actually empty (0 bytes). The archive can be extracted without issues using file-roller, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1815480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814506] Re: Use nemo-desktop to draw desktop icons under Unity (Disco)
Just a comment, does that mean that two file managers will always be run in the background? If so, why not just use nemo and drop nautilus completely? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1814506 Title: Use nemo-desktop to draw desktop icons under Unity (Disco) Status in ubuntu-settings package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: As nautilus > 3.30 is now uploaded in Ubuntu 19.10, it doesn't have the desktop any more. The alternate options are to use caja-desktop or nemo-desktop keeping nautilus default file manger for now. Since nemo- desktop does not require any extensive patching it is easy to use under unity. Nemo-desktop will only draw the icons, not the background. In absence of nautilus unity-settings-daemon draws the background, so nothing to do in u-s-d. There are few small patches (nemo action files) required from nemo. @fossfreedom (ubuntu-budgie-dev) suggested that it's better that we ship these action files ourselves as recommended by upstream. Budgie is doing the same. https://github.com/UbuntuBudgie/budgie-desktop-environment/tree/master/nemo-actions Since nautilus still be default file-manager we disable auto-mount with nemo and various other cinnamon/nemo option in ubuntu-settings.gsettings-override To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1814506/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815480] [NEW] “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud
You have been subscribed to a public bug: For any .zip archive generated by the ownCloud software, it seems that extracting the files using Nautilus results in correctly-named directories/files to be created, but all files are actually empty (0 bytes). The archive can be extracted without issues using file-roller, unzip or 7z: $ unzip -t test.zip Archive: test.zip testing: test/OK testing: test/f1.txt OK testing: test/f2.txt OK testing: test/f3.txt OK No errors detected in compressed data of test.zip. $ unzip test Archive: test.zip creating: test/ extracting: test/f1.txt extracting: test/f2.txt extracting: test/f3.txt $ 7z x test.zip 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (306D4),ASM,AES-NI) Scanning the drive for archives: 1 file, 8656 bytes (9 KiB) Extracting archive: test.zip -- Path = test.zip Type = zip Physical Size = 8656 64-bit = + Everything is Ok Folders: 1 Files: 3 Size: 7850 Compressed: 8656 Expected behavior: Download the attached file “test.zip”, right-click the file in Nautilus and choose “Extract Here”. A directory “test” containing three non-empty files “f1.txt”, “f2.txt” and “f3.txt” should be created. Actual behavior: All three files are empty (0 bytes). Nautilus version: 1:3.26.4-0ubuntu7.1 (cosmic) ** Affects: libarchive (Ubuntu) Importance: Low Status: Fix Released ** Tags: cosmic -- “Extract Here” only creates empty files (0 bytes) for .zip files created by ownCloud https://bugs.launchpad.net/bugs/1815480 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libarchive 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 1783499] Re: systemd: Failed to send signal
After 5 hours of reboot the server is stuck. See the attached debug log and ILO capture. ** Attachment added: "Ubuntu-18.zip" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5238635/+files/Ubuntu-18.zip -- 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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults
Uploaded fix for Bionic, it is now waiting for approval in the queue: https://launchpad.net/ubuntu/bionic/+queue?queue_state=1 Will someone be able to test a Cosmic fix if I do it? ** Description changed: - All kde applications shipped with ubuntu and particularly kubuntu bionic - print via the qt print dialog, that, unfortunately, does not seem to - respect the defaults set for the printer. + [Impact] + All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. + [Test Case] + 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. + + 2) Open a PDF with okular, and open the print dialog. Select the printer + above. + + 3) Press the "Options" button to enlarge the dialog to also present the + options. Select the "options" tab, right of "copies". Verify that Duplex + Printing is preset to "None" + + This is wrong, because the printer was configured to do duplex with + long-edge binding. + + 4) Print and close okular. + + 5) Reopen okular (with the same or another PDF file). Open again the + print dialog and select the same printer. + + 6) Redo 3). Again see that Duplex Printing is preset to "None", instead + of being at the default or at the previously used setup. + + [Regression Potential] + The proposed patch only changes the default settings. The regression potential may be that the values are wrong, although they are already wrong. + + In case there is some bug it may lead to crashes. But this code is in + the latest stable Qt release and I am not aware of any such crashes + reported. + + [Other Info] + The proposed patch is a backport of the following upstream commits: + - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3 + - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e + + [Original Description] See also https://bugs.kde.org/show_bug.cgi?id=395150 As a final comment and in general, I think that Bionic should be updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as possible (at least via a kubuntu ppa). The QT 5 print dialog has always been extremely poor, with no possibility to provide information about things like print quality and resolution, paper type, stapling (for printers supporting it), etc. Now, QT 5.11 has finally a better print dialog and it would be great if the bionic users could use it. - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: libqt5widgets5 5.9.5+dfsg-0ubuntu1 - ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 - Uname: Linux 4.15.0-22-generic x86_64 - ApportVersion: 2.20.9-0ubuntu7.2 - Architecture: amd64 - CurrentDesktop: KDE - Date: Mon Jun 11 10:23:53 2018 - EcryptfsInUse: Yes - InstallationDate: Installed on 2013-12-12 (1641 days ago) - InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) - SourcePackage: qtbase-opensource-src - UpgradeStatus: Upgraded to bionic on 2018-06-08 (2 days ago) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1776173 Title: qt print dialog shipped with bionic ignores printer defaults Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src source package in Cosmic: New Bug description: [Impact] All kde applications shipped with ubuntu and particularly kubuntu bionic print via the qt print dialog, that, unfortunately, does not seem to respect the defaults set for the printer. Specifically, every time one starts to print the "duplex" option gets reset to "none" even for those printers that were configured for "long edge" duplex by default. This may lead to a huge *waste of paper*: people print, expecting the duplex, do not get it, throw away the printout and reprint, for a total of 3 times the paper usage if the print dialog respected the default. [Test Case] 1) Install a printer that can duplex and configure it to do duplex with long-edge binding from the printer setup dialog. 2) Open a PDF with okular, and open the print dialog. Select the printer above. 3) Press the "Options" button to enlarge the dialog to also present the options. Select the "options" tab, right of "copies". Verify that Duplex Printing is preset to "None" This is wrong,
[Touch-packages] [Bug 1815125] Re: constant video freezes in firefox with x-x-v-amdgpu 18.1.0
I've tested it on a 'vega 8 mobile' laptop with glxgears. Without the fix the session would freeze periodically, after installing the update and restarting gnome-shell things work fine. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1815125 Title: constant video freezes in firefox with x-x-v-amdgpu 18.1.0 Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Bug description: [Impact] There are constant video freezes in firefox (e.g. on youtube) with xf86-video-amdgpu-18.1.0, which is included in the HWE stack in 18.04.2 https://bugs.freedesktop.org/show_bug.cgi?id=107992 [Test case] test firefox with youtube on radeon [Regression potential] it's a single commit from upstream 1.6.7, shouldn't regress anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1815125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806246] Re: Unable to turn off 2 and more openvpn-connections via Network Manager
** Package changed: network-manager (Ubuntu) => network-manager-openvpn (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1806246 Title: Unable to turn off 2 and more openvpn-connections via Network Manager Status in network-manager-openvpn package in Ubuntu: New Bug description: Have some openvpn-connections. If started 2 or more connection and try to stop all connections, will stoped only last started connection. And first started connection unable to stop from GUI. Also unable to stop definite connection, only last started. Forced to use nmcli. Ubuntu 18.04. network-manager-1.10.6 network-manager-gnome-1.8.10 network-manager-openvpn-1.8.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1806246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1809614] Re: Lubuntu 18.04 ICS not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: network-manager (Ubuntu) Importance: Undecided => Low ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1809614 Title: Lubuntu 18.04 ICS not working Status in network-manager package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.1 LTS Release: 18.04 network-manager: Installed: 1.10.6-2ubuntu1.1 Candidate: 1.10.6-2ubuntu1.1 Version table: *** 1.10.6-2ubuntu1.1 500 500 http://us.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 1.10.6-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages ICS does NOT work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down your problem.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco
Reported upstream also on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/124
, they might have a clue even without the backtrace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfaults in disco
Status in network-manager package in Ubuntu:
Incomplete
Bug description:
When I updated to the latest version of networkmanager in disco dingo
(1.15.2-0ubuntu1), it started segfaulting. Reverting to the version
in cosmic (1.12.4-1ubuntu1.2) solved the problem.
Syslog shows the following (will attach a more complete log):
feb 13 10:39:45 regan NetworkManager[2315]:
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
assertion failed: __extension__ ({ GTypeInstance *__inst =
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class &&
__inst->g_class->g_type == __t) __r = (!(0)); else __r =
g_type_check_instance_is_a (__inst, __t); __r; })
feb 13 10:39:45 regan NetworkManager[2315]: [1550050785.3612]
ifupdown: management mode: managed
feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type
'(null)' in cast to 'NMSettingsConnection'
feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=6/ABRT
---
ProblemType: Bug
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
CurrentDesktop: GNOME
DistroRelease: Ubuntu 19.04
InstallationDate: Installed on 2016-12-22 (782 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
Package: network-manager 1.12.4-1ubuntu1.2
PackageArchitecture: amd64
Tags: disco
Uname: Linux 4.19.0-1-amd64 x86_64
UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev
sambashare scanner src sudo tss wireshark
_MarkForUpload: True
mtime.conffile..etc.NetworkManager.NetworkManager.conf:
2018-06-01T16:38:44.962715
nmcli-nm:
RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW
WIFI WWAN-HW WWAN
running 1.12.4 connected started full enabled enabled
enabled enabled enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815901] Re: Service: Group name with whitespace not working anymore
** 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/1815901 Title: Service: Group name with whitespace not working anymore Status in systemd package in Ubuntu: Confirmed Bug description: On Ubuntu 16.04.x, I have a perfectly working custom systemd service file which sets username and group for the service as [Service] User=user Group=domain users where both group and user come from an AD domain joined to with winbind. This is not working anymore on 18.04. Even with the group name quoted, or mangled with systemd-escape. The service doesn't start with one of the following messages in the journal (depending on how it's spelled): /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain users /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: "domain users" /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\x20users /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\ users The only thing that works is to use the GID instead of the group name. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Feb 14 12:58:59 2019 InstallationDate: Installed on 2019-01-28 (16 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/he--puppet--dev04-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1815901/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot
Actually, the line which works without specifying a PATH in a cron.d file is the following: @reboot root /bin/sleep 5 && /sbin/sysctl --system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot
I feel it's important to add that the very last comment (Stanley Sisneros (stanley-sisneros) wrote on 2018-05-30) is wrong, and the right workaround is by Tomasz Konefal (twkonefal-j) wrote on 2018-05-07. That is, add this to crontab: @reboot root sleep 5 && sysctl --system -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
This bug was fixed in the package linux-oem - 4.15.0-1033.38
---
linux-oem (4.15.0-1033.38) bionic; urgency=medium
* linux-oem: 4.15.0-1033.38 -proposed tracker (LP: #1814241)
* Packaging resync (LP: #1786013)
- [Packaging] update update.conf
[ Ubuntu: 4.15.0-45.48 ]
* linux: 4.15.0-45.48 -proposed tracker (LP: #1813779)
* External monitors does not work anymore 4.15.0-44 (LP: #1813663)
- SAUCE: Revert "drm/i915/dp: Send DPCD ON for MST before phy_up"
* kernel 4.15.0-44 cannot mount ext4 fs with meta_bg enabled (LP: #1813727)
- ext4: fix false negatives *and* false positives in
ext4_check_descriptors()
linux-oem (4.15.0-1032.37) bionic; urgency=medium
* linux-oem: 4.15.0-1032.37 -proposed tracker (LP: #1811421)
* Fix non-working pinctrl-intel (LP: #1811777)
- pinctrl: intel: Implement intel_gpio_get_direction callback
- pinctrl: intel: Do pin translation when lock IRQ
- pinctrl: intel: Do pin translation in other GPIO operations as well
- Revert "pinctrl: intel: Do pin translation when lock IRQ"
* Fix not working Goodix touchpad (LP: #1811929)
- HID: i2c-hid: Disable runtime PM on Goodix touchpad
* Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-44.47
[ Ubuntu: 4.15.0-44.47 ]
* linux: 4.15.0-44.47 -proposed tracker (LP: #1811419)
* Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
* CPU hard lockup with rigorous writes to NVMe drive (LP: #1810998)
- blk-wbt: pass in enum wbt_flags to get_rq_wait()
- blk-wbt: Avoid lock contention and thundering herd issue in wbt_wait
- blk-wbt: move disable check into get_limit()
- blk-wbt: use wq_has_sleeper() for wq active check
- blk-wbt: fix has-sleeper queueing check
- blk-wbt: abstract out end IO completion handler
- blk-wbt: improve waking of tasks
* To reduce the Realtek USB cardreader power consumption (LP: #1811337)
- mmc: sdhci: Disable 1.8v modes (HS200/HS400/UHS) if controller can't
support
1.8v
- mmc: core: Introduce MMC_CAP_SYNC_RUNTIME_PM
- mmc: rtsx_usb_sdmmc: Don't runtime resume the device while changing led
- mmc: rtsx_usb: Use MMC_CAP2_NO_SDIO
- mmc: rtsx_usb: Enable MMC_CAP_ERASE to allow erase/discard/trim requests
- mmc: rtsx_usb_sdmmc: Re-work runtime PM support
- mmc: rtsx_usb_sdmmc: Re-work card detection/removal support
- memstick: rtsx_usb_ms: Add missing pm_runtime_disable() in probe function
- misc: rtsx_usb: Use USB remote wakeup signaling for card insertion
detection
- memstick: Prevent memstick host from getting runtime suspended during card
detection
- memstick: rtsx_usb_ms: Use ms_dev() helper
- memstick: rtsx_usb_ms: Support runtime power management
* Support non-strict iommu mode on arm64 (LP: #1806488)
- iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
- iommu/arm-smmu-v3: Implement flush_iotlb_all hook
- iommu/dma: Add support for non-strict mode
- iommu: Add "iommu.strict" command line option
- iommu/io-pgtable-arm: Add support for non-strict mode
- iommu/arm-smmu-v3: Add support for non-strict mode
- iommu/io-pgtable-arm-v7s: Add support for non-strict mode
- iommu/arm-smmu: Support non-strict mode
* ELAN900C:00 04F3:2844 touchscreen doesn't work (LP: #1811335)
- pinctrl: cannonlake: Fix community ordering for H variant
- pinctrl: cannonlake: Fix HOSTSW_OWN register offset of H variant
* Add Cavium ThunderX2 SoC UNCORE PMU driver (LP: #1811200)
- perf: Export perf_event_update_userpage
- Documentation: perf: Add documentation for ThunderX2 PMU uncore driver
- drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver
- [Config] New config CONFIG_THUNDERX2_PMU=m
* Update hisilicon SoC-specific drivers (LP: #1810457)
- SAUCE: Revert "net: hns3: Updates RX packet info fetch in case of multi
BD"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: separate roce from nic when
resetting"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Use roce handle when calling
roce
callback function"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add calling roce callback
function when link status change"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: optimize the process of
notifying
roce client"
- Revert "UBUNTU: SAUCE: {topost} net: hns3: Add pf reset for hip08 RoCE"
- scsi: hisi_sas: Remove depends on HAS_DMA in case of platform dependency
- ethernet: hisilicon: hns: hns_dsaf_mac: Use generic eth_broadcast_addr
- scsi: hisi_sas: consolidate command check in hisi_sas_get_ata_protocol()
- scsi: hisi_sas: remove some unneeded structure members
- scsi: hisi_sas: Introduce hisi_sas_phy_set_linkrate()
- net: hns: Fix the process of adding broadcast addresses to tcam
- net: hns3: remove redundant variable 'protocol'
- scsi: hisi_sas: Drop hisi_sas_slot_abort()
- net: hns: Make
[Touch-packages] [Bug 1815693] Re: Kubuntu 18.10 Xorg severe memory leak
** Description changed: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills and linked is a log of constantly increasing Xorg memory usage. So it goes until it chokes the machine and only a hard reboot is possible. My installed RAM is 10GB. Swap is 6GB. Please refer to the linked file to see how the Xorg usage creeps up. https://www.dropbox.com/s/nf1ev2dxdlc6gqw/xorg_leak.log?dl=0 Please advise what additional information I should post to have this resolved. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Wed Feb 13 01:00:13 2019 DistUpgraded: 2019-02-09 11:54:01,040 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: cosmic DistroVariant: ubuntu - ExtraDebuggingInterest: No + ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2015-10-22 (1209 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic root=UUID=8959cd47-b52f-4a6e-97bb-5d509e3c2480 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to cosmic on 2019-02-09 (3 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- 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/1815693 Title: Kubuntu 18.10 Xorg severe memory leak Status in xorg package in Ubuntu: New Bug description: Suddenly sometimes during the past two weeks my kubuntu installation has started to freeze up. I can't remember what apt upgrade that caused it, and I have done several the last few days hoping for it to be resolved. I didn't know what was causing it as I hadn't made any other changes expect for the odd apt upgrade. Before that I had just finished a several weeks long session of intense work around the clock without having to reboot even once. Suddenly it is now freezing up within hours. Even without doing anything, just leaving the computer alone. However, yesterday I accidentally discovered that my RAM was filled up. More than filled up, even all swap was full. And before I could close anything down it froze up again. So TLDR; I have today logged the memory consumption while I was handling some bills
[Touch-packages] [Bug 1815901] [NEW] Service: Group name with whitespace not working anymore
Public bug reported: On Ubuntu 16.04.x, I have a perfectly working custom systemd service file which sets username and group for the service as [Service] User=user Group=domain users where both group and user come from an AD domain joined to with winbind. This is not working anymore on 18.04. Even with the group name quoted, or mangled with systemd-escape. The service doesn't start with one of the following messages in the journal (depending on how it's spelled): /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain users /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: "domain users" /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\x20users /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\ users The only thing that works is to use the GID instead of the group name. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Feb 14 12:58:59 2019 InstallationDate: Installed on 2019-01-28 (16 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/he--puppet--dev04-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1815901 Title: Service: Group name with whitespace not working anymore Status in systemd package in Ubuntu: New Bug description: On Ubuntu 16.04.x, I have a perfectly working custom systemd service file which sets username and group for the service as [Service] User=user Group=domain users where both group and user come from an AD domain joined to with winbind. This is not working anymore on 18.04. Even with the group name quoted, or mangled with systemd-escape. The service doesn't start with one of the following messages in the journal (depending on how it's spelled): /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain users /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: "domain users" /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\x20users /lib/systemd/system/myservice.service:11: Invalid user/group name or numeric ID: domain\ users The only thing that works is to use the GID instead of the group name. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.12 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Feb 14 12:58:59 2019 InstallationDate: Installed on 2019-01-28 (16 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=xterm-256color LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/he--puppet--dev04-root ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1787440] Re: systemd 237-3ubuntu10 ADT test failure with linux 4.18.0-5.6
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-bionic -- 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/1787440 Title: systemd 237-3ubuntu10 ADT test failure with linux 4.18.0-5.6 Status in systemd package in Ubuntu: New Bug description: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/i386/s/systemd/20180816_145803_9e627@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-unstable/cosmic/s390x/s/systemd/20180816_140152_9e627@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787440/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815894] [NEW] the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173)
Public bug reported: modem manger not working with usb modem Huawei E173 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:52:34 2019 InstallationDate: Installed on 2018-10-18 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1815894 Title: the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173) Status in modemmanager package in Ubuntu: New Bug description: modem manger not working with usb modem Huawei E173 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:52:34 2019 InstallationDate: Installed on 2018-10-18 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1815894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815894] Re: the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173)
please your help if there is any solution -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1815894 Title: the modem itself is recognized by modem-manger but fail to connect to Internet (USB Modem HUAWEL E173) Status in modemmanager package in Ubuntu: New Bug description: modem manger not working with usb modem Huawei E173 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: modemmanager 1.6.8-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:52:34 2019 InstallationDate: Installed on 2018-10-18 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: modemmanager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1815894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1758736] Re: [USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only mono playback
This bug was fixed in the package pulseaudio - 1:12.2-2ubuntu1
---
pulseaudio (1:12.2-2ubuntu1) disco; urgency=medium
* Add steelseries headset support. This provides sufficient support to
enable the Steelseries Arctis 5 and 7 Gaming Headsets (LP: #1758736).
-- Dave Chiluk Tue, 12 Feb 2019 00:50:27 -0600
** Changed in: pulseaudio (Ubuntu Disco)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo playback only
mono playback
Status in pulseaudio package in Ubuntu:
Fix Released
Status in pulseaudio source package in Bionic:
In Progress
Status in pulseaudio source package in Cosmic:
In Progress
Status in pulseaudio source package in Disco:
Fix Released
Bug description:
[Impact]
* User is only able to get mono audio from steelseries headsets
because they provide both a stereo and mono output. PA selects the
mono output by default.
* This should be backported to stable releases because this fix is
isolated to code that only applies to the affected headsets.
Additionally other gaming headsets may be more easily enabled by adding
ATTRS{idVendor}=="", ATTRS{idProduct}=="",
ENV{PULSE_PROFILE_SET}="steelseries-arctis-7-usb-audio.conf"
to /lib/udev/rules.d/90-pulseaudio.rules now. Such as the Lucidsound
LS31 which I own.
* The upload fixes the bug by conditionally setting a pulseaudio
profile for the headset based on specific usb vendor and product ids
in the udev rules.
[Test Case]
1. Acquire headset.
2. Open sound settings, and click test speakers.
3. Only option available will be mono sound
[Regression Potential]
* Risk of regressions should be mitigated to those who own the
headset. In which case it is likely that their headset is already not
working.
[Other Info]
* All patches originate from upstream pulseaudio, and are documented as
such including the shas.
* I will be pursuing enabling other similar headsets in the coming weeks.
* I plan to work with upstream pulseaudio to enable my own headset and to
also make the headset templates backported here more generic.
Original Description -
There is not stereo playback only mono playback
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: pulseaudio 1:10.0-2ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: kaj1755 F...m pulseaudio
/dev/snd/controlC1: kaj1755 F pulseaudio
/dev/snd/pcmC0D0c: kaj1755 F...m pulseaudio
/dev/snd/controlC0: kaj1755 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 25 21:30:50 2018
InstallationDate: Installed on 2018-03-08 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S7 successful
Symptom_Card: SteelSeries Arctis 7 - SteelSeries Arctis 7
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [USB-Audio - SteelSeries Arctis 7, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET35W (1.09 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FMS2AV00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrR06ET35W(1.09):bd03/09/2016:svnLENOVO:pn20FMS2AV00:pvrThinkPadT460:rvnLENOVO:rn20FMS2AV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460
dmi.product.name: 20FMS2AV00
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1758736/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1628032] Re: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
The issue saw not report since 17.10 according to the error tracker, closing ** Changed in: evolution-data-server (Ubuntu) Status: Confirmed => Fix Released ** 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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1628032 Title: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() Status in evolution-data-server package in Ubuntu: Fix Released Bug description: This is an automatic bug report. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: evolution-data-server 3.21.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-16-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Tue Sep 27 17:21:52 2016 ExecutablePath: /usr/lib/evolution/evolution-calendar-factory-subprocess InstallationDate: Installed on 2015-08-05 (418 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: /usr/lib/evolution/evolution-calendar-factory-subprocess --factory local --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.Calendarx2625x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/Calendar/2625/3 ProcEnviron: LANG=ru_RU.UTF-8 LANGUAGE=ru PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SegvAnalysis: Segfault happened at: 0x7f3ad07f085c : movzbl 0x14(%rax),%edx PC (0x7f3ad07f085c) ok source "0x14(%rax)" (0x55ac0014) not located in a known VMA region (needed readable region)! destination "%edx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading unknown VMA Signal: 11 SourcePackage: evolution-data-server StacktraceTop: g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: evolution-calendar-factory-subprocess crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1628032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
** Description changed: + * Impact + Evolution doesn't work with Kopano IMAP servers: + + * Test case + Configure an account on a Kopano IMAP server and try to use it from evolution + + * Regression potential + The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly + + - + 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815881] Re: Installation fails if update-notifier is missing
II fact that's not an issue in 18.10, it was created in Debian by dropping the exit 0 call ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815881 Title: Installation fails if update-notifier is missing Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact THe postinst doesn't handle update-notifier not being installed * Test case - remove update-notifier - install evolution-data-server The installation should not error out in the postinst * Regression potential The change is only to add a || true to the update-notifier command in the postinst, it shouldn't impact on anything (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813268] Re: connection issues with Kopano IMAP servers
The fix is in the current disco version and being SRUed to 18.10 ** Changed in: evolution-data-server (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 evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Bug description: 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815881] [NEW] Installation fails if update-notifier is missing
Public bug reported: * Impact THe postinst doesn't handle update-notifier not being installed * Test case - remove update-notifier - install evolution-data-server The installation should not error out in the postinst * Regression potential The change is only to add a || true to the update-notifier command in the postinst, it shouldn't impact on anything (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603) ** Affects: evolution-data-server (Ubuntu) Importance: Low Status: Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815881 Title: Installation fails if update-notifier is missing Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact THe postinst doesn't handle update-notifier not being installed * Test case - remove update-notifier - install evolution-data-server The installation should not error out in the postinst * Regression potential The change is only to add a || true to the update-notifier command in the postinst, it shouldn't impact on anything (see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911603) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815882] [NEW] Update evolution-data-server to 3.30.5
Public bug reported: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. ** Affects: evolution-data-server (Ubuntu) Importance: High Status: Fix Released ** Changed in: evolution-data-server (Ubuntu) Importance: Undecided => High ** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1815862] Re: test bug
** Changed in: apport Status: New => Invalid ** Changed in: apport (Ubuntu) Status: New => Invalid -- 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/1815862 Title: test bug Status in Apport: Invalid Status in apport package in Ubuntu: Invalid Bug description: test bug ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: apport 2.20.10-0ubuntu20 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CrashReports: 640:1000:119:4491999:2019-02-14 11:28:54.686578636 +0600:2019-02-14 11:34:26.810664197 +0600:/var/crash/_usr_bin_gnome-control-center.1000.crash CurrentDesktop: ubuntu:GNOME Date: Thu Feb 14 12:53:06 2019 InstallationDate: Installed on 2019-02-14 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to disco on 2019-02-14 (0 days ago) mtime.conffile..etc.default.apport: 2019-02-14T12:51:16.243720 To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1815862/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1814105] Re: random 404s on security.ubuntu.com for libavahi packages
Yeah I noticed, thanks -- 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/1814105 Title: random 404s on security.ubuntu.com for libavahi packages Status in avahi package in Ubuntu: Invalid Bug description: Hi, when I try to apt-get upgrade from xenial-security I get 404s from some of the security.ubuntu.com mirrors. Not sure if this is the place to report it but it seems to be related to https://launchpad.net/ubuntu/+source/avahi/0.6.32~rc+dfsg- 1ubuntu2.3/+publishinghistory. ``` root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:19-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.161, 91.189.88.152, 91.189.88.149, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.161|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-01-31 13:48:19 ERROR 404: Not Found. root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:20-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.161, 91.189.88.152, 91.189.88.149, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.161|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-01-31 13:48:20 ERROR 404: Not Found. root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:20-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.152, 91.189.91.26, 91.189.91.23, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.152|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 21452 (21K) [application/x-debian-package] Saving to: ‘libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.1’ libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.1 100%[==>] 20.95K --.-KB/sin 0.02s 2019-01-31 13:48:21 (1.21 MB/s) - ‘libavahi-common-data_0.6.32~rc +dfsg-1ubuntu2.3_amd64.deb.1’ saved [21452/21452] root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:22-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.152, 91.189.88.149, 91.189.88.161, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.152|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 21452 (21K) [application/x-debian-package] Saving to: ‘libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.2’ libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.2 100%[==>] 20.95K --.-KB/sin 0.03s 2019-01-31 13:48:23 (664 KB/s) - ‘libavahi-common-data_0.6.32~rc+dfsg- 1ubuntu2.3_amd64.deb.2’ saved [21452/21452] root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:24-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.162, 91.189.91.23, 91.189.88.152, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.162|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-01-31 13:48:24 ERROR 404: Not Found. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1814105/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Kris B. I think this november update changed in some way / ownership. Also I tryed to test it and it recurrenced, if I was not loged in as root, but I did as user sudo apt-get upgrade To fix it try this, log in as root: chown root:root / -- 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 1814105] Re: random 404s on security.ubuntu.com for libavahi packages
Forgot to comment: This issue was resolved by the Mirror team shortly after -- 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/1814105 Title: random 404s on security.ubuntu.com for libavahi packages Status in avahi package in Ubuntu: Invalid Bug description: Hi, when I try to apt-get upgrade from xenial-security I get 404s from some of the security.ubuntu.com mirrors. Not sure if this is the place to report it but it seems to be related to https://launchpad.net/ubuntu/+source/avahi/0.6.32~rc+dfsg- 1ubuntu2.3/+publishinghistory. ``` root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:19-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.161, 91.189.88.152, 91.189.88.149, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.161|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-01-31 13:48:19 ERROR 404: Not Found. root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:20-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.161, 91.189.88.152, 91.189.88.149, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.161|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-01-31 13:48:20 ERROR 404: Not Found. root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:20-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.152, 91.189.91.26, 91.189.91.23, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.152|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 21452 (21K) [application/x-debian-package] Saving to: ‘libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.1’ libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.1 100%[==>] 20.95K --.-KB/sin 0.02s 2019-01-31 13:48:21 (1.21 MB/s) - ‘libavahi-common-data_0.6.32~rc +dfsg-1ubuntu2.3_amd64.deb.1’ saved [21452/21452] root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:22-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.152, 91.189.88.149, 91.189.88.161, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.152|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 21452 (21K) [application/x-debian-package] Saving to: ‘libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.2’ libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb.2 100%[==>] 20.95K --.-KB/sin 0.03s 2019-01-31 13:48:23 (664 KB/s) - ‘libavahi-common-data_0.6.32~rc+dfsg- 1ubuntu2.3_amd64.deb.2’ saved [21452/21452] root@okok-blabla-magweb-cmbl ~ # wget http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb --2019-01-31 13:48:24-- http://security.ubuntu.com/ubuntu/pool/main/a/avahi/libavahi-common-data_0.6.32~rc+dfsg-1ubuntu2.3_amd64.deb Resolving security.ubuntu.com (security.ubuntu.com)... 91.189.88.162, 91.189.91.23, 91.189.88.152, ... Connecting to security.ubuntu.com (security.ubuntu.com)|91.189.88.162|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2019-01-31 13:48:24 ERROR 404: Not Found. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1814105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
