[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk
Thank you Will! We are running Ubuntu 16.04 with network-manager version 1.2.6, that will be fixed too? -- 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/1796622 Title: NetworkManager IPv6 DAD lifetime behavior introduce security risk Status in network-manager package in Ubuntu: New Bug description: Description: When performing IPv6 certification test, two DAD test cases (3.2.5c and d) check the remaining lifetime feature of the IPv6 packets. The Network trace shows that the remaining lifetime becomes infinite when running these test cases. Hence when running in IPv6 environment with Network Manager enabled, there is a risk of packets travelling in network which has valid lifetime always. If these packets are snooped by a hacker he can reply to these packets and they can send legitimate packets which are actually not. According to https://tools.ietf.org/search/rfc4862, page 19: "The above rules address a specific denial-of-service attack in which a bogus advertisement could contain prefixes with very small Valid Lifetimes. Without the above rules, a single unauthenticated advertisement containing bogus Prefix Information options with short Valid Lifetimes could cause all of a node's addresses to expire prematurely. The above rules ensure that legitimate advertisements (which are sent periodically) will "cancel" the short Valid Lifetimes before they actually take effect." Other notes: - 2 test cases pass without NetworkManager. - Tested with different Linux Desktop Distributions, as long as NetworkManager is running, those DAD test cases fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Just another "me too". Renamed the file to bak, and had a semi-working system. Also had to reinstall Nvidia driver since i was stuck at 640x480, that was fun -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Committed Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Committed Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 63 files and directories currently installed.) Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): subprocess installed post-removal script returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) Commenting out the dpkg-divert in systemd-shim's postrm solved this for me and I was about to continue the upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
** Description changed: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. - gdm3 can be started manually from a tty + gdm3 can be started manually from a tty. + Switching to another tty then back also starts gdm. When this issue happens there is a plymouth crash reported in bug 1794292 - ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 ** Description changed: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty. Switching to another tty then back also starts gdm. - When this issue happens there is a plymouth crash reported in bug - 1794292 + It happens on bare metal and VM. + + Originally, when this issue happened there was a plymouth crash reported + in bug 1794292 but this issue is still happening without the plymouth + crash. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Won't Fix Status in kmod package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-video-fbdev package in Ubuntu: Fix Released Status in gdm3 source package in Cosmic: Won't Fix Status in kmod source package in Cosmic: Invalid Status in linux source package in Cosmic: Invalid Status in xorg-server source package in Cosmic: Confirmed Status in xserver-xorg-video-fbdev source package in Cosmic: Fix Released Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty. Switching to another tty then back also starts gdm. It happens on bare metal and VM. Originally, when this issue happened there was a plymouth crash reported in bug 1794292 but this issue is still happening without the plymouth crash. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot
IMHO if a "match" option is present (especially with a MAC condition),
it should always override the ID.
--
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/1770082
Title:
systemd-networkd not renaming devices on boot
Status in netplan:
Fix Released
Status in cloud-init package in Ubuntu:
Confirmed
Status in netplan.io package in Ubuntu:
Fix Released
Status in nplan package in Ubuntu:
Fix Released
Status in systemd package in Ubuntu:
Confirmed
Status in nplan source package in Xenial:
Fix Released
Status in netplan.io source package in Bionic:
Fix Committed
Bug description:
[Impact]
Systems relying on renaming network interfaces at boot and when 'netplan
apply' is run.
[Test case]
- Write a new netplan YAML (adjusting for current system as necessary):
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: myif0
- Run 'netplan apply'
- Verify that the device is correctly renamed to 'myif0'.
- Reboot.
- Make sure the device is correctly renamed to 'myif0'.
[Regression potential]
Changes in rename logic to add udev rules may otherwise impact applying
different settings to the network interfaces. Changes in settings on network
interfaces, missing parameters (especially on bonds, bridges) should be
investigated as potential regressions. Other failures to apply network settings
might also happen if there's a race between applying renames via the udev
rules, and using the new names to apply configuration changes to the interfaces.
=== systemd issue ===
Renaming devices doesn't seem to work.
If I disable all other network configuration and create
/etc/systemd/network/10-network.link with:
[Match]
MACAddress=52:54:00:c1:c9:bb
[Link]
Name=myiface3
I expect this to cause the device with that MAC address to be renamed
to myiface3. However, when I reboot, I instead see:
$ ip l
1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3: mtu 1500 qdisc noop state DOWN mode DEFAULT
group default qlen 1000
link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
The device is not renamed.
This link file is pretty much identical to Example 2 in
https://www.freedesktop.org/software/systemd/man/systemd.link.html.
The renaming does work if I boot with net.ifnames=0, and oddly, it
also works if I unbind the device and rebind it as netplan apply does.
No setting of NamePolicy seems to help.
=== Original Bug ==
'set-name:' doesn't change the name of a network interface on boot, it
only works when you do netplan apply.
Say I take this 50-cloud-init.yaml file:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
ens3:
dhcp4: true
match:
macaddress: 52:54:00:de:bd:f6
set-name: ens3
Say I change set-name to 'myiface3' and reboot. I expect that the
device will be called myiface3 and brought up fine with dhcp. However,
instead I see:
$ ip a
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens3: mtu 1500 qdisc noop state DOWN group default
qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
The name has not been changed, and the device has not been brought up.
If I run netplan apply however, I see the following:
1: lo: mtu 65536 qdisc noqueue state UNKNOWN group
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: myiface3: mtu 1500 qdisc fq_codel state
UP group default qlen 1000
link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
valid_lft 3575sec preferred_lft 3575sec
inet6 fe80::5054:ff:fede:bdf6/64 scope link
valid_lft forever preferred_lft forever
So names are successfully changed with netplan apply.
This seems to be some udev-related timing or priority issue that I'm
still trying to hunt down.
This breaks some forms of mig
[Touch-packages] [Bug 1797518] [NEW] System freezes after suspend
Public bug reported: Linux Version: 4.15.0-36-generic After login or during login the screen freezes. Mouse does not move any longer. Total crash/hang this is new since about 3 weeks or so. All updates are installed. I attached kern.log, about 9:14 this morning I had to reboot again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 09:30:00 2018 DistUpgraded: 2018-07-08 17:00:19,279 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 640 OEM] [1043:8597] InstallationDate: Installed on 2018-05-28 (136 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. M70AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=2fab21eb-af61-44eb-8a0a-f863dcc151ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-08 (95 days ago) dmi.bios.date: 03/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M70AD 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.:bvr0802:bd03/19/2014:svnASUSTeKCOMPUTERINC.:pnM70AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM70AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: M70AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jul 9 17:58:45 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session ** Attachment added: "Logfile" https://bugs.launchpad.net/bugs/1797518/+attachment/5200248/+files/kern.log -- 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/1797518 Title: System freezes after suspend Status in xorg package in Ubuntu: New Bug description: Linux Version: 4.15.0-36-generic After login or during login the screen freezes. Mouse does not move any longer. Total crash/hang this is new since about 3 weeks or so. All updates are installed. I attached kern.log, about 9:14 this morning I had to reboot again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 09:30:00 2018 DistUpgraded: 2018-07-08 17:00:19,279 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 640 OEM] [1043:8597] InstallationDate: Installed on 2018-05-28 (136 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. M70AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=2fab21eb-af61-44eb-8a0a-f863dcc151ee ro
[Touch-packages] [Bug 1797518] Re: System freezes after suspend
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1797518 Title: System freezes after suspend Status in Ubuntu: Incomplete Bug description: Linux Version: 4.15.0-36-generic After login or during login the screen freezes. Mouse does not move any longer. Total crash/hang this is new since about 3 weeks or so. All updates are installed. I attached kern.log, about 9:14 this morning I had to reboot again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 09:30:00 2018 DistUpgraded: 2018-07-08 17:00:19,279 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GT 640 OEM] [10de:0fc0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK107 [GeForce GT 640 OEM] [1043:8597] InstallationDate: Installed on 2018-05-28 (136 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK COMPUTER INC. M70AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=2fab21eb-af61-44eb-8a0a-f863dcc151ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-08 (95 days ago) dmi.bios.date: 03/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M70AD 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.:bvr0802:bd03/19/2014:svnASUSTeKCOMPUTERINC.:pnM70AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM70AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: Desktop dmi.product.name: M70AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Mon Jul 9 17:58:45 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1797518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796622] Re: NetworkManager IPv6 DAD lifetime behavior introduce security risk
It should be yes, but I'd like to look at the changes needed before going any further. Looking at the diff, it doesnt look too bad for the current version on n-m. With some luck it will be backported by upstream, if not we'll take a look. Release of Cosmic is next week, so I dont think this will get any traction until that's out the door, but then we will get on the case. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed ** Changed in: network-manager (Ubuntu) Importance: Undecided => Medium ** Also affects: network-manager (Ubuntu Dd-series) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1796622 Title: NetworkManager IPv6 DAD lifetime behavior introduce security risk Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in DD-Series: New Bug description: Description: When performing IPv6 certification test, two DAD test cases (3.2.5c and d) check the remaining lifetime feature of the IPv6 packets. The Network trace shows that the remaining lifetime becomes infinite when running these test cases. Hence when running in IPv6 environment with Network Manager enabled, there is a risk of packets travelling in network which has valid lifetime always. If these packets are snooped by a hacker he can reply to these packets and they can send legitimate packets which are actually not. According to https://tools.ietf.org/search/rfc4862, page 19: "The above rules address a specific denial-of-service attack in which a bogus advertisement could contain prefixes with very small Valid Lifetimes. Without the above rules, a single unauthenticated advertisement containing bogus Prefix Information options with short Valid Lifetimes could cause all of a node's addresses to expire prematurely. The above rules ensure that legitimate advertisements (which are sent periodically) will "cancel" the short Valid Lifetimes before they actually take effect." Other notes: - 2 test cases pass without NetworkManager. - Tested with different Linux Desktop Distributions, as long as NetworkManager is running, those DAD test cases fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1796622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794629] Re: CVE-2018-15473 - User enumeration vulnerability
The attachment "bionic-upstream-delay-bailout-for-invalid- authenticating-user.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1794629 Title: CVE-2018-15473 - User enumeration vulnerability Status in openssh package in Ubuntu: Confirmed Bug description: https://nvd.nist.gov/vuln/detail/CVE-2018-15473 OpenSSH through 7.7 is prone to a user enumeration vulnerability due to not delaying bailout for an invalid authenticating user until after the packet containing the request has been fully parsed, related to auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c. Fixed in Debian: https://www.debian.org/security/2018/dsa-4280 Currently pending triage? https://people.canonical.com/~ubuntu- security/cve/2018/CVE-2018-15473.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797415] Re: DNS stops working when disconnecting PPTP VPN on desktop
** Tags added: rls-cc-incoming -- 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/1797415 Title: DNS stops working when disconnecting PPTP VPN on desktop Status in systemd package in Ubuntu: New Bug description: On Cosmic I was testing some VPN setups. I created a PPTP VPN connection to my server. Everything connected and worked as it should. When I disconnect the VPN, DNS resolution stops working. Looking at "systemd-resolve --status" shows that the correct DNS server is listed for the interface when the connection is torn down, and I can ping it. Doing a nslookup setting the server to the IP address shown in --status shows that DNS resolution is working correctly. resolv.conf says nameserver 127.0.0.53 Restart resolved makes things work again. (Also, restarting Network Manager makes it work again.) Trying to ping a hostname from the cli when in the broken state yields zero output from resolved logs when in debug mode. Almost like it's not even hitting resolved, so this bug could very well be somewhere else. I've checked, and I can ping 127.0.0.1 and the default routes look OK, although there is a route to the VPN server left over. I'm all out of ideas. Any ideas? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554471] Re: Mouse not working
This may be related: https://unix.stackexchange.com/questions/207999/mouse-recognized-as-keyboard-xinput-fedora-22 -- 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/1554471 Title: Mouse not working Status in xorg package in Ubuntu: Triaged Bug description: I have a Cougar 450M gaming mouse. I am dual booting between Windows 10 and Xubuntu. The mouse works perfectly in Windows but fails dismally in any flavour of Ubuntu (tried Ubuntu, Lubuntu and Xubuntu) including during the OS installation phase. On very rare occasion it will work when I boot into Ubuntu, but 9 out of 10 times the only functions available are the mouse buttons and scroll wheel. There is also a DPI adjustment button on the 450M which cycles through the various available settings and changes colour based on the current DPI setting. I have noted that if you press the button once, the button changes colour as expected, but if you continue to press the button, nothing happens. It seems to freeze on that setting. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 8 10:52:02 2016 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Pitcairn PRO [Radeon HD 7850 / R7 265 / R9 270 1024SP] [1002:6819] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:2730] InstallationDate: Installed on 2016-03-03 (4 days ago) InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Gigabyte Technology Co., Ltd. Z87-D3HP ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-30-generic.efi.signed root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87-D3HP-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd08/12/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87-D3HP:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87-D3HP-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87-D3HP dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Tue Mar 8 10:48:41 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.2-1ubuntu9.1 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1554471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op
AppArmor really should restrict NFS access only via the file-path rules, not via the network rules, since if an application accesses a file via NFS, all related network traffic is initiated and controlled by the kernel (or by kernel helper processes like automount, rpc.gssd and nfsidmap), and not by the application. Workaround (for /usr/bin/man only): Add to /etc/apparmor.d/local/usr.bin.man the lines # TCP/UDP network access for NFS network inet stream, network inet6 stream, network inet dgram, network inet6 dgram, then run # systemctl reload apparmor This really should be fixed in the kernel, but until then, perhaps adding a widely-included /etc/apparmor.d/abstractions/nfs with the above lines would be useful, as /usr/bin/man is just one example of an affected application. See also bug #1662552 -- 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/1784499 Title: AppArmor treats regular NFS file access as network op Status in apparmor package in Ubuntu: Confirmed Bug description: I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic. I have the usr.bin.man profile enforced, and home directories in NFS. The log excerpt copied below is the result of a single invocation of "man ls" by an unprivileged user. (The program did display the man page correctly to the user.) It does not seem appropriate for AppArmor to report the man(1) program as having attempted to contact the NFS server directly, when it only tried to access an NFS-served file in the normal way. "man" is not a network-aware program and the log below misleadingly implies otherwise. Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 callbacks suppressed Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 request
[Touch-packages] [Bug 1797097] Re: Missaligned border wit ComboBox in Headerbar
** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low -- 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/1797097 Title: Missaligned border wit ComboBox in Headerbar Status in ubuntu-themes package in Ubuntu: New Bug description: Hi, with ubuntu-themes_16.10+18.10.20181005 the left border of a GtkComboBox with a GtkTextEntry in the GtkHeaderbar seems to be slightly misaligned leaving an additional white space to its left. The bug isn't visible once the GtkTextEntry gets the focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1797097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797536] [NEW] libgtk-3-0:i386: gtk-query-immodules-3.0 not executable
*** This bug is a duplicate of bug 1797275 *** https://bugs.launchpad.net/bugs/1797275 Public bug reported: The gtk-3 utility "gtk-query-immodules-3.0" is installed under the libdir; however, it is not executable. It is thus unusable as described in the man page provided via package "libgtk-3-bin". |$ dpkg -S gtk-query-immodules-3.0 |libgtk-3-doc: /usr/share/doc/libgtk-3-doc/gtk3/gtk-query-immodules-3.0.html |libgtk-3-0:i386: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |libgtk-3-bin: /usr/share/man/man1/gtk-query-immodules-3.0.1.gz |$ . /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |bash: .: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: cannot execute binary file |$ ls -l /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |-rwxr-xr-x 1 root root 13672 Apr 16 20:23 /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query- |immodules-3.0 |$ file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |/usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: ELF 32-bit LSB shared object, Intel |80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, |BuildID[sha1]=b7c03cbac4882fe78ea6f0b92d1dc98dbeb13017, stripped Qualifiers: 1) |$ lsb_release -rd |Description: Linux Mint 19 Tara |Release: 19 2) |$ apt-cache policy libgtk-3-0:i386 |libgtk-3-0: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://mirror.clarkson.edu/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status 3) I expect to be able to gtk-query-immodules-3.0 as described in the man page and in Gtk+-3 documentation. 4) The file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 is present, but not executable. ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: New ** Tags: gtk-query-immodules-3.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797536 Title: libgtk-3-0:i386: gtk-query-immodules-3.0 not executable Status in gtk+3.0 package in Ubuntu: New Bug description: The gtk-3 utility "gtk-query-immodules-3.0" is installed under the libdir; however, it is not executable. It is thus unusable as described in the man page provided via package "libgtk-3-bin". |$ dpkg -S gtk-query-immodules-3.0 |libgtk-3-doc: /usr/share/doc/libgtk-3-doc/gtk3/gtk-query-immodules-3.0.html |libgtk-3-0:i386: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |libgtk-3-bin: /usr/share/man/man1/gtk-query-immodules-3.0.1.gz |$ . /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |bash: .: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: cannot execute binary file |$ ls -l /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |-rwxr-xr-x 1 root root 13672 Apr 16 20:23 /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query- |immodules-3.0 |$ file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |/usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: ELF 32-bit LSB shared object, Intel |80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, |BuildID[sha1]=b7c03cbac4882fe78ea6f0b92d1dc98dbeb13017, stripped Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-0:i386 |libgtk-3-0: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://mirror.clarkson.edu/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status 3) I expect to be able to gtk-query-immodules-3.0 as described in the man page and in Gtk+-3 documentation. 4) The file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 is present, but not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797536] Re: libgtk-3-0:i386: gtk-query-immodules-3.0 not executable
*** This bug is a duplicate of bug 1797275 *** https://bugs.launchpad.net/bugs/1797275 ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1797275 libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797536 Title: libgtk-3-0:i386: gtk-query-immodules-3.0 not executable Status in gtk+3.0 package in Ubuntu: New Bug description: The gtk-3 utility "gtk-query-immodules-3.0" is installed under the libdir; however, it is not executable. It is thus unusable as described in the man page provided via package "libgtk-3-bin". |$ dpkg -S gtk-query-immodules-3.0 |libgtk-3-doc: /usr/share/doc/libgtk-3-doc/gtk3/gtk-query-immodules-3.0.html |libgtk-3-0:i386: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |libgtk-3-bin: /usr/share/man/man1/gtk-query-immodules-3.0.1.gz |$ . /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |bash: .: /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: cannot execute binary file |$ ls -l /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |-rwxr-xr-x 1 root root 13672 Apr 16 20:23 /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query- |immodules-3.0 |$ file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 |/usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: ELF 32-bit LSB shared object, Intel |80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, |BuildID[sha1]=b7c03cbac4882fe78ea6f0b92d1dc98dbeb13017, stripped Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-0:i386 |libgtk-3-0: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://mirror.clarkson.edu/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status 3) I expect to be able to gtk-query-immodules-3.0 as described in the man page and in Gtk+-3 documentation. 4) The file /usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 is present, but not executable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797275] Re: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
What architecture do you use? Could you give the output of those commands? $ uname -a $ dpkg -l | grep libgtk-3-0 $ debsums libgtk-3-0 | grep gtk-query -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797275 Title: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts
I just want to add, this is not minor. If you don't update /etc/hosts then sudo hangs, which in our case breaks automation. -- 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/1162475 Title: [hostnamed] Changing hostname doesn't update /etc/hosts Status in gnome-control-center package in Ubuntu: Triaged Status in systemd package in Ubuntu: Triaged Status in unity-control-center package in Ubuntu: Confirmed Status in gnome-control-center package in Debian: Fix Released Bug description: GUI --- 1a. Run sudo gnome-control-center, or... 1b. Save the gnome-control-center.pkla from https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run gnome-control-center as an admin user 2. Enter the Details panel 3. The "Device name" (hostname) text field should be editable; change the text to something else. 4. The hostname is updated instantly which can be verified by looking in /etc/hostname. However /etc/hosts/ is not updated. Command line hostnamectl set-hostname The hostnamed documentation at http://www.freedesktop.org/wiki/Software/systemd/hostnamed says "To properly handle name lookups with changing local hostnames without having to edit /etc/hosts for them we recommend using hostnamed in combination with nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ " Without /etc/hosts being handled correctly, the hostnamed integration is only half-working. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-control-center 1:3.6.3-0ubuntu18 ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4 Uname: Linux 3.8.0-15-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sun Mar 31 08:52:57 2013 MarkForUpload: True SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu6.1 deja-dup26.0-0ubuntu1 gnome-control-center-signon 0.1.5-0ubuntu1 gnome-control-center-unity 1.2daily13.02.15-0ubuntu1 indicator-datetime 12.10.3daily13.03.26-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1162475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693948] Re: useless diagnostics in dpkg.log from journalctl due to ellipses
Fixed in https://salsa.debian.org/debian/init-system- helpers/commit/5836b307724f8731b47d3d4d064ada1833182705 thus the package is fixed in version debian/1.49 and later. ** Also affects: init-system-helpers (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: init-system-helpers (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: init-system-helpers (Ubuntu Xenial) Status: New => Confirmed ** Changed in: init-system-helpers (Ubuntu) Status: Confirmed => Fix Released ** Changed in: init-system-helpers (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: init-system-helpers (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1693948 Title: useless diagnostics in dpkg.log from journalctl due to ellipses Status in init-system-helpers package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in init-system-helpers source package in Bionic: Fix Released Bug description: Many of the apport hooks try to include some information about why a service didn't start correctly. One recent report included the following: May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process exited, ...a[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD Secure She[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered failed s[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with result 'e[0m Hint: Some lines were ellipsized, use -l to show in full. The actual error information is this: /etc/ssh/sshd_config line 64: miss and Failed with result 'e This is very nearly useless. We should include the -l parameter as suggested so that we stand a chance of seeing an error that doesn't occur in the first twenty characters of program output. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1693948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta
** Description changed:
[Impact]
- * When Secure Boot is enabled and a new dkms module is installed sim-
- signed asks for a new Secure Boot key, or aborts package installation in
- non-interactive mode. When unattended-upgrades performed the upgrade the
- aborted installation leaves an unconfigured system behind that may even
- fail to boot.
+ * When Secure Boot is enabled and MOK is not set and a new dkms module
+ is installed sim-signed asks for a Secure Boot MOK, or aborts package
+ installation in non-interactive mode. When unattended-upgrades performed
+ the upgrade the aborted installation leaves an unconfigured system
+ behind that may even fail to boot. In nvdidia's special case the new
+ module is actually just a new version of the nvidia module which should
+ be fine to install.
- * The fix in u-u detects new dkms-related packages and holds them back
- from installation.
+ * The fix in shim-signed now handles nvidia dkms module directory
+ renames as simple upgrades and also does not handle module removals as a
+ reason to abort installation.
- [Test Case]
+ [Test Case (shim-signed)]
+
+ WIP
+
+ [Test Case (unattended-upgrades)]
1. Set up a fully - or almost fully updated Bionic system.
2. Install packagages to trigger the block:
apt install dkms shim-signed r8168-dkms
3. Fake enabled secure boot:
echo "shim-signed shim/enable_secureboot boolean true" |
debconf-set-selections
4. Add and enable PPA hosting updated dkms package pulling in a new dkms-like
dependency:
add-apt-repository ppa:rbalint/scratch
echo 'Unattended-Upgrade::Allowed-Origins
{"LP-PPA-rbalint-scratch:${distro_codename}";}' >
/etc/apt/apt.conf.d/51unattended-upgrades-all
5. Observe u-u keeping back the new package:
unattended-upgrade --verbose --dry-run --debug
...
Checking: r8168-dkms ([])
pkg new-dkms-dep may trigger secure boot key prompt
sanity check failed
...
- [Regression Potential]
+
+ [Regression Potential (shim-signed)]
+
+ * The fix lets installation of nvidia dkms module upgrades continue and also
lets dkms module removals continue when MOK is not set and those should not
cause regressions themselves. In case of an implementation mistake a new module
installation could go undetected and could cause the system not load a dkms
module on next boot.
+ In practice not loading new modules rarely cause regressions, but if a module
is converted from being in the kernel to a dkms module upon an upgrade this is
possible.
+ * I tested the module addition, removal, nvidia module upgrade and not
module change cases with stubs pretending that the system is secure-boot
capable an found the changed script working properly.
+
+ [Regression Potential (unattended-upgrades)]
* Since the fix is holding back packages from installation it is
expected that systems that would have otherwise broke during the
installation would not receive all updates. Since exact detection of the
installation failure reported here does not seem possible u-u holds back
more packages than it would be absolutely necessary.
* Administrators are expected to set up email notifications about the
updates performed by u-u and act on held back packages.
* Since updates pulling in new packages are fairly rare especially in
the -security pocket which u-u installs from by default unwanted
regressions are unlikely to show up.
[Original Bug Text]
Occurred a minute after logging in
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 11:35:53 2017
EFITables:
Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
Oct 24 11:33:04 paddy-laptop kernel: efi: ACPI=0x7866 ACPI
2.0=0x7866 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x79360598
Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from
0x79360598 to 0x793605d0.
Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2017-09-11 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.2
apt 1.2.24
SecureBoot: 6 0 0 0 1
SourcePackage: shim-signed
Title: package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
failed to install/upgrade: subprocess installed post-installation script
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-u
[Touch-packages] [Bug 1781586] Re: Skip rebuilding python-apt in upgrade autopkgtests
1.1ubuntu1.18.04.5 rebuilding python-apt: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20180719_173343_b16b4@/log.gz ... dpkg-deb: building package 'python3-apt' in '../python3-apt_1.6.2_amd64.deb'. dpkg-deb: building package 'python3-apt-dbg' in '../python3-apt-dbg_1.6.2_amd64.deb'. dpkg-genbuildinfo dpkg-genchanges >../python-apt_1.6.2_amd64.changes ... 1.1ubuntu1.18.04.6 not rebuilding python-apt: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/u/unattended-upgrades/20181010_011153_2b8c7@/log.gz ** 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 unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1781586 Title: Skip rebuilding python-apt in upgrade autopkgtests Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Bug description: [Impact] * Python-apt has a new build dependency making the rebuilding as is failing and the reference handling issue is worked around in unattended-upgrades already. * Table updates of python-apt may make u-u autopkgtest fail without the u-u package having any problem when it is installed. [Test Case] * Check upgrade-all-security autopkgtest output, it should not rebuild the python-apt package. [Regression Potential] * Autopkgtest may fail due running it with not rebuilt python-apt. This problem can be caught easily when testing the package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
Bug #1784485 is also reporting sound problems with the same audio card as the systems in this bug, but I'm not sure if it can be duplicated to this bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 682662] Re: pam-auth-update ignores debconf settings
** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/682662 Title: pam-auth-update ignores debconf settings Status in dpkg package in Ubuntu: New Status in pam package in Ubuntu: Triaged Status in pam package in Debian: Won't Fix Bug description: pam-auth-update ignores the current debconf-settings. This makes it impossible to do automatically configure pam in noninteractive installations. Demonstration: ~ # debconf-get-selections | grep libpam-runtime libpam-runtimelibpam-runtime/override boolean true libpam-runtimelibpam-runtime/conflictserror libpam-runtimelibpam-runtime/no_profiles_chosen error libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, ldap, tmpdir, gnome-keyring, consolekit libpam-runtimelibpam-runtime/you-had-no-auth error ~ # DEBIAN_FRONTEND=noninteractive pam-auth-update ~ # debconf-get-selections | grep libpam-runtime libpam-runtimelibpam-runtime/override boolean false libpam-runtimelibpam-runtime/conflictserror libpam-runtimelibpam-runtime/no_profiles_chosen error libpam-runtimelibpam-runtime/profiles multiselect krb5, unix, winbind, ldap libpam-runtimelibpam-runtime/you-had-no-auth error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/682662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797387] Re: bash crashes on PS1 set, wait, press enter, Ctrl-C, enter
Reproduced on debian 8 but not debian 9. I will log a bug through debian also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1797387 Title: bash crashes on PS1 set, wait, press enter, Ctrl-C, enter Status in bash package in Ubuntu: New Bug description: Reproducible on xubuntu 16.04 x86_64 (reproduced on two machines I tried). Steps to reproduce: export PS1="\e[1;32m\u@$HOSTNAME \t \$()\e[1;36m\$(sleep 1)\e[m\n\w>" Press enter wait Press enter Ctrl-C Press enter bash will crash. My PS1 line calls (and forks) a little shell script to report a status I want to see. It seems to be specific to bash on 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1797387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797555] [NEW] headphone not detected on initialization
Public bug reported: every time i initialize the computer with the headphone connected, there's no sound in the headphones. i have to take the headphone off and plug it again, then i'm prompted with the ubuntu window asking if it's a headphone, phone or mic. after selecting the headphone option the audio works fine. this happens every time, not a single exception to this behavior. my laptop is a Dell Inspiron 15-3567 with Ubuntu 18.04. 1) Ubuntu 18.04.1 2) Pulseaudio 1:11.1-1ubuntu7.1 3) Expected to initialize the OS with the headphone connected and get the headphone recognized right away. 4) There's no sound in the headphones, and i have to take them off and plug it again. Then after responding to the ubuntu audio window the sound goes back to working again ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797555 Title: headphone not detected on initialization Status in pulseaudio package in Ubuntu: New Bug description: every time i initialize the computer with the headphone connected, there's no sound in the headphones. i have to take the headphone off and plug it again, then i'm prompted with the ubuntu window asking if it's a headphone, phone or mic. after selecting the headphone option the audio works fine. this happens every time, not a single exception to this behavior. my laptop is a Dell Inspiron 15-3567 with Ubuntu 18.04. 1) Ubuntu 18.04.1 2) Pulseaudio 1:11.1-1ubuntu7.1 3) Expected to initialize the OS with the headphone connected and get the headphone recognized right away. 4) There's no sound in the headphones, and i have to take them off and plug it again. Then after responding to the ubuntu audio window the sound goes back to working again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797425] Re: printing docs with images is very slow - PCL printer
** Description changed: ubuntu 18.04 - Intel Xeon 8 core workstation - default driver for samsung ML-4600 The printer is an old Samsung ML-4600 USB laser printer, but it does its job. On a 8core workstation, printing starts immediately if it's text only. The print itself is always done in 10" or so. - A 26kB LibO doc, containing a tiny 8k image only, needs 2'6" till the - printer starts printing. With a 900kB image in the doc, the time is the - same. + A 26kB LibO doc, containing a tiny 8k image only, needs 2min 6" till the + printer starts printing. With a 900kB image in the doc, the time is + exactly the same. With scribus and the tiny 8K image, it takes 45s till the printer starts action. - When trying to print a heavy 2MB per page doc, it takes more than 10' - till the printer starts to act. + When trying to print a heavy 2MB per page PDF doc, it takes more than 10 + min till the printer starts to act. Odd - with top I cannot see any printing activity causing relevant cpu load, but I think at least one core should do heavy rasterizing work. I love linux to support old hardware - but this is not state-of-the-art, hope improvements are possible. Cheers, Wolf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1797425 Title: printing docs with images is very slow - PCL printer Status in cups package in Ubuntu: New Bug description: ubuntu 18.04 - Intel Xeon 8 core workstation - default driver for samsung ML-4600 The printer is an old Samsung ML-4600 USB laser printer, but it does its job. On a 8core workstation, printing starts immediately if it's text only. The print itself is always done in 10" or so. A 26kB LibO doc, containing a tiny 8k image only, needs 2min 6" till the printer starts printing. With a 900kB image in the doc, the time is exactly the same. With scribus and the tiny 8K image, it takes 45s till the printer starts action. When trying to print a heavy 2MB per page PDF doc, it takes more than 10 min till the printer starts to act. Odd - with top I cannot see any printing activity causing relevant cpu load, but I think at least one core should do heavy rasterizing work. I love linux to support old hardware - but this is not state-of-the- art, hope improvements are possible. Cheers, Wolf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1797425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769657] Re: update toolchain packages for bionic
I'm still seeing the issue and have followed up in bug #1797557 -- 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/1769657 Title: update toolchain packages for bionic Status in binutils package in Ubuntu: Fix Released Status in build-essential package in Ubuntu: New Status in cross-toolchain-base package in Ubuntu: New Status in cross-toolchain-base-ports package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in binutils source package in Bionic: Fix Released Status in cross-toolchain-base source package in Bionic: Fix Released Status in cross-toolchain-base-ports source package in Bionic: Fix Released Status in gcc-7 source package in Bionic: Fix Released Status in gcc-7-cross source package in Bionic: Fix Released Status in gcc-7-cross-ports source package in Bionic: Fix Released Status in gcc-8 source package in Bionic: Fix Released Status in gcc-8-cross source package in Bionic: Fix Released Status in gcc-8-cross-ports source package in Bionic: Fix Released Status in gcc-defaults source package in Bionic: Fix Released Status in gcc-defaults-ports source package in Bionic: Fix Released Bug description: I'd like to update the toolchain packages in bionic, to state which we have in cosmic on May 07: - LP: #1771635: binutils updates from the branch - gcc-8, update to the final 8.1.0 release - gcc-7, updates to the gcc-7-branch up to the time of the 8.1.0 release. - gcc-defaults to bump the 8.1 version, and add some provides - build-essential to add cross packages for amd64 and i386 - corresponding gcc-cross packages The package builds are prepared in https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/ppa/+packages [Impact] Provide an upstream release for GCC 8, and update GCC 7 fixes to the date of the corresponding GCC 8 updates. [Regression Potential] There is regression potential, however with a test rebuild of the main portion of the archive no regressions were found. [Test Case] No regressions in the GCC test suite, and no regressions in the test rebuild of the main component of the archive (all architectures) As a test, a complete archive rebuild (main only) was performed, and no regressions were found with this new package. The archive rebuild also contained updated versions of gcc-7, gcc-8, binutils, python3.6 and python3.7. The GCC and Python packages should not infer with each other. [Validation] Analyze the build logs for regressions. For the cross builds, just make sure that the packages build using the updated sources. Summary of the test rebuilds: file:///home/ubuntu/ftbfs-report/production/test-rebuild-20180730-bionic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20180730-gcc-bionic.html No regressions are shown with the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1769657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797573] [NEW] package libattr1:i386 1:2.4.47-2 failed to install/upgrade: package libattr1:i386 is already installed and configured
Public bug reported: 70.1834:package libgusb2:i386 is already installed and configured ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libattr1:i386 1:2.4.47-2build1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 AptdaemonVersion: 1.1.1+bzr982-0ubuntu19 Architecture: i386 Date: Fri Oct 12 09:59:05 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 multiarch-support 2.27-3ubuntu1 ErrorMessage: package libattr1:i386 is already installed and configured InstallationDate: Installed on 2018-01-10 (275 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: attr Title: package libattr1:i386 1:2.4.47-2 failed to install/upgrade: package libattr1:i386 is already installed and configured UpgradeStatus: Upgraded to bionic on 2018-10-12 (0 days ago) ** Affects: attr (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to attr in Ubuntu. https://bugs.launchpad.net/bugs/1797573 Title: package libattr1:i386 1:2.4.47-2 failed to install/upgrade: package libattr1:i386 is already installed and configured Status in attr package in Ubuntu: New Bug description: 70.1834:package libgusb2:i386 is already installed and configured ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libattr1:i386 1:2.4.47-2build1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic i686 ApportVersion: 2.20.9-0ubuntu7.4 AptdaemonVersion: 1.1.1+bzr982-0ubuntu19 Architecture: i386 Date: Fri Oct 12 09:59:05 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 multiarch-support 2.27-3ubuntu1 ErrorMessage: package libattr1:i386 is already installed and configured InstallationDate: Installed on 2018-01-10 (275 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: attr Title: package libattr1:i386 1:2.4.47-2 failed to install/upgrade: package libattr1:i386 is already installed and configured UpgradeStatus: Upgraded to bionic on 2018-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/attr/+bug/1797573/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.
I have tested the resume in cosmic and it works fine for me. -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: In Progress Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: In Progress Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Invalid Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797578] [NEW] unable to open Ubuntu Software
Public bug reported: when i try to open Ubuntu Software it flashes on the launcher then the icon looks like it didn't open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 12 16:41:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3616] InstallationDate: Installed on 2018-01-21 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO Lenovo H420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2011 dmi.bios.vendor: LENOVO dmi.bios.version: DPKT22A dmi.board.name: To be filled by O.E.M. dmi.board.vendor: LENOVO dmi.board.version: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrDPKT22A:bd11/08/2011:svnLENOVO:pnLenovoH420:pvrLenovo:rvnLENOVO:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Lenovo H420 dmi.product.version: Lenovo dmi.sys.vendor: LENOVO 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.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Oct 12 15:05:52 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB Keyboard KEYBOARD, id 8 input USB Keyboard KEYBOARD, id 9 inputKYE SYSTEMS CORP. Wired Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** 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/1797578 Title: unable to open Ubuntu Software Status in xorg package in Ubuntu: New Bug description: when i try to open Ubuntu Software it flashes on the launcher then the icon looks like it didn't open. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Oct 12 16:41:02 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:3616] InstallationDate: Installed on 2018-01-21 (264 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO Lenovo H420 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=510425b4-02db-49c7-91bd-587ef9d2671d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08
[Touch-packages] [Bug 1797302] Re: ubuntu-bug doesn't provide a way of just getting the URL to report a bug
** Changed in: apport (Ubuntu) Status: New => Triaged ** Changed in: apport (Ubuntu) Importance: Undecided => Low -- 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/1797302 Title: ubuntu-bug doesn't provide a way of just getting the URL to report a bug Status in apport package in Ubuntu: Triaged Bug description: I use more than one browser profile, only one of which is logged in to Launchpad. When using ubuntu-bug to report a bug, it will open the page in whichever one happened to be focused last. If this browser profile isn't logged in to Launchpad, it will redirect me to a login page. It is impossible, as far as I can tell, to reconstruct the original URL in order to copy/paste it in to a browser profile which _is_ logged in to Launchpad. It would be good if ubuntu-bug could either display the URL it is opening before it opens it in the UI. (An acceptable workaround for me (as I generally launch ubuntu-bug from a terminal) would be to write the URL to stdout.) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 11 00:31:45 2018 InstallationDate: Installed on 2017-10-23 (352 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to cosmic on 2018-09-10 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797588] [NEW] System lagging
Public bug reported: The system is lagging and not opening programs well. even switching between windows is very slow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 12 08:37:51 2018 DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3] InstallationDate: Installed on 2018-01-02 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago) dmi.bios.date: 06/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 28 08:34:42 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-I-1 HDMI-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1797588 Title: System lagging Status in xorg package in Ubuntu: New Bug description: The system is lagging and not opening programs well. even switching between windows is very slow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 12 08:37:51 2018 DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3] InstallationDate: Installed on 2018-01-02 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago) dmi.bi
[Touch-packages] [Bug 1693948] Re: useless diagnostics in dpkg.log from journalctl due to ellipses
** Changed in: init-system-helpers (Ubuntu Xenial) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to init-system-helpers in Ubuntu. https://bugs.launchpad.net/bugs/1693948 Title: useless diagnostics in dpkg.log from journalctl due to ellipses Status in init-system-helpers package in Ubuntu: Fix Released Status in init-system-helpers source package in Xenial: Confirmed Status in init-system-helpers source package in Bionic: Fix Released Bug description: Many of the apport hooks try to include some information about why a service didn't start correctly. One recent report included the following: May 26 18:39:19 ux305ua-linux systemd[1]: Starting OpenBSD Secure Shell serv May 26 18:39:19 ux305ua-linux sshd[2500]: /etc/ssh/sshd_config line 64: miss May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Main process exited, ...a[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;31mFailed to start OpenBSD Secure She[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Unit entered failed s[0m May 26 18:39:19 ux305ua-linux systemd[1]: [0;1;39mssh.service: Failed with result 'e[0m Hint: Some lines were ellipsized, use -l to show in full. The actual error information is this: /etc/ssh/sshd_config line 64: miss and Failed with result 'e This is very nearly useless. We should include the -l parameter as suggested so that we stand a chance of seeing an error that doesn't occur in the first twenty characters of program output. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1693948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia- driver-390) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797602] [NEW] systemd incompatible with openresolv and dnsmasq
Public bug reported: Problem: systemd breaks resolvconf-dependent DNS Test case: Install dnsmasq with systemd. Result: The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the make_resolv_conf() function to pass DHCP information to the /sbin/resolvconf program. The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the make_resolv_conf() function to write DHCP information to /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf As a result, resolvconf never runs, and dnsmasq never receives the DHCP-supplied nameservers. Therefore, DNS resolution is broken. Expected result: DHCP-supplied nameservers should be passed to both resolvconf and to systemd. Workaround: Use the 127.0.0.53 address for the systemd resolver as the dnsmasq upstream server. lsb_release -rd output: Description:Ubuntu 18.04.1 LTS Release:18.04 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1797602 Title: systemd incompatible with openresolv and dnsmasq Status in systemd package in Ubuntu: New Bug description: Problem: systemd breaks resolvconf-dependent DNS Test case: Install dnsmasq with systemd. Result: The script in /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines the make_resolv_conf() function to pass DHCP information to the /sbin/resolvconf program. The script in /etc/dhcp/dhclient-enter-hooks.d/resolved redefines the make_resolv_conf() function to write DHCP information to /run/systemd/resolved.conf.d/isc-dhcp-v4-$interface.conf As a result, resolvconf never runs, and dnsmasq never receives the DHCP-supplied nameservers. Therefore, DNS resolution is broken. Expected result: DHCP-supplied nameservers should be passed to both resolvconf and to systemd. Workaround: Use the 127.0.0.53 address for the systemd resolver as the dnsmasq upstream server. lsb_release -rd output: Description:Ubuntu 18.04.1 LTS Release:18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1797602/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797555] Re: headphone not detected on initialization
Hello Bruno, Please create a new report with this command in the terminal: $ ubuntu-bug linux Best regards, -- Cristian Aravena Romero (caravena) ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1797555 Title: headphone not detected on initialization Status in pulseaudio package in Ubuntu: Incomplete Bug description: every time i initialize the computer with the headphone connected, there's no sound in the headphones. i have to take the headphone off and plug it again, then i'm prompted with the ubuntu window asking if it's a headphone, phone or mic. after selecting the headphone option the audio works fine. this happens every time, not a single exception to this behavior. my laptop is a Dell Inspiron 15-3567 with Ubuntu 18.04. 1) Ubuntu 18.04.1 2) Pulseaudio 1:11.1-1ubuntu7.1 3) Expected to initialize the OS with the headphone connected and get the headphone recognized right away. 4) There's no sound in the headphones, and i have to take them off and plug it again. Then after responding to the ubuntu audio window the sound goes back to working again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797555/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797588] Re: System lagging
https://bugs.freedesktop.org/show_bug.cgi?id=108346 -- Cristian Aravena Romero (caravena) ** Bug watch added: freedesktop.org Bugzilla #108346 https://bugs.freedesktop.org/show_bug.cgi?id=108346 ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=108346 Importance: Unknown Status: Unknown -- 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/1797588 Title: System lagging Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: The system is lagging and not opening programs well. even switching between windows is very slow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 12 08:37:51 2018 DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3] InstallationDate: Installed on 2018-01-02 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago) dmi.bios.date: 06/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 28 08:34:42 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-I-1 HDMI-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1797588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797588] Re: System lagging
Hello David, https://bugs.freedesktop.org/show_bug.cgi?id=108346#c1 "Do you have this problem? If so, a bit more information could help. What DE are you using, what version of mesa, what programs aren't opening "well", etc?" Best regards, -- Cristian Aravena Romero (caravena) ** 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/1797588 Title: System lagging Status in X.Org X server: Unknown Status in xorg package in Ubuntu: Incomplete Bug description: The system is lagging and not opening programs well. even switching between windows is very slow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Oct 12 08:37:51 2018 DistUpgraded: 2018-09-28 22:03:01,394 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT216 [GeForce GT 220] [1043:82f3] InstallationDate: Installed on 2018-01-02 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=b73e1c3a-b0eb-4da1-9c26-2fba56feefa2 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-29 (13 days ago) dmi.bios.date: 06/01/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-DS3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd06/01/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-DS3P:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Sep 28 08:34:42 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-I-1 HDMI-1 VGA-1 xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1797588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1726803] Re: unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to install/upgrade: subprocess insta
This bug was fixed in the package shim-signed - 1.38
---
shim-signed (1.38) cosmic; urgency=medium
* Don't fail non-interactive upgrade of nvidia module and module removals
(LP: #1726803)
-- Balint Reczey Thu, 11 Oct 2018 18:12:37 +0200
** Changed in: shim-signed (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1726803
Title:
unattended-upgrades + nvidia stack upgrade == dkms fail (package shim-
signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1 failed to
install/upgrade: subprocess installed post-installation script
returned error exit status 1)
Status in shim-signed package in Ubuntu:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Incomplete
Status in shim-signed source package in Bionic:
Triaged
Status in unattended-upgrades source package in Bionic:
Incomplete
Bug description:
[Impact]
* When Secure Boot is enabled and MOK is not set and a new dkms
module is installed sim-signed asks for a Secure Boot MOK, or aborts
package installation in non-interactive mode. When unattended-upgrades
performed the upgrade the aborted installation leaves an unconfigured
system behind that may even fail to boot. In nvdidia's special case
the new module is actually just a new version of the nvidia module
which should be fine to install.
* The fix in shim-signed now handles nvidia dkms module directory
renames as simple upgrades and also does not handle module removals as
a reason to abort installation.
[Test Case (shim-signed)]
WIP
[Test Case (unattended-upgrades)]
1. Set up a fully - or almost fully updated Bionic system.
2. Install packagages to trigger the block:
apt install dkms shim-signed r8168-dkms
3. Fake enabled secure boot:
echo "shim-signed shim/enable_secureboot boolean true" |
debconf-set-selections
4. Add and enable PPA hosting updated dkms package pulling in a new dkms-like
dependency:
add-apt-repository ppa:rbalint/scratch
echo 'Unattended-Upgrade::Allowed-Origins
{"LP-PPA-rbalint-scratch:${distro_codename}";}' >
/etc/apt/apt.conf.d/51unattended-upgrades-all
5. Observe u-u keeping back the new package:
unattended-upgrade --verbose --dry-run --debug
...
Checking: r8168-dkms ([])
pkg new-dkms-dep may trigger secure boot key prompt
sanity check failed
...
[Regression Potential (shim-signed)]
* The fix lets installation of nvidia dkms module upgrades continue and also
lets dkms module removals continue when MOK is not set and those should not
cause regressions themselves. In case of an implementation mistake a new module
installation could go undetected and could cause the system not load a dkms
module on next boot.
In practice not loading new modules rarely cause regressions, but if a module
is converted from being in the kernel to a dkms module upon an upgrade this is
possible.
* I tested the module addition, removal, nvidia module upgrade and not
module change cases with stubs pretending that the system is secure-boot
capable an found the changed script working properly.
[Regression Potential (unattended-upgrades)]
* Since the fix is holding back packages from installation it is
expected that systems that would have otherwise broke during the
installation would not receive all updates. Since exact detection of
the installation failure reported here does not seem possible u-u
holds back more packages than it would be absolutely necessary.
* Administrators are expected to set up email notifications about the
updates performed by u-u and act on held back packages.
* Since updates pulling in new packages are fairly rare especially in
the -security pocket which u-u installs from by default unwanted
regressions are unlikely to show up.
[Original Bug Text]
Occurred a minute after logging in
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: shim-signed 1.32~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
.proc.sys.kernel.moksbstate_disabled: 0
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Oct 24 11:35:53 2017
EFITables:
Oct 24 11:33:04 paddy-laptop kernel: efi: EFI v2.40 by American Megatrends
Oct 24 11:33:04 paddy-laptop kernel: efi: ACPI=0x7866 ACPI
2.0=0x7866 SMBIOS=0xf SMBIOS 3.0=0xf0020 ESRT=0x79360598
Oct 24 11:33:04 paddy-laptop kernel: esrt: Reserving ESRT space from
0x79360598 to 0x793605d0.
Oct 24 11:33:04 paddy-laptop kernel: Secure boot enabled
ErrorMessage: subprocess installed post-installation script returned error
exit status 1
InstallationDate: Installed on 2017-09-11 (42 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus"
[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep
yes, this still happens in Bionic. does not happen if i login with Wayland session (but wayland is buggy in different ways, so not really a solution). -- 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/1712866 Title: icons from qt applications disappear after screen lock/sleep Status in gnome-shell-extension-appindicator package in Ubuntu: Fix Released Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in gnome-shell-extension-appindicator source package in Artful: Fix Released Bug description: [Impact] Indicators of some Qt apps are not showing after unlocking the screen or shell restart. [Test case] - Login to 17.10 - launch dropbox (if not already launched) - Launch telegram (snap version or without libappindicator support) - Observe icons in taskbar - Lock screen with Super+L - Unlock screen - Icons should still be there [Possible regressions] Icons that should be hidden could be visible instead The fix doesn't apply to snapped applications In the Ubuntu Xorg session, with the Ubuntu Appindicator extension enabled, the tray icons for QT apps (in my case, both owncloud-client from the Ubuntu repos and enpass, from their own repo) show up after first logging in. But once the screen has been left idle long enough to be put to sleep, and is then woken up (I don't actually have screen *lock* enabled, but it still goes comes back to the clock screen and a further gesture is needed to scroll that up to get the desktop), then the icons for those QT apps are gone. Non-QT apps (eg: in my case hexchat, from the ubuntu repos) remain. For a while and due to inattention it seemed more random than that, but I'm fairly sure now it's just the display sleep/wake thing that kills it. The applications are still running in the background (so for instance enpass is still available via the browser extension), and can be seen in the process list. It's just the icons that have disappeared. If I then kill those apps (from the commandline with 'kill [pid]' because there's no other interface to do it from) and relaunch them, they reappear back in the appindicator area. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell-extension-appindicator 17.10 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 24 17:12:43 2017 Dependencies: InstallationDate: Installed on 2017-07-30 (24 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op
See also https://lists.ubuntu.com/archives/apparmor/2018-October/011823.html -- 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/1784499 Title: AppArmor treats regular NFS file access as network op Status in apparmor package in Ubuntu: Confirmed Bug description: I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic. I have the usr.bin.man profile enforced, and home directories in NFS. The log excerpt copied below is the result of a single invocation of "man ls" by an unprivileged user. (The program did display the man page correctly to the user.) It does not seem appropriate for AppArmor to report the man(1) program as having attempted to contact the NFS server directly, when it only tried to access an NFS-served file in the normal way. "man" is not a network-aware program and the log below misleadingly implies otherwise. Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 callbacks suppressed Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2788 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="i
[Touch-packages] [Bug 1797275] Re: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
|$ uname -a |Linux Green 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:16:44 UTC 2018 i686 i686 i686 GNU/Linux |$ dpkg -l | grep libgtk-3-0 |ii libgtk-3-0:i3863.22.30-1ubuntu1 i386 GTK+ graphical user interface library |$ debsums libgtk-3-0 | grep gtk-query |/usr/lib/i386-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0 OK Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797275 Title: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797625] [NEW] Missing the 'Call Trace' with the cases of 'KernelOops'
Public bug reported: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic wayland-session ** Description changed: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 + And the file: 'OopsText.txt' does not appear in the 'Call Trace'. + Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." - - - And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: - + ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: New Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs
[Touch-packages] [Bug 1784499] Re: AppArmor treats regular NFS file access as network op
Thanks for looking into this Markus. I'm surprised that the kernel pieces needed to make this work as expected have yet to be fully integrated. -- 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/1784499 Title: AppArmor treats regular NFS file access as network op Status in apparmor package in Ubuntu: Confirmed Bug description: I am using AppArmor 2.12-4ubuntu5 on Ubuntu 18.04/bionic. I have the usr.bin.man profile enforced, and home directories in NFS. The log excerpt copied below is the result of a single invocation of "man ls" by an unprivileged user. (The program did display the man page correctly to the user.) It does not seem appropriate for AppArmor to report the man(1) program as having attempted to contact the NFS server directly, when it only tried to access an NFS-served file in the normal way. "man" is not a network-aware program and the log below misleadingly implies otherwise. Jul 30 17:38:35 darkstar kernel: [69963.052243] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052274] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052297] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052314] kauditd_printk_skb: 34 callbacks suppressed Jul 30 17:38:35 darkstar kernel: [69963.052316] audit: type=1400 audit(1532986715.854:214): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052323] audit: type=1400 audit(1532986715.854:215): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052327] audit: type=1400 audit(1532986715.854:216): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052339] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052363] audit: type=1400 audit(1532986715.854:217): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052364] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052369] audit: type=1400 audit(1532986715.854:218): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=802 faddr=10.24.115.84 fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.052386] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.052450] audit: type=1400 audit(1532986715.854:219): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.059570] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.059640] audit: type=1400 audit(1532986715.862:220): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2781 comm="man" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.061907] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.061925] audit: type=1400 audit(1532986715.862:221): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.062006] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.062014] audit: type=1400 audit(1532986715.862:222): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2792 comm="less" laddr=X.X.X.X lport=719 faddr=Y.Y.Y.Y fport=2049 family="inet" sock_type="stream" protocol=6 requested_mask="send" denied_mask="send" Jul 30 17:38:35 darkstar kernel: [69963.066404] nfs: RPC call returned error 13 Jul 30 17:38:35 darkstar kernel: [69963.066434] audit: type=1400 audit(1532986715.866:223): apparmor="DENIED" operation="sendmsg" profile="/usr/bin/man" pid=2788 com
[Touch-packages] [Bug 1797628] [NEW] System hangs during boot at "Started configure plugged in printer"
Public bug reported: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub OS: Cosmic xorg version: 1:7.7+19ubuntu8 Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. Have not tested if only unplugging printer from hub makes any difference. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 15:48:22 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2018-10-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: LENOVO 2356CU8 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 529944 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356CU8 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1797628 Title: System hangs during boot at "Started configure plugged in printer" Status in xorg package in Ubuntu: New Bug description: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub OS: Cosmic xorg version: 1:7.7+19ubuntu8 Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. Have not tested if only unplugging printer from hub makes any difference. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 15:48:22 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166]
[Touch-packages] [Bug 1797628] Re: System hangs during boot at "Started configure plugged in printer"
** Description changed: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub - - OS: Cosmic - xorg version: 1:7.7+19ubuntu8 Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. - What I tried: rebooting + What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. - Have not tested if only unplugging printer from hub makes any - difference. + After this "fix," I can reboot fine without unplugging anything. This + bug appears to happen right after a system update (running Software + Updater and there are kernel bits to update). + + This is new behaviour; I had the same system setup running and booting + fine under 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 .tmp.unity_support_test.0: - + ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 15:48:22 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] + Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb] InstallationDate: Installed on 2018-10-02 (10 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927) MachineType: LENOVO 2356CU8 ProcEnviron: - LANGUAGE=en_CA:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_CA.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_CA:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_CA.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET91WW (2.51 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356CU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: 529944 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430s dmi.product.name: 2356CU8 dmi.product.sku: LENOVO_MT_2356 dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1 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 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- 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/1797628 Title: System hangs during boot at "Started configure plugged in printer" Status in xorg package in Ubuntu: New Bug description: System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg. What I tried: rebooting What I expected: to see the login screen What happened: booting hangs Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer" When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub. After this "fix," I can reboot fine without unplugging anything. This bug appears to happen right after a system update (running Software Updater and there are kernel bits to u
[Touch-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
Hi, it was a great idea to test by running without installation, and i test it on: ubuntu-16.04.1-desktop-amd64 - don't see my Bluetooth headset ubuntu-17.10.1-desktop-amd64 - same problems with skipping as with current version ubuntu-18.04-desktop-amd64 - same problems with skipping as with current version so basically it doesn't work at all and the biggest mystery as for me is why i was able to use my headset on ubuntu at least for half a day when i installed it first time? and why it works perfect right now on windows... so i guess the fact that bluetooth works under windows - excluded hardware problem. -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1534433] Re: package python3-libapparmor 2.8.95~2430-0ubuntu5.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/1534433 Title: package python3-libapparmor 2.8.95~2430-0ubuntu5.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in apparmor package in Ubuntu: Confirmed Bug description: I was given instructions on installation from this link: http://dev.deluge- torrent.org/wiki/Installing/Linux/Ubuntu#InstallDeluge ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python3-libapparmor 2.8.95~2430-0ubuntu5.3 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Jan 15 13:08:18 2016 DuplicateSignature: package:python3-libapparmor:2.8.95~2430-0ubuntu5.3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-17 (58 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic root=UUID=9b929f13-0a72-4190-a02c-ea2e221d302a ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: apparmor Syslog: Title: package python3-libapparmor 2.8.95~2430-0ubuntu5.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1534433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state
** Changed in: init-system-helpers (Ubuntu)
Assignee: Balint Reczey (rbalint) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1778219
Title:
unattended-upgrades hangs on shutdown, leaves system in a broken state
Status in init-system-helpers package in Ubuntu:
Invalid
Status in snapd package in Ubuntu:
New
Status in unattended-upgrades package in Ubuntu:
Fix Released
Bug description:
[Impact]
* Unattended-upgrades hangs and gets killed when installing upgrades
that stat/stop services on shutdown, leaving the system in a broken
state
[Test Case]
* Install an updated bionic system:
$ lxc launch ubuntu:18.04 uu-shutdown-test
# apt update
...
* When testing the fixed version, install upgrade u-u at this point checking
that u-u.service is set up before and is wanted by shutdown.target:
# systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket"
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
* Configure u-u to run on shutdown and install -updates:
# echo 'Unattended-Upgrade::InstallOnShutdown "true";' >
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
# echo 'Unattended-Upgrade::Allowed-Origins::
"${distro_id}:${distro_codename}-updates";' >
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too
* Downgrade snapd:
# apt install snapd=2.32.5+18.04
* # reboot
* With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
`-{unattended-upgr}
* With fixed u-u observe snapd update taking place and system
rebooting after a few seconds with all updates installed
* Since this fix is partially reverting the fix for LP: #1654600
please test LP: #1654600 as well to avoid regressions.
[Regression Potential]
* As part of the fix manual changes were made to postinst to properly
transition from coupling u-u.service with multi-user.target to coupling it with
shutdown.target again which can make u-u started during normal boot when there
is a bug in the implementation.
on-testing the SRU.
* Due to relationship changes between u-u.service, other services and
targets u-u may fail to run on shutdown in case of an unexpected regression.
[Original Bug Text]
When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
package installation on various packages hangs until the systemd
ShutdownTimeout (30min) is expired and systemd kills all processes and
powers off/reboots the system.
This leaves packages in an unconfigured, broken state. At least
sometimes this cannot be fixed with a "dpkg --configure -a", but
instead requires the user to manually reinstall the package that
caused the hang.
This appears to be a deadlock, because the hanging commands are always
"systemctl stop ..." or "systemctl restart ...", etc.. If I understand
this correctly, those systemctl commands block because systemd tries
to shutdown the system and tries to satisfy all dependencies for the
shutdown targets before those systemctl commands could get executed,
which creates a deadlock.
Steps to reproduce:
- Install 18.04
- activate "InstallOnShutdown" in /etc/apt/apt.conf.d/50unattended-upgrades
- disable bionic-updates in /etc/apt/sources.list (more on that later)
- execute "unattended-upgrade --download-only"
- reboot the system
-> The upgrade on shutdown hangs when configuring the apport package.
The hanging command is "systemctl stop apport-forward.socket". The
system hangs until the systemd ShutdownTimeout expires and systemd
forcefully reboots the system.
After the system is rebooted the apport package is in "iUR" state, and
needs to be reinstalled to fix this.
I disabled the bionic-updates pocket in sources.list, because in the
default configuration unattended-updates does not use bionic-updates,
and seems to have skipped installation of apport from bionic-security
(supposedly beca
[Touch-packages] [Bug 1797275] Re: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
unsure what's the issue on your machine, the binary is there/valid/not corrupted, what happens if you do "$ /usr/lib/i386-linux-gnu/libgtk-3-0 /gtk-query-immodules-3.0"? ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797275 Title: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. Status in gtk+3.0 package in Ubuntu: New Bug description: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
After upgrading from 18.04 to 18.10 the freezes before login. (nvidia- driver-390) -- 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/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797649] [NEW] receive authentication canceled in terminal when changing options in "Other Software"
Public bug reported: I've tried to disable some PPAs in the "Other Software" tab of software- properties and whenever I check a box for the first time I get a message in the terminal about "ERROR:root:Authentication canceled, changes have not been saved" (although an authentication dialog has not appeared) and the dialog box greys out. However, frequently upon clicking the box for a second time (when it is greyed out) I am then presented with an authentication dialog. This seems quite odd. I've tested this the following versions of software-properties-gtk. 0.96.24.32.5 from bionic 0.26.27 from cosmic ** Affects: software-properties (Ubuntu) Importance: Medium Status: New ** Tags: bionic cosmic ** Tags added: bionic cosmic ** Changed in: software-properties (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1797649 Title: receive authentication canceled in terminal when changing options in "Other Software" Status in software-properties package in Ubuntu: New Bug description: I've tried to disable some PPAs in the "Other Software" tab of software-properties and whenever I check a box for the first time I get a message in the terminal about "ERROR:root:Authentication canceled, changes have not been saved" (although an authentication dialog has not appeared) and the dialog box greys out. However, frequently upon clicking the box for a second time (when it is greyed out) I am then presented with an authentication dialog. This seems quite odd. I've tested this the following versions of software-properties-gtk. 0.96.24.32.5 from bionic 0.26.27 from cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1797649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
hi, FINALLY, i was able to localize problem :) all my headsets are skipping only when setting window is open! so basically when you click test left or test right - it is in settings window and thus it sounds terribly. But, if you close setting window - every headset works just fine (on online radio for example). my guess would be that while settings window is open - system constantly looking for available devices and thus interfere with present devices. Sorry guys for all these troubles, meanwhile solution was so simple. Thanks -- 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/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794544] Re: [SRU] 2.56.3
What testing will be done of the resulting binary packages to guard against misbuilds not caught by the upstream testing? Please call this out explicitly in the bug description. (If the autopkgtests are sufficient, that's fine, please just call it out.) ** Changed in: glib2.0 (Ubuntu Bionic) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794544 Title: [SRU] 2.56.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: Incomplete Bug description: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. * New upstream release (LP: #xxx) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797648] [NEW] package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: AS per summary. I am new to Linux/Ubuntu and encountered this error when trying to install new software ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbsd0:i386 0.8.7-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Oct 12 23:15:10 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 DuplicateSignature: package:libbsd0:i386:0.8.7-1 Setting up libmng2:amd64 (2.0.2-0ubuntu3) ... dpkg: error processing package libbsd0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libbsd Title: package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libbsd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libbsd in Ubuntu. https://bugs.launchpad.net/bugs/1797648 Title: package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libbsd package in Ubuntu: New Bug description: AS per summary. I am new to Linux/Ubuntu and encountered this error when trying to install new software ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbsd0:i386 0.8.7-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Oct 12 23:15:10 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 DuplicateSignature: package:libbsd0:i386:0.8.7-1 Setting up libmng2:amd64 (2.0.2-0ubuntu3) ... dpkg: error processing package libbsd0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libbsd Title: package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbsd/+bug/1797648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794544] Re: [SRU] 2.56.3
** Description changed: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME - [ Regresison potential ] + [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. - * New upstream release (LP: #xxx) - + The documentation for G_GNUC_MALLOC has changed to be more restrictive - to avoid miscompilations; you should check whether any uses of it in - your code are appropriate - + Fix cancellation of g_subprocess_communicate_async() calls - + Bug fixes: - + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 - + GBookmarkFile: nullptr access in current_element - + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char - + Backport g_subprocess_communicate() cancellation fixes from !266 to - glib-2-56 (LP: #1789476) - + Many uses of G_GNUC_MALLOC are incorrect - + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw - + Fix persistent CI failure on glib-2-56 + * New upstream release (LP: #xxx) + + The documentation for G_GNUC_MALLOC has changed to be more restrictive + to avoid miscompilations; you should check whether any uses of it in + your code are appropriate + + Fix cancellation of g_subprocess_communicate_async() calls + + Bug fixes: + + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + + GBookmarkFile: nullptr access in current_element + + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + + Backport g_subprocess_communicate() cancellation fixes from !266 to + glib-2-56 (LP: #1789476) + + Many uses of G_GNUC_MALLOC are incorrect + + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + + Fix persistent CI failure on glib-2-56 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1794544 Title: [SRU] 2.56.3 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Bionic: In Progress Bug description: [ Description ] The third stable release in the 2.56 series. [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regression potential ] Various fixes in multiple places so multiple apps could be affected. * New upstream release (LP: #xxx) + The documentation for G_GNUC_MALLOC has changed to be more restrictive to avoid miscompilations; you should check whether any uses of it in your code are appropriate + Fix cancellation of g_subprocess_communicate_async() calls + Bug fixes: + /network-monitor/create-in-thread fails in (LXC) containers on glib-2-56 + GBookmarkFile: nullptr access in current_element + GBookmarkFile: heap-buffer-overflow in g_utf8_get_char + Backport g_subprocess_communicate() cancellation fixes from !266 to glib-2-56 (LP: #1789476) + Many uses of G_GNUC_MALLOC are incorrect + Test for BROKEN_IP_MREQ_SOURCE_STRUCT is broken on Windows / Mingw + Fix persistent CI failure on glib-2-56 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1794544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797648] Re: package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libbsd in Ubuntu. https://bugs.launchpad.net/bugs/1797648 Title: package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libbsd package in Ubuntu: New Bug description: AS per summary. I am new to Linux/Ubuntu and encountered this error when trying to install new software ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libbsd0:i386 0.8.7-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Fri Oct 12 23:15:10 2018 Dependencies: gcc-8-base 8.2.0-1ubuntu2~18.04 libc6 2.27-3ubuntu1 libgcc1 1:8.2.0-1ubuntu2~18.04 DuplicateSignature: package:libbsd0:i386:0.8.7-1 Setting up libmng2:amd64 (2.0.2-0ubuntu3) ... dpkg: error processing package libbsd0:i386 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-10-12 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: libbsd Title: package libbsd0:i386 0.8.7-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libbsd/+bug/1797648/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786227] Re: should not hard-depend on cifs-utils
This question was also asked a few months ago: https://community.ubuntu.com/t/anyone-use-cifs-root-in-live-session/1821 Some people apparently do use the CIFS feature for the default Ubuntu ISO. Are you interested in the default ISO or were you making a custom ISO? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1786227 Title: should not hard-depend on cifs-utils Status in casper package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Currently (current bionic has the casper version 1.394), it hard- depends on cifs-utils, which make the installation 41 MB bigger. This is only needed if used with getting the squash image via cifs. The basic functionality (running a live iso or image) works without it - proven by killing the dependency by hand. So I suggest to move cifs-utils to recommendends or suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1786227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786227] Re: should not hard-depend on cifs-utils
casper is also in the 'live' seed for Ubuntu and its flavors so it would still be installed by default in the live environment. ** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1786227 Title: should not hard-depend on cifs-utils Status in casper package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Currently (current bionic has the casper version 1.394), it hard- depends on cifs-utils, which make the installation 41 MB bigger. This is only needed if used with getting the squash image via cifs. The basic functionality (running a live iso or image) works without it - proven by killing the dependency by hand. So I suggest to move cifs-utils to recommendends or suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1786227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1264368] Re: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c
The message is emitted by glib: https://gitlab.gnome.org/GNOME/glib/commit/a919be3d39150328874ff647fb2c2be7af3df996 The commit log description is: "gmain: Warn when g_source_remove() fails". So why is it calling g_critical() instead of g_warning()? Obviously, it's not a critical error, if people are able to live with these annoying messages for five years with no obvious ill effects. Critical errors are often routed to /dev/console, and it's clearly inappropriate to escalate these messages that high. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to consolekit in Ubuntu. https://bugs.launchpad.net/bugs/1264368 Title: GLib-CRITICAL **: Source ID was not found when attempting to remove it - warning when leaving Network menu of g-c-c Status in AndroidSDK: New Status in Banshee: New Status in gnome-control-center: Incomplete Status in GParted: Unknown Status in notification-daemon: New Status in anjuta package in Ubuntu: Confirmed Status in consolekit package in Ubuntu: Confirmed Status in f-spot package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-mplayer package in Ubuntu: Confirmed Status in putty package in Ubuntu: Confirmed Bug description: Steps to recreate: 1. Open gnome-control-center in terminal. 2. Go to Network. 3. Go back to All preferences. 4. Notice that in terminal there is a warning: $ gnome-control-center (gnome-control-center:13519): GLib-CRITICAL **: Source ID 166 was not found when attempting to remove it ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu49 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu3 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Dec 26 21:03:52 2013 InstallationDate: Installed on 2013-10-15 (71 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131015) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to trusty on 2013-11-05 (51 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/androidsdk/+bug/1264368/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786227] Re: should not hard-depend on cifs-utils
I made a custom ISO - or better a completely new one. Its whole size is 122 MB. It has e.g. no GUI, but fullfiles one specific target (network/VPN/firewall area). A "normal" ubuntu live ISO have probably most dependencies for cifs- utils, so there is no big deal I assume. But it hurts really if one tries to make "minimal" boot/live CDs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1786227 Title: should not hard-depend on cifs-utils Status in casper package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Currently (current bionic has the casper version 1.394), it hard- depends on cifs-utils, which make the installation 41 MB bigger. This is only needed if used with getting the squash image via cifs. The basic functionality (running a live iso or image) works without it - proven by killing the dependency by hand. So I suggest to move cifs-utils to recommendends or suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1786227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450588] Re: /var/log/dmesg No Longer Being Updated
Sorry but that argument is illogical. The only retention period that would ensure that you always have the boot time kernel messages is 'infinity' and that's not a reasonable option for obvious reasons (c.f. LP #1618188). ** Changed in: systemd (Ubuntu) Status: Won't Fix => 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/1450588 Title: /var/log/dmesg No Longer Being Updated Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450588] Re: /var/log/dmesg No Longer Being Updated
** Also affects: rsyslog (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/1450588 Title: /var/log/dmesg No Longer Being Updated Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450588] Re: /var/log/dmesg No Longer Being Updated
./debian/rsyslog.dmesg.upstart was shipped by rsyslog package in Trusty and/or other releases. It was: start on runlevel [2345] task script savelog -q -p -c 5 /var/log/dmesg dmesg -s 524288 > /var/log/dmesg chgrp adm /var/log/dmesg end script Thus if such functionality is desired to be preserved, imho rsyslog should be shipping a similar configuration or unit. Note that journald pushes all entries to rsyslog, thus i would have thought it could have generated /var/log/dmesg using normal rsyslog logging configuration facilities. I'm not sure how to configure rsyslog correctly to retain these. But I can write an equivalent systemd unit: $ systemctl cat dmesg # /etc/systemd/system/dmesg.service [Unit] Description=Save kernel messages [Service] Type=idle ExecStartPre=/usr/bin/savelog -q -p -c 5 /var/log/dmesg ExecStart=/bin/sh -c '/bin/dmesg -s 524288 > /var/log/dmesg' ExecStartPost=/bin/chgrp adm /var/log/dmesg [Install] WantedBy=multi-user.target The dmesg command can be approximated with the following journalctl command, which may have more data than dmesg ring-buffer: $ journalctl --boot 0 --dmesg --output short-monotonic --quiet --no- pager --no-hostname however, that is slightly incompatible format due to the extra `kernel:` stanza after the timestamp [1195009.811669] kernel: aufs au_plink_put:436:umount[15188]: pseudo- link is not flushed --boot 0 -> means to show output from current boot only --dmesg -> means to show dmesg logs only --output short-monotonic -> means to prefix things with regular [monotonic] time in dmesg like format --quiet -> disables the headers with when the logs/boot started finished --no-pager -> dumps to stdout, instead of less --no-hostname -> supresses the hostname entry which is injected between time and kernel: normally E.g. on my system journalctl command above recovers things from 0.00 time microcode updated, instead of from very late messages. Imho journalctl should suppress the `kernel:` as that should be implied by --dmesg flag. Depending on how much things happen during boot, i'm not sure if dmesg should be used, or journalctl to retrieve the boot log. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1450588 Title: /var/log/dmesg No Longer Being Updated Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450588] Re: /var/log/dmesg No Longer Being Updated
Marking as invalid for systemd package. As neither it, nor upstart shipped the functionality in question. It is a regression in the rsyslog package. Or possibly makes sense to ship this in like util-linux which ships /bin/dmesg. ** Changed in: rsyslog (Ubuntu) Assignee: (unassigned) => Canonical Server Team (canonical-server) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1450588 Title: /var/log/dmesg No Longer Being Updated Status in rsyslog package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Bug description: After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786227] Re: should not hard-depend on cifs-utils
Unfortunately, we are in Final Freeze now in preparation for Ubuntu 18.10's release next week so I don't removing the direct dependency from casper is something we are going to be able to do until 19.04. https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseSchedule -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1786227 Title: should not hard-depend on cifs-utils Status in casper package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Currently (current bionic has the casper version 1.394), it hard- depends on cifs-utils, which make the installation 41 MB bigger. This is only needed if used with getting the squash image via cifs. The basic functionality (running a live iso or image) works without it - proven by killing the dependency by hand. So I suggest to move cifs-utils to recommendends or suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1786227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1786227] Re: should not hard-depend on cifs-utils
Sorry I didn't stumble across this bug a month ago. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1786227 Title: should not hard-depend on cifs-utils Status in casper package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Currently (current bionic has the casper version 1.394), it hard- depends on cifs-utils, which make the installation 41 MB bigger. This is only needed if used with getting the squash image via cifs. The basic functionality (running a live iso or image) works without it - proven by killing the dependency by hand. So I suggest to move cifs-utils to recommendends or suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1786227/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797625] Re: Missing the 'Call Trace' with the cases of 'KernelOops'
** Tags added: rls-dd-incoming -- 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/1797625 Title: Missing the 'Call Trace' with the cases of 'KernelOops' Status in apport package in Ubuntu: New Bug description: Hello, I am working with these two reports: * watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112] https://bugs.launchpad.net/bugs/1796385 * watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:1:85] https://bugs.launchpad.net/bugs/1797538 And the file: 'OopsText.txt' does not appear in the 'Call Trace'. Others: https://bugzilla.kernel.org/show_bug.cgi?id=201379#c3 "The bug in lauchpad, unless I am missing something, provides not a single actionable traceback. I don't think it is even possible to identify where exactly the CPU hangs unless additional information is provided. There is no traceback in dmesg, and OopsText doesn't include it either. Given that, it is not possible to identify the responsible subsystem, much less to fix the underlying problem. The only thing we can say for sure is that it is _not_ a watchdog driver problem." Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: apport 2.20.10-0ubuntu11 Uname: Linux 4.18.13-gnu x86_64 ApportLog: ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 12 16:12:58 2018 InstallationDate: Installed on 2017-10-13 (364 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1797625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797275] Re: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent.
Thank you, Sebastian! That worked. I am accustomed to using "." in order to run an executable which is not locatable in PATH. Having experimented some by writing a trivial non-PATH executable script and calling it both with and without the preceding ".", I have learned something new about shell syntax. I have been holding on to an assumption which does not serve me, and which now I relinquish. This issue - mine, not yours - is resolved. Thank you again for your time and attention. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1797275 Title: libgtk-3-bin v. 3.22.30-1ubuntu1: Binary "gtk-query-immodules-3.0" is absent. Status in gtk+3.0 package in Ubuntu: New Bug description: The binary "gtk-query-immodules-3.0" is absent from package. The package DOES include the man-page for "gtk-query-immodules-3.0", but not the actual utility it documents. I downloaded the source tarball "gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz" and untar-ed it: |$ ls ./ |debian |gtk+3.0_3.22.30-1ubuntu1.debian.tar.xz |$ ls ./debian/libgtk-3-bin* |debian/libgtk-3-bin.install |debian/libgtk-3-bin.links.in |$ cat ./debian/libgtk-3-bin.install |usr/bin/broadwayd |usr/bin/gtk-builder-tool |usr/bin/gtk-launch |usr/bin/gtk-query-settings |usr/share/gettext/its/gtkbuilder.its |usr/share/gettext/its/gtkbuilder.loc |usr/share/man/man1/broadwayd.1 |usr/share/man/man1/gtk-builder-tool.1 |usr/share/man/man1/gtk-launch.1 |usr/share/man/man1/gtk-query-immodules-3.0.1 |usr/share/man/man1/gtk-query-settings.1 Qualifiers: 1) |$ lsb_release -rd |Description:Linux Mint 19 Tara |Release:19 2) |$ apt-cache policy libgtk-3-bin |libgtk-3-bin: | Installed: 3.22.30-1ubuntu1 | Candidate: 3.22.30-1ubuntu1 | Version table: | *** 3.22.30-1ubuntu1 500 |500 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages |100 /var/lib/dpkg/status |$ ls /usr/share/man/man1/gtk-query* |/usr/share/man/man1/gtk-query-immodules-2.0.1.gz |/usr/share/man/man1/gtk-query-immodules-3.0.1.gz |/usr/share/man/man1/gtk-query-settings.1.gz |$ ls /usr/bin/gtk-query* |/usr/bin/gtk-query-settings 3) I am experimenting with development of specialized immodules for GtkEntry widget. I expect to be able to install these additional modules and for my application to access them per the instructions in the Gtk+3 documentation. 4) |$ whereis gtk-query-immodules-3.0 |gtk-query-immodules-3: Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1797275/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644626] Re: Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5
[Expired for krb5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: krb5 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1644626 Title: Login does not work with krb5 after upgrade to 16.04.1 from 14.04.5 Status in krb5 package in Ubuntu: Expired Bug description: After having managed to have a 1024x768 lightdm screen displayed begging to login, I've tried and being prompted with "You where logged in with cached credentials". Not really: I am logged in, but immediately thrown out again. It is impossible to work! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.2-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 24 19:32:58 2016 InstallationDate: Installed on 2014-02-10 (1017 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) IpRoute: default via 10.160.0.1 dev eth1 10.160.0.0/16 dev eth1 proto kernel scope link src 10.160.2.45 169.254.0.0/16 dev eth0 scope link metric 1000 172.18.8.0/24 dev eth0 proto kernel scope link src 172.18.8.141 IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-11-24 (0 days ago) ftp_proxy: http://proxy01-muc.bfs.de:8080/ http_proxy: http://proxy01-muc.bfs.de:8080/ nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Kabelnetzwerkverbindung 1 c6be5d5a-c232-41e9-ae61-28f7974f30a9 802-3-ethernet 1397215392 Fr 11 Apr 2014 13:23:12 CEST yes 0 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- eth1ethernet unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.2connected started none enabled enabled enabled enabled enabled no_proxy: 127.0.0.1, localhost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1644626/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1082900] Re: cant update via ubuntu file manager
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1082900 Title: cant update via ubuntu file manager Status in cups package in Ubuntu: Expired Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 12.04 Package: cups 1.5.0-8ubuntu6 [modified: usr/lib/cups/filter/commandtoescpx usr/lib/cups/filter/commandtopclx usr/lib/cups/filter/imagetopdf usr/lib/cups/filter/imagetops usr/lib/cups/filter/imagetoraster usr/lib/cups/filter/pdftoijs usr/lib/cups/filter/pdftoopvp usr/lib/cups/filter/pdftopdf usr/lib/cups/filter/pdftops usr/lib/cups/filter/pdftoraster usr/lib/cups/filter/pstopdf usr/lib/cups/filter/rastertoescpx usr/lib/cups/filter/rastertopclx usr/lib/cups/filter/texttopdf usr/lib/cups/filter/texttops usr/share/cups/banners/classified usr/share/cups/banners/confidential usr/share/cups/banners/secret usr/share/cups/banners/standard usr/share/cups/banners/topsecret usr/share/cups/banners/unclassified usr/share/cups/data/testprint] ProcVersionSignature: Ubuntu 3.0.0-21.35-generic 3.0.32 Uname: Linux 3.0.0-21-generic x86_64 ApportVersion: 2.0.1-0ubuntu5 Architecture: amd64 Date: Sun Nov 25 14:38:10 2012 DpkgHistoryLog: Start-Date: 2012-11-25 14:38:08 Commandline: aptdaemon role='role-fix-broken-depends' sender=':1.58' Install: printer-driver-gutenprint:amd64 (5.2.8~pre1-0ubuntu2.1, automatic), cups-filters:amd64 (1.0.18-0ubuntu0.1, automatic) Upgrade: cups-client:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu4), cups-common:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu4), cups:amd64 (1.5.0-8ubuntu6, 1.5.3-0ubuntu4), cups-bsd:amd64 (1.5.2-9ubuntu1, 1.5.3-0ubuntu4) ErrorMessage: subprocess new pre-removal script returned error exit status 100 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) Lpstat: device for MFC5890CN: usb://Brother/MFC-5890CN?serial=BROF1F322237 MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Papersize: a4 PpdFiles: MFC5890CN: Brother MFC-5890CN CUPS v1.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-21-generic root=UUID=35fd4678-7f52-4d5f-8c95-99816c0a7ec1 ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups 1.5.0-8ubuntu6 [modified: usr/lib/cups/filter/commandtoescpx usr/lib/cups/filter/commandtopclx usr/lib/cups/filter/imagetopdf usr/lib/cups/filter/imagetops usr/lib/cups/filter/imagetoraster usr/lib/cups/filter/pdftoijs usr/lib/cups/filter/pdftoopvp usr/lib/cups/filter/pdftopdf usr/lib/cups/filter/pdftops usr/lib/cups/filter/pdftoraster usr/lib/cups/filter/pstopdf usr/lib/cups/filter/rastertoescpx usr/lib/cups/filter/rastertopclx usr/lib/cups/filter/texttopdf usr/lib/cups/filter/texttops usr/share/cups/banners/classified usr/share/cups/banners/confidential usr/share/cups/banners/secret usr/share/cups/banners/standard usr/share/cups/banners/topsecret usr/share/cups/banners/unclassified usr/share/cups/data/testprint] failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 UpgradeStatus: Upgraded to precise on 2012-11-25 (0 days ago) dmi.bios.date: 05/11/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77-DS3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd05/11/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-DS3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-03-07 (523 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: device for HP-Officejet-5740-series: hp:/usb/Officejet_5740_series?serial=TH61K4Y1RD05ZF MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP-Officejet-5740-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP-Officejet-5740-series.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/ubuntu--vg-root ro vesafb.invalid=1 drm.debug=0xe crashkernel=
[Touch-packages] [Bug 1091446] Re: cron fails to work after upgrade
[Expired for cron (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cron (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1091446 Title: cron fails to work after upgrade Status in cron package in Ubuntu: Expired Bug description: after upgrading to 12.10, cron jobs no longer execute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1091446/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1019358] Re: cron is not functional in kubuntu 12.04
[Expired for cron (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cron (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1019358 Title: cron is not functional in kubuntu 12.04 Status in cron package in Ubuntu: Expired Bug description: After upgrading to kubuntu 12.04 from 11.10, cron jobs are no longer executing, even though cron is running To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1019358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
