[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
Hi charlie, thank you for your answer. I confirm I'm using VMware me too. Last kernel 4.15.0-33 doesn't fix the issue. Last kernel not affected is 4.15.0-30. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in util-linux package in Ubuntu: New Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5
Hello Jonathan, or anyone else affected, Accepted console-setup into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console- setup/1.178ubuntu2.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: console-setup (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1788597 Title: ubiquity broken with console-setup 1.178ubuntu2.5 Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: [ SRU Justification ] Due to my brain being in the wrong language, a function was exiting the script instead of returning. Derp. [ Regression Potential ] N'much. [ Test Case ] Build a new ubiquity and see if we can haz keyboard again. [ Original Bug ] Since this version of console-setup in bionic ubiquity now skips the Keyboard and Wireless pages. http://launchpadlibrarian.net/382474004/console- setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769301] Re: resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument'
I've asked a question on stackexchange.com, but still no answer. There is a
detailed description and some logs.
https://unix.stackexchange.com/questions/458853/useradd-groupadd-fails-failure-while-writing-changes-to-etc-passwd-and-etc-gr
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libselinux in Ubuntu.
https://bugs.launchpad.net/bugs/1769301
Title:
resetting /proc/thread-self/attr/fscreate results in 'Invalid
Argument'
Status in libselinux package in Ubuntu:
Confirmed
Bug description:
root@ubuntu:~# useradd -g 100 tst003
useradd: failure while writing changes to /etc/passwd
root@ubuntu:~# sestatus
SELinux status: enabled
SELinuxfs mount:/sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode: permissive
Mode from config file: permissive
Policy MLS status: enabled
Policy deny_unknown status: allowed
Memory protection checking: requested (insecure)
Max kernel policy version: 31
The problem does not occur when SELinux is complete disabled.
Please note that a very similar problem occurs using groupadd:
root@ubuntu:~# groupadd tstgrp001
groupadd: failure while writing changes to /etc/group
= journal =
(Please note that there is *no* AVC!)
May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004,
GID=100, home=/home/tst003, shell=/bin/sh
May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user
id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0
res=success'
May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to
/etc/passwd
May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user
acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0
res=failed'
May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted
= ltrace =
[pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360
[pid 1074] <... fflush resumed> )= 0
[pid 1074] fileno(0x5595b21c6200)= 12
[pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154
[pid 1074] SYS_fsync(12) = 0
[pid 1074] <... fsync resumed> ) = 0
[pid 1074] fclose(0x5595b21c6200
[pid 1074] SYS_close(12) = 0
[pid 1074] <... fclose resumed> )= 0
[pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1
[pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0
[pid 1074] <... utime resumed> ) = 0
[pid 1074] fclose(0x5595b21af2a0
[pid 1074] SYS_close(5) = 0
[pid 1074] <... fclose resumed> )= 0
[pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2
[pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5
[pid 1074] SYS_write(5, nil, 0) = -22
[pid 1074] SYS_close(5) = 0
[pid 1074] <... setfscreatecon resumed> )= 0x
[pid 1074] free(0x5595b21b9dc0) =
[pid 1074] free(0x5595b21b8a00) =
[pid 1074] strlen("x") = 1
[pid 1074] memset(0x5595b21b7560, '\0', 1) = 0x5595b21b7560
[pid 1074] free(0x5595b21b7560) =
[pid 1074] free(0x5595b21b94e0) =
[pid 1074] free(0x5595b21b9000) =
[pid 1074] free(0x5595b21b8fc0) =
= strace =
write(12, "root:x:"..., 1360) = 1360
fsync(12) = 0
close(12) = 0
utime("/etc/passwd-", {actime=1525497034 /* 2018-05-05T05:10:34+ */,
modtime=1525496803 /* 2018-05-05T05:06:43+ */}) = 0
close(5)= 0
openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5
write(5, NULL, 0) = -1 EINVAL (Invalid argument)
close(5)= 0
= Version Information =
root@ubuntu:~# lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04
root@ubuntu:~# dpkg -l | grep passwd | grep -v base-pa
ii passwd1:4.5-1ubuntu1
amd64change and administer password and group data
root@ubuntu:~# dpkg -l | grep selinux
ii libselinux1:amd64 2.7-2build2
amd64SELinux runtime shared libraries
ii python3-selinux 2.7-2build2
amd64Python3 bindings to SELinux shared libraries
ii selinux-basics0.5.6
all SEL
[Touch-packages] [Bug 1788810] [NEW] Computer won't suspend, DBUS reports that a suspend or shutdown operation already in progress
Public bug reported: After a fresh boot computer suspends fine, however further attempts to suspend result in failure with the above mentioned error message. When that happens, shutdown doesn't work either; shutdown process gets stuck at some point and I must forcibly turn off or reset the computer. Sometimes the shutdown almost completes, but THEN the computer enters suspend, after which I must wake it up to complete shutdown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Aug 24 10:39:30 2018 SourcePackage: dbus UpgradeStatus: Upgraded to bionic on 2018-06-19 (65 days ago) ** Affects: dbus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1788810 Title: Computer won't suspend, DBUS reports that a suspend or shutdown operation already in progress Status in dbus package in Ubuntu: New Bug description: After a fresh boot computer suspends fine, however further attempts to suspend result in failure with the above mentioned error message. When that happens, shutdown doesn't work either; shutdown process gets stuck at some point and I must forcibly turn off or reset the computer. Sometimes the shutdown almost completes, but THEN the computer enters suspend, after which I must wake it up to complete shutdown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Aug 24 10:39:30 2018 SourcePackage: dbus UpgradeStatus: Upgraded to bionic on 2018-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1788810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags added: resume ** Tags added: suspend-resume -- 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/1788807 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Bug description: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. ProblemType: Bug DistroRelease: Ubuntu 18.
[Touch-packages] [Bug 1603715] Re: [Dell DW375] bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume
** Summary changed:
- bluetooth unavailable after rfkill hard (or soft) unblocking and after
suspend/resume
+ [Dell DW375] bluetooth unavailable after rfkill hard (or soft) unblocking and
after suspend/resume
--
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/1603715
Title:
[Dell DW375] bluetooth unavailable after rfkill hard (or soft)
unblocking and after suspend/resume
Status in Bluez Utilities:
Incomplete
Status in bluez package in Ubuntu:
Confirmed
Bug description:
DELL Latitude E5510 has a hardware switch to disable and enable
bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
terms of wifi, this works great: After hard unblocking, the device
resumes back to normal operation without any manual intervention. That
was also working with bluetooth as of ubuntu 14.04, kernel 4.2.
In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
is not working any more:
After hard blocking and unblocking
- bluetooth is not working at all
- the applet-indicator remains gray
- bluetooth cannot be enabled with the applet-indicator (see
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
Applet-indicator remains gray
- rfkill list tells me that the kernel knows about the hard unblocking (turns
from "yes" to "no"):
rfkill list bluetooth
2: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
8: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
The device is a
sudo lsusb
Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module
Workaround: After a
sudo service bluetooth restart
the bluetooth device turns back to normal operation and the applet-
indicator turns from gray to black (available).
Suggested fix: Make the workaround obsolete.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu6
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sun Jul 17 04:00:58 2016
InstallationDate: Installed on 2014-11-29 (595 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64
(20140722.2)
MachineType: Dell Inc. Latitude E5510
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet
splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
dmi.bios.date: 12/06/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.name: 023HKR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5510
dmi.product.version: 0001
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1603715/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]
** Summary changed: - Bluetooth device not detected after resume from suspend + Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] -- 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/1788807 Title: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565] Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Bug description: When I suspend my laptop, it often happens that the bluetooth stops working. From gnome settings it is shown like if I had no bluetooth device at all. $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 'blue|firm' 03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01) Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter [1a3b:2130] Kernel driver in use: ath9k Kernel modules: ath9k 04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader [10ec:5287] (rev 01) -- 04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12) Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1043:200f] Kernel driver in use: r8169 Kernel modules: r8169 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. Bus 001 Device 006: ID 13d3:3408 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4.15.0-32-generic [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 35.407491] Bluetooth: Core ver 2.22 [ 35.407504] Bluetooth: HCI device and connection manager initialized [ 35.407506] Bluetooth: HCI socket layer initialized [ 35.407507] Bluetooth: L2CAP socket layer initialized [ 35.407510] Bluetooth: SCO socket layer initialized [ 53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 53.501780] Bluetooth: BNEP filters: protocol multicast [ 53.501783] Bluetooth: BNEP socket layer initialized [ 87.220137] Bluetooth: RFCOMM TTY layer initialized [ 87.220143] Bluetooth: RFCOMM socket layer initialized [ 87.220149] Bluetooth: RFCOMM ver 1.11 [ 1675.503865] usb 1-5: device firmware changed [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err [ 1681.095546] Bluetooth: Loading patch file failed [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=10248 label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined" Trying to use bluetooth from bluetoothctl $ bluetoothctl Agent registered [bluetooth]# scan on No default controller available Trying to restart the bluetooth service doesn't produce any effect: $ sudo service bluetooth restart Getting bluetooth service status: $ sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago Docs: man:bluetoothd(8) Main PID: 24999 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4915) CGroup: /system.slice/bluetooth.service └─24999 /usr/lib/bluetooth/bluetoothd elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service... elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service. elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service... elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48 elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service. elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management interface 1 lines 1-17/17 (END) Reloading the driver: $ sudo modprobe -r btusb; sudo modprobe btusb; $ sudo service bluetooth restart None of these attempts could solve the issue. What happens? Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth controller is no longer recognised and bluetooth service cannot be used anymore. What would you expect? Bluetooth controller to be recognised and working also after resume. ProblemTy
[Touch-packages] [Bug 1782893] Re: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174)
** Summary changed: - Bluetooth not working on Dell XPS 15 + Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174) -- 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/1782893 Title: Bluetooth not working on Dell XPS 15 (Qualcomm Atheros QCA6174) Status in bluez package in Ubuntu: Incomplete Status in gnome-bluetooth package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: am 5501 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (272 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (32 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt-f2 switches to virtual terminal 2
Possibly a duplicate of #520546. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt-f2 switches to virtual terminal 2 Status in console-cyrillic package in Ubuntu: Invalid Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-cyrillic/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559618] [NEW] light-locker appears to incorrectly handle Kerberos ticket cache filenames
You have been subscribed to a public bug: When unlocking an Ubuntu 16.04 system which is using light-locker as the screen saver, Kerberos authentication works for a normal, unprivileged user, except that the resulting ticket cache is incorrectly named. Instead of the resulting ticket cache created as a result of such successful authentication being named something like: krb5cc_1000 (if the UID of the user is 1000) ...the cache file is named: krb5cc_0 (which would presumably be correct if root were logging in, but not a normal, unprivileged user) I am willing to help debug this issue, so if there is anything you would like me to try, please let me know. Thanks, Brian ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: light-locker 1.7.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 22:32:52 2016 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug xenial -- light-locker appears to incorrectly handle Kerberos ticket cache filenames https://bugs.launchpad.net/bugs/1559618 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1559618] Re: light-locker appears to incorrectly handle Kerberos ticket cache filenames
I do not thing that this a bug in light-locker, but in lightdm. Similar report: bug 1296276 ** Package changed: light-locker (Ubuntu) => lightdm (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1559618 Title: light-locker appears to incorrectly handle Kerberos ticket cache filenames Status in lightdm package in Ubuntu: Confirmed Bug description: When unlocking an Ubuntu 16.04 system which is using light-locker as the screen saver, Kerberos authentication works for a normal, unprivileged user, except that the resulting ticket cache is incorrectly named. Instead of the resulting ticket cache created as a result of such successful authentication being named something like: krb5cc_1000 (if the UID of the user is 1000) ...the cache file is named: krb5cc_0 (which would presumably be correct if root were logging in, but not a normal, unprivileged user) I am willing to help debug this issue, so if there is anything you would like me to try, please let me know. Thanks, Brian ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: light-locker 1.7.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 22:32:52 2016 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: light-locker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1559618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788597] Re: ubiquity broken with console-setup 1.178ubuntu2.5
I ran ubuntu-18.08.1 ISO, did a full-upgrade to console-setup 1.178ubuntu2.6, ran ubiquity, noted that it skipped the keyboard and wireless pages. I then enabled proposed, did a full-upgrade to console-setup 1.178ubuntu2.7, ran ubiquity, noted that it did not skip any pages. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1788597 Title: ubiquity broken with console-setup 1.178ubuntu2.5 Status in console-setup package in Ubuntu: Fix Committed Status in console-setup source package in Bionic: Fix Committed Bug description: [ SRU Justification ] Due to my brain being in the wrong language, a function was exiting the script instead of returning. Derp. [ Regression Potential ] N'much. [ Test Case ] Build a new ubiquity and see if we can haz keyboard again. [ Original Bug ] Since this version of console-setup in bionic ubiquity now skips the Keyboard and Wireless pages. http://launchpadlibrarian.net/382474004/console- setup_1.178ubuntu2.4_1.178ubuntu2.5.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488155] Re: apt failed to open translation file
No. This bug only existed on 15.10, it was fixed on 16.04
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1488155
Title:
apt failed to open translation file
Status in apt package in Ubuntu:
Incomplete
Bug description:
Ubuntu 15.10 + apt 1.0.9.10ubutnu6
When run `strace apt-cache show ubuntu-desktop' on my system, the
output shows it try to access non-exists translation file.
The description of specified package can't be displayed due to this
bug.
It seems that an overflow occured.
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-y%5fRelease.bz2",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-y%5fRelease.xz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-y%5fRelease.lzma",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-y%5fRelease.gz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-y%5fRelease.uncompressed",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-y%5fRelease",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-id%5fRelease.bz2",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-id%5fRelease.xz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-id%5fRelease.lzma",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-id%5fRelease.gz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-id%5fRelease.uncompressed",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_main_i18n_Translation-id%5fRelease",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-dists%5fwi%ff98%15%ffb2%13GV.bz2",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-dists%5fwi%ff98%15%ffb2%13GV.xz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-dists%5fwi%ff98%15%ffb2%13GV.lzma",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-dists%5fwi%ff98%15%ffb2%13GV.gz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-dists%5fwi%ff98%15%ffb2%13GV.uncompressed",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-dists%5fwi%ff98%15%ffb2%13GV",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-%ffc0I%ffb2%13GV.bz2",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-%ffc0I%ffb2%13GV.xz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-%ffc0I%ffb2%13GV.lzma",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-%ffc0I%ffb2%13GV.gz",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-%ffc0I%ffb2%13GV.uncompressed",
0x7ffe7e9622f0) = -1 ENOENT (No such file or directory)
stat("/var/lib/apt/lists/ftp.jaist.ac.jp_pub_Linux_ubuntu_dists_wily_multiverse_i18n_Translation-%ffc0I%ffb2%13GV",
0x7ffe7e9622f0) = -1 ENOENT (No such file or dir
[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
I've now pushed a PR which should alleviate the reboot issue
*partially*. The complexity in fixing this arises from the differing
behaviours of implementations of the shutdown, poweroff, and reboot
commands; upstart's poweroff & reboot commands for example, immediately
return (briefly) permitting the caller to query their exit codes. In
contrast, systemd's don't return at all unless the poweroff or reboot
fails. None of the reboot or poweroff implementations provide a
scheduling facility like the /sbin/shutdown implementation
(unsurprisingly), but systemd's poweroff and reboot commands *do* work
even in the post-trusty upgrade environment (even though systemd's
shutdown command doesn't).
The quandry is as follows: we can reliably detect when the shutdown
command fails (it exits with an exit code and some error messages), and
when it succeeds ... sort of. We currently schedule the shutdown for 4
minutes time and if it hasn't died within 10 seconds we assume it's
going to work; this assumes that the implementation won't fail at the
end of the schedule but so far that seems a reliable assumption under
both upstart and systemd. We cannot *reliably* detect when the poweroff
or reboot commands either succeed or fail, but they do seem reliable in
practice even in aberrant environments like the post-trusty upgrade.
So, the method I've chosen is as follows: treat shutdown and restart
requests as we presently do (schedule /bin/shutdown for 4 minutes time,
monitor for 10 seconds). If it succeeds, nothing changes. If it fails,
report the failure with an extra message indicating we are going to
attempt to force the procedure, then run /sbin/poweroff or /sbin/reboot
as appropriate. The result is that in the post-trusty environment
(testing on containers and VMs) a reboot request does succeed, but is
still reported as failing (albeit with an extended message explaining
we're going to try and force it).
We *could* report it as succeeding, but frankly there's no guarantees so
it's a choice between giving the user bad news ("sorry your reboot
request failed ...") with a possible silver lining ("... but we're going
to try another way which *might* work, however we won't be able to
tell"), or giving the user good news ("your reboot request worked after
we forced it") and hoping we're not lying! The former sounds like the
more sensible approach to me, and hence is what is in the PR
(https://github.com/CanonicalLtd/landscape-client/pull/55).
** Changed in: landscape-client (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
** Changed in: landscape-client (Ubuntu)
Status: Confirmed => In Progress
--
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/1670291
Title:
Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
Status in landscape-client package in Ubuntu:
In Progress
Status in systemd package in Ubuntu:
Incomplete
Status in landscape-client source package in Xenial:
Confirmed
Status in systemd source package in Xenial:
Incomplete
Bug description:
Used Landscape (Paid Canonical Subscription) to upgrade one of my
machines.
Landscape only shows "In Progress" for more than 8 hours now and asked
for a reboot of the machine in a second alert.
In the reboot attempt I get the message:
=
Failed to set wall message, ignoring: Method "SetWallMessage" with signature
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
Failed to call ScheduleShutdown in logind, proceeding with immediate
shutdown: Method "ScheduleShutdown" with signature "st" on interface
"org.freedesktop.login1.Manager" doesn't exist
=
Steps to reproduce:
* Fully updated 14.04.5 machine
* Open Landscape
* Choose the machine
* Choose Packages
* This computer can be upgraded to a newer release
* Apply
* Wait 2 hours
* Alert comes in a seperate Landscape message Machine is ready for reboot
* Choose Info... Power
* Deliver to selected computers as soon as possible
* Error message
I found this thread on reddit about this issue maybe the solution can be
built into the upgrade script
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836]
I use ubuntu 18.04 with 4.15 kernel I have hit the same problem, but with synaptics touchpad. I have bisected 4.13-4.14 and the problem was in commit 1455cf8dbfd06aa7651dcfccbadb7a093944ca65 (as in the attached patch) I am unable to use USB bus because udev is bogged down with these bind/unbind events ``` UDEV [496.168312] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.175932] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.176947] unbind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) UDEV [496.177602] unbind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.185259] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.185479] unbind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) UDEV [496.186342] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.196813] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.197103] unbind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) UDEV [496.197501] unbind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) KERNEL[496.207283] bind /devices/pci:00/:00:1d.0/usb2/2-1/2-1.4/2-1.4.2/2-1.4.2:1.0 (usb) ``` ``` > cat /sys/bus/usb/devices/2-1.4/2-1.4.2/id* 8162 413c ``` ``` > lsusb -d 413c:8162 Bus 002 Device 006: ID 413c:8162 Dell Computer Corp. Integrated Touchpad [Synaptics] ``` -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
i'm running debian. i'm using 686 (32 bit) and pae. what kernel are you running? kernel 4.9.0-5 works and 4.9.0-8 is broken (didn't check others). apt-get changelog linux-image-4.9.0-8-686-pae has lots of swap related notes so they definitely borked something. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in util-linux package in Ubuntu: New Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: util-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788854] [NEW] After update from xubuntu i686 version 04.16 to i686 04.18 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-remo
Public bug reported: I had 32-bits OS of Xubuntu from 04.16, and answered yes to be upgraded into 04.18 on my HP EliteBook 6930p laptop. Severals error came up after the reboot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Thu Aug 23 22:30:08 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-22 (1674 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago) ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1788854 Title: After update from xubuntu i686 version 04.16 to i686 04.18 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: I had 32-bits OS of Xubuntu from 04.16, and answered yes to be upgraded into 04.18 on my HP EliteBook 6930p laptop. Severals error came up after the reboot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Thu Aug 23 22:30:08 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-22 (1674 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
the changes that broke this seem to be related to the L1 terminal patches. i've linked the CVE numbers. maybe that will get us some help. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3620 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-3646 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
> RE -W/w in `host` , correct -- even with timeout set, it blocks forever (I tested this several days ago in the dup'd ticket iirc) > RE timeout , good thoughts all - sure let's just stick with 5 seconds then > RE logic true/false (@Trent) , thanks yes! that'll do it; clarified now in my mind -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: In Progress Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in strongswan package in Ubuntu: Invalid Status in avahi source package in Bionic: Triaged Status in bind9 source package in Bionic: Confirmed Status in avahi source package in Cosmic: In Progress Status in bind9 source package in Cosmic: Confirmed Status in avahi package in Debian: New Bug description: [Impact] * Network connections for some users fail (in some cases a direct interface, in others when connecting a VPN) because the 'host' command to check for .local in DNS called by /usr/lib/avahi/avahi-daemon- check-dns.sh never times out like it should - leaving the script hanging indefinitely blocking interface up and start-up. This appears to be a bug in host caused in some circumstances however we implement a workaround to call it under 'timeout' as the issue with 'host' has not easily been identified, and in any case acts as a fall-back. [Test Case] * Multiple people have been unable to create a reproducer on a generic machine (e.g. it does not occur in a VM), I have a specific machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM) by simply "ifdown br0; ifup br0" and there are clearly 10s of other users affected in varying circumstances that all involve the same symptoms but no clear test case exists. Best I can suggest is that I test the patch on my system to ensure it works as expected, and the change is only 1 line which is fairly easily auditible and understandable. [Regression Potential] * The change is a single line change to the shell script to call host with "timeout". When tested on working and non-working system this appears to function as expected. I believe the regression potential for this is subsequently low. * In attempt to anticipate possible issues, I checked that the timeout command is in the same path (/usr/bin) as the host command that is already called without a path, and the coreutils package (which contains timeout) is an Essential package. I also checked that timeout is not a built-in in bash, for those that have changed /bin/sh to bash (just in case). [Other Info] * N/A [Original Bug Description] On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 172.29.0.0 0.0.0.0 255.255.0.0 U 0 0 0 tun0 172.29.88.110.0.0.0 255.255.255.255 UH0 0 0 tun0 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlp2s0 liam@liam-lat:~$ ping 172.29.88.11 PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data. ^C --- 172.29.88.11 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3054ms ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: openconnect 7.08-3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 22:11:33 2018 InstallationDate: Installed on 2017-06-15 (258 days ago
[Touch-packages] [Bug 1734040] Re: openssh: The concurrency of settimeofday and ssh connect would lead to coredump
This was fixed upstream a while back in response to you reporting it directly to them (https://anongit.mindrot.org/openssh.git/commit/?id=5db6fbf1438b108e5df3e79a1b4de544373bc2d4); that fix was in OpenSSH 7.7p1 and is thus in cosmic. It might not be a bad idea to backport this fix to xenial and bionic, so I've opened bug tasks for that. ** Also affects: openssh (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: openssh (Ubuntu) Status: New => Fix Released -- 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/1734040 Title: openssh: The concurrency of settimeofday and ssh connect would lead to coredump Status in openssh package in Ubuntu: Fix Released Status in openssh source package in Xenial: New Status in openssh source package in Bionic: New Bug description: Hi, pals: we found a coredump when we do ssh connection. the basic information as follow: the stack trace in coredump: (gdb) bt #0 0x20007510 in raise () from /lib/libc.so.6 #1 0x2000c718 in abort () from /lib/libc.so.6 #2 0x2053d42c in __mulvsi3 (a=, b=) at /home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159 #3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, ms=0x48027c40, ms@entry=0xbfa20a98) at misc.c:871 #4 0x204d2568 in ssh_exchange_identification (timeout_ms=timeout_ms@entry=5000) at sshconnect.c:580 #5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, timeout_ms=5000) at sshconnect.c:1346 #6 0x204c433c in main (ac=, av=) at ssh.c:1326 the direct cause of the coredump, is that the function __mulvsi3 in gcc checked the plus operation is overflow, then this gcc function abort(). the reason of the overflow is cause by the time-setting operation when do ssh connect. in function ms_subtract_diff . the timeoutp get a very big value because of the time-change. So could we add a limitation for the differ of the 2 values get from gettimeofday ? if it's too big, would lead to overflow, we set a default value and report a warning log. thanks for you attention and expect your reply. B.R. Le Wang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1734040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661199] Re: Apt-cacher-ng fails on https repo
Reopening against acng for further consideration and possible discussion. ** Changed in: apt-cacher-ng (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1661199 Title: Apt-cacher-ng fails on https repo Status in apt package in Ubuntu: Won't Fix Status in apt-cacher-ng package in Ubuntu: New Bug description: Following the instructions to add the docker repo here: https://docs.docker.com/engine/installation/linux/ubuntu/ /etc/apt/sources.list contains the repo: deb https://apt.dockerproject.org/repo/ ubuntu-xenial main When running through apt-cacher-ng, apt-get update returns: $ sudo apt-get update Ign:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 https://apt.dockerproject.org/repo ubuntu-xenial Release Ign:3 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages.diff/Index Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Err:4 https://apt.dockerproject.org/repo ubuntu-xenial/main i386 Packages Received HTTP code 403 from proxy after CONNECT Ign:5 https://apt.dockerproject.org/repo ubuntu-xenial/main all Packages Ign:6 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en_US Ign:7 https://apt.dockerproject.org/repo ubuntu-xenial/main Translation-en Ign:8 https://apt.dockerproject.org/repo ubuntu-xenial/main amd64 Packages Ign:9 http://dl.google.com/linux/chrome/deb stable InRelease Hit:10 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:11 http://dl.google.com/linux/chrome/deb stable Release Hit:13 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:14 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done W: The repository 'https://apt.dockerproject.org/repo ubuntu-xenial Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-xenial/main/binary-i386/Packages Received HTTP code 403 from proxy after CONNECT E: Some index files failed to download. They have been ignored, or old ones used instead. When apt is set to disable the proxy, using the following /etc/apt/apt.conf: Acquire::http::Proxy "http://127.0.0.1:/";; Acquire::https::Proxy "DIRECT"; (note that the port has been changed from the default) The response is: $ sudo apt-get update Hit:1 https://apt.dockerproject.org/repo ubuntu-xenial InRelease Ign:2 http://dl.google.com/linux/chrome/deb stable InRelease Hit:3 http://archive.ubuntu.com/ubuntu xenial InRelease Hit:4 http://dl.google.com/linux/chrome/deb stable Release Hit:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease Hit:7 http://archive.ubuntu.com/ubuntu xenial-security InRelease Reading package lists... Done
[Touch-packages] [Bug 1788868] [NEW] installed systemd-shim package post-removal script subprocess returned error exit status 2cess returned error exit status 2grade: installed systemd-shim package po
Public bug reported: erreur sur mise à jour partielle ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 22 11:44:47 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-03 (1693 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- 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/1788868 Title: installed systemd-shim package post-removal script subprocess returned error exit status 2cess returned error exit status 2grade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: erreur sur mise à jour partielle ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 22 11:44:47 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-03 (1693 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788868/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
Charlie, as regards me: - Ubuntu 18.04 - Linux 4.15.0-33-generic #36-Ubuntu GNU/Linux - util-linux|mount 2.31.1-0.4ubuntu3.1 affected - Ubuntu 16.04 - Linux 4.15.0-33-generic #36~16.04.1-Ubuntu GNU/Linux - util-linux|mount 2.27.1-6ubuntu3.6 not affected -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Confirmed Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR
see also bug 685194 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1648107 Title: $XAUTHORITY should move into $XDG_RUNTIME_DIR Status in lightdm package in Ubuntu: Triaged Bug description: Historically, the X authority file was placed into $HOME/.Xauthority such that X11 clients on remote servers could access it in environments in which $HOME is located on a network file system. Today, this practice has become an anachronism that causes far more problems than it solves: a) Remote X11 clients are typically started today via "ssh -X", which emulates its own X11 server port $DISPLAY and therefore always creates its own X authority file entry on the remote server. Therefore, there is no longer any practical benefit from having the X authority file located in $HOME. b) If $HOME is on a network file system that implements "root squash", then commands such as "sudo xterm" or "sudo wireshark" won't work to start an X client with root privileges, as root is not able to read ~/.Xauthority via NFS. :-( c) If $HOME is on a network file system with Kerberos authentication, then users can easily get locked out by their screensavers once the Kerberos ticket expires. This is because some screen lockers (e.g., gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome- screensaver/gnome-screensaver-dialog) in order to ask the user of a locked screen for their password. Such a tool needs to access $XAUTHORITY right before it can display the password prompt, which will fail if the user's Kerberos ticket has expired (e.g. because a machine was suspended for 24 hours and therefore the ticket was not refreshed automatically on time). Without the ability to ask for a password, the screensaver then cannot call pam_krb5 to renew the user's Kerberos ticket, and the user remains locked out in a deadlock situation. :-( Both b) and c) are regular reasons for support requests in educational/corporate Linux environments with $HOME on Kerberized NFS. The solution is simple. Instead of $HOME/.Xauthority, just use in future $XDG_RUNTIME_DIR/xauthority as the location of the X authority file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER might be a suitable fallback option.) According to https://standards.freedesktop.org/basedir-spec/basedir- spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for holding the X authority file: it is always located in a local tmpfs filesystem, guaranteed to be accessible only to the current user, and will be wiped when the user has closed all sessions. On modern Linux systems, pam_systemd usually creates XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end. (Note that according to https://standards.freedesktop.org/basedir-spec /basedir-spec-latest.html you should set the "sticky bit" on any files created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.) Feature request: please provide an option for LightDM to do the equivalent of export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority chmod +t $XAUTHORITY and encourage Linux distribution maintainers to set this option by default, such that ~/.Xauthority is no longer used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 537970]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/314. -- 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/537970 Title: Evince does not print images in some pdf files. Status in Poppler: Unknown Status in cups package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in poppler package in Ubuntu: Confirmed Bug description: Binary package hint: evince Evince fails to print the image in .pdf file. It shows up correctly in preview, acroread prints it properly. To reproduce: 1) Download this here invoice: http://www.mlink.net.pl/~imachine/faktura_24_2010_12-03-2010.pdf 2) Preview in Evince - company logo is here. 3) Print - company logo is not on paper. Frustrating, used to work, just stopped at some point, too far back in time now to find out tho :/ Cheers! ProblemType: Bug Architecture: amd64 Date: Fri Mar 12 10:58:00 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.29.91-0ubuntu2 ProcEnviron: SHELL=/bin/bash LANG=pl_PL.utf8 LANGUAGE=pl_PL:pl:en_GB:en ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: evince Uname: Linux 2.6.32-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/537970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 299409]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/poppler/poppler/issues/308. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/299409 Title: saving a copy of a pdf form deletes all content excepting filled fields Status in Evince: Unknown Status in poppler package in Ubuntu: Triaged Bug description: Binary package hint: evince Ubuntu 8.10 evince 2.24.1 i have to fill a pdf form, when i save a copy of this file whitout filling any field then all the content is save. When i save a copy with one ore more fields filled, only filled fields are saved and all other content is lost. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.24.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SourcePackage: evince Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/299409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1728077] Re: Evince uses wrong encoding when filling out a PDF form
Launchpad has imported 6 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103492.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2017-10-27T19:09:19+00:00 Thomas Dreibholz wrote:
Evince and Okular (based on poppler) uses the wrong encoding when
filling out a PDF form.
How to reproduce:
- Get the official Chinese Visa Application Form from
http://www.china-embassy.org/eng/visas/fd/W020130830801798289342.pdf
- Open it in Evince
- Fill in a name (e.g. "Smith"). The entered text is displayed correctly.
- Click into another filed
- The previously entered name is displayed in wrong characters (wrong encoding
used?). E.g. "Smith" becomes "4NJUI".
- Saving and loading the PDF (with the entered text) also results in displaying
wrong characters
- Clicking into the name filed results in displaying the correct name ("Smith")
=> It seems that somewhere in Evince (or libpoppler?) the wrong encoding
is used for displaying non-active input fields.
Tested Ubuntu versions:
- Ubuntu 16.04
- Ubuntu 17.10
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1728077/comments/3
On 2017-10-27T19:29:36+00:00 Thomas Dreibholz wrote:
Created attachment 135133
Screenshot: filling in text into a field of the form
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1728077/comments/5
On 2017-10-27T19:31:43+00:00 Thomas Dreibholz wrote:
Created attachment 135134
Screenshot: filling in text into a field of the form
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1728077/comments/6
On 2017-10-27T19:32:31+00:00 Thomas Dreibholz wrote:
Created attachment 135135
Screenshot: result after activating another field of the form
Reply at:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1728077/comments/7
On 2017-10-27T19:43:32+00:00 Thomas Dreibholz wrote:
The PDF form contains a couple of fonts -- some are embedded, some are
not -- with a couple of different encodings. May be something in
libpoppler goes wrong with the font encoding handling for the form's
fields?
$ pdffonts W020130830801798289342.pdf
name type encoding emb sub
uni object ID
- --- ---
--- -
ZJWNJQ+SimSunCID TrueType Identity-H yes yes
yes 1780 0
AASELS+TimesNewRoman,BoldCID TrueType Identity-H yes yes
yes 1785 0
JEIVZQ+SimSunCID TrueType Identity-H yes yes
yes 1787 0
HRUUFF+SimSunCID TrueType Identity-H yes yes
yes 1789 0
TimesNewRomanPS-BoldItalicMT TrueType WinAnsi no no
no1791 0
TimesNewRomanPSMTTrueType WinAnsi no no
no1793 0
Times-Roman Type 1Custom no no
no1689 0
AdobeSongStd-Light CID Type 0UniGB-UTF16-Hno no
no1692 0
SimHei CID TrueType UniGB-UTF16-Hno no
no1693 0
SimSun CID TrueType UniGB-UTF16-Hno no
no1694 0
TimesNewRomanTrueType WinAnsi no no
no1695 0
MicrosoftYaHei CID TrueType UniGB-UTF16-Hno no
no1717 0
MicrosoftYaHei,Bold CID TrueType UniGB-UTF16-Hno no
no1718 0
NSimSun CID TrueType UniGB-UTF16-Hno no
no1719 0
AdobeSongStd-Light CID Type 0UniGB-UTF16-Hno no
no1772 0
ZJWNJQ+SimSunCID TrueType Identity-H yes yes
yes285 0
TimesNewRomanPSMTTrueType WinAnsi no no
no 289 0
ZJWNJQ+SimSunCID TrueType Identity-H yes yes
yes372 0
QGJLNI+CambriaMath CID TrueType Identity-H yes yes
yes377 0
TimesNewRomanPSMTTrueType WinAnsi no no
no 379 0
AdobeSongStd-Light CID Type 0UniGB-UTF16-Hno no
no 361 0
TimesNewRomanPS-BoldItalicMT TrueType WinAnsi no no
no 398 0
KozMinPr6N-Regular CID Type 0UniJIS-UTF16-H no no
[Touch-packages] [Bug 537970] Re: Evince does not print images in some pdf files.
** Changed in: poppler Status: Confirmed => Unknown -- 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/537970 Title: Evince does not print images in some pdf files. Status in Poppler: Unknown Status in cups package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: Confirmed Status in poppler package in Ubuntu: Confirmed Bug description: Binary package hint: evince Evince fails to print the image in .pdf file. It shows up correctly in preview, acroread prints it properly. To reproduce: 1) Download this here invoice: http://www.mlink.net.pl/~imachine/faktura_24_2010_12-03-2010.pdf 2) Preview in Evince - company logo is here. 3) Print - company logo is not on paper. Frustrating, used to work, just stopped at some point, too far back in time now to find out tho :/ Cheers! ProblemType: Bug Architecture: amd64 Date: Fri Mar 12 10:58:00 2010 DistroRelease: Ubuntu 10.04 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.29.91-0ubuntu2 ProcEnviron: SHELL=/bin/bash LANG=pl_PL.utf8 LANGUAGE=pl_PL:pl:en_GB:en ProcVersionSignature: Ubuntu 2.6.32-16.25-generic SourcePackage: evince Uname: Linux 2.6.32-16-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/537970/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 299409] Re: saving a copy of a pdf form deletes all content excepting filled fields
** Changed in: evince Status: Confirmed => Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/299409 Title: saving a copy of a pdf form deletes all content excepting filled fields Status in Evince: Unknown Status in poppler package in Ubuntu: Triaged Bug description: Binary package hint: evince Ubuntu 8.10 evince 2.24.1 i have to fill a pdf form, when i save a copy of this file whitout filling any field then all the content is save. When i save a copy with one ore more fields filled, only filled fields are saved and all other content is lost. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 ExecutablePath: /usr/bin/evince NonfreeKernelModules: nvidia Package: evince 2.24.1-0ubuntu1 ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=fr_FR.UTF-8 SourcePackage: evince Uname: Linux 2.6.27-7-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/299409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck
I've been trying to figure out how to test this with dig instead, and I think I found something. If you have a normal /etc/resolv.conf then you see this: === $ dig -t soa local.; echo $? ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> -t soa local. ;; global options: +cmd ;; Got answer: ;; WARNING: .local is reserved for Multicast DNS ;; You are currently testing what happens when an mDNS query is leaked to DNS ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2061 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;local. IN SOA ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Fri Aug 24 09:16:38 MDT 2018 ;; MSG SIZE rcvd: 34 0 === If, instead, you add "local" to the search then you get this: === $ dig -t soa local.; echo $? ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> -t soa local. ;; global options: +cmd ;; connection timed out; no servers could be reached 9 === This may not be a good test (maybe under some other configuration some sort of response is sent?), but it might be a good idea to figure out how to accomplish this without using host. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1752411 Title: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck Status in avahi package in Ubuntu: In Progress Status in bind9 package in Ubuntu: Confirmed Status in openconnect package in Ubuntu: Invalid Status in strongswan package in Ubuntu: Invalid Status in avahi source package in Bionic: Triaged Status in bind9 source package in Bionic: Confirmed Status in avahi source package in Cosmic: In Progress Status in bind9 source package in Cosmic: Confirmed Status in avahi package in Debian: New Bug description: [Impact] * Network connections for some users fail (in some cases a direct interface, in others when connecting a VPN) because the 'host' command to check for .local in DNS called by /usr/lib/avahi/avahi-daemon- check-dns.sh never times out like it should - leaving the script hanging indefinitely blocking interface up and start-up. This appears to be a bug in host caused in some circumstances however we implement a workaround to call it under 'timeout' as the issue with 'host' has not easily been identified, and in any case acts as a fall-back. [Test Case] * Multiple people have been unable to create a reproducer on a generic machine (e.g. it does not occur in a VM), I have a specific machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM) by simply "ifdown br0; ifup br0" and there are clearly 10s of other users affected in varying circumstances that all involve the same symptoms but no clear test case exists. Best I can suggest is that I test the patch on my system to ensure it works as expected, and the change is only 1 line which is fairly easily auditible and understandable. [Regression Potential] * The change is a single line change to the shell script to call host with "timeout". When tested on working and non-working system this appears to function as expected. I believe the regression potential for this is subsequently low. * In attempt to anticipate possible issues, I checked that the timeout command is in the same path (/usr/bin) as the host command that is already called without a path, and the coreutils package (which contains timeout) is an Essential package. I also checked that timeout is not a built-in in bash, for those that have changed /bin/sh to bash (just in case). [Other Info] * N/A [Original Bug Description] On 18.04 Openconnect connects successfully to any of multiple VPN concentrators but network traffic does not flow across the VPN tunnel connection. When testing on 16.04 this works flawlessly. This also worked on this system when it was on 17.10. I have tried reducing the mtu of the tun0 network device but this has not resulted in me being able to successfully ping the IP address. Example showing ping attempt to the IP of DNS server: ~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 172.29.88.11 nameserver 127.0.0.53 liam@liam-lat:~$ netstat -nr Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 0.0.0.0 192.168.1.1 0.0.0.0 UG0 0 0 wlp2s0 105.27.198.106 192.168.1.1 255.255.255.255 UGH 0 0 0 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U
Re: [Touch-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so
I adjusted the sound according to your advice. Thank you very much. The package system message has now been corrupted. I can not download and install the update. 2018-08-23, kt, 05:10 Daniel van Vugt rašė: > Please run this command all on one line: > > sudo sh -c "echo 'realtime-scheduling = no' >> /etc/pulse/daemon.conf" > > and then reboot. Does that fix the problem? > > ** Changed in: pulseaudio (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1788471 > > Title: > There is no sound when you turn on the tube. Sometimes the sound is. I > do not understand why this is so > > Status in pulseaudio package in Ubuntu: > Incomplete > > Bug description: > There is no sound when you turn on the tube. Sometimes the sound is. I > do not understand why this is so > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: pulseaudio 1:11.1-1ubuntu7.1 > Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 > ApportVersion: 2.20.9-0ubuntu7.2 > Architecture: amd64 > AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', > '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', > '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', > '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', > '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit > code 1: > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 22 22:04:28 2018 > InstallationDate: Installed on 2018-08-13 (8 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 > (20180105.1) > 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-08-13 (8 days ago) > dmi.bios.date: 08/07/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 5.11 > dmi.board.asset.tag: Default string > dmi.board.name: Default string > dmi.board.vendor: AMI Corporation > dmi.board.version: Default string > dmi.chassis.asset.tag: Default string > dmi.chassis.type: 3 > dmi.chassis.vendor: Default string > dmi.chassis.version: Default string > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: > dmi.product.family: Default string > dmi.product.name: Default string > dmi.product.version: Default string > dmi.sys.vendor: Default string > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788471/+subscriptions > ** Attachment added: "IMG_20180824_182634.jpg" https://bugs.launchpad.net/bugs/1788471/+attachment/5180341/+files/IMG_20180824_182634.jpg -- 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/1788471 Title: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 22:04:28 2018 InstallationDate: Installed on 2018-08-13 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) 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-08-13 (8 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:c
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
Please put this back in. I never understand why developers /remove/ features instead of leaving them in and making it an option. The previous org->gnome->nautilus->preferences setting accomplished this fine and should have been left active. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788893] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear()
*** This bug is a duplicate of bug 1750253 *** https://bugs.launchpad.net/bugs/1750253 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1750253, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1788893/+attachment/5180342/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1788893/+attachment/5180344/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1788893/+attachment/5180347/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1788893/+attachment/5180348/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1788893/+attachment/5180349/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1788893/+attachment/5180350/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1788893/+attachment/5180351/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1750253 ibus-daemon crashed with SIGABRT in g_mutex_clear() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1788893 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() Status in ibus package in Ubuntu: New Bug description: Hello, I do not know why this happened... Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: ibus 1.5.17-3ubuntu4 Uname: Linux 4.18.4-041804-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Aug 24 07:55:13 2018 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2017-10-13 (314 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcCmdline: ibus-daemon --xim --panel disable ProcEnviron: LANGUAGE=es_CL:es PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_CL.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () g_closure_invoke () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1788893/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1788471] Re: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so
The red "-" icon appears. He did not exist before. See picture. 2018-08-24, pn, 18:30 Jonas Zikaras rašė: > I adjusted the sound according to your advice. Thank you very much. The > package system message has now been corrupted. I can not download and > install the update. > > 2018-08-23, kt, 05:10 Daniel van Vugt > rašė: > >> Please run this command all on one line: >> >> sudo sh -c "echo 'realtime-scheduling = no' >> /etc/pulse/daemon.conf" >> >> and then reboot. Does that fix the problem? >> >> ** Changed in: pulseaudio (Ubuntu) >>Status: New => Incomplete >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1788471 >> >> Title: >> There is no sound when you turn on the tube. Sometimes the sound is. I >> do not understand why this is so >> >> Status in pulseaudio package in Ubuntu: >> Incomplete >> >> Bug description: >> There is no sound when you turn on the tube. Sometimes the sound is. I >> do not understand why this is so >> >> ProblemType: Bug >> DistroRelease: Ubuntu 18.04 >> Package: pulseaudio 1:11.1-1ubuntu7.1 >> Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 >> ApportVersion: 2.20.9-0ubuntu7.2 >> Architecture: amd64 >> AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', >> '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', >> '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', >> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', >> '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit >> code 1: >> CurrentDesktop: ubuntu:GNOME >> Date: Wed Aug 22 22:04:28 2018 >> InstallationDate: Installed on 2018-08-13 (8 days ago) >> InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 >> (20180105.1) >> 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-08-13 (8 days ago) >> dmi.bios.date: 08/07/2017 >> dmi.bios.vendor: American Megatrends Inc. >> dmi.bios.version: 5.11 >> dmi.board.asset.tag: Default string >> dmi.board.name: Default string >> dmi.board.vendor: AMI Corporation >> dmi.board.version: Default string >> dmi.chassis.asset.tag: Default string >> dmi.chassis.type: 3 >> dmi.chassis.vendor: Default string >> dmi.chassis.version: Default string >> dmi.modalias: >> dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: >> dmi.product.family: Default string >> dmi.product.name: Default string >> dmi.product.version: Default string >> dmi.sys.vendor: Default string >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1788471/+subscriptions >> > -- 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/1788471 Title: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so Status in pulseaudio package in Ubuntu: Incomplete Bug description: There is no sound when you turn on the tube. Sometimes the sound is. I do not understand why this is so ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 Uname: Linux 4.16.0-rc3-stockmind-gpdpocket x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer', '/dev/sequencer2', '/dev/sequencer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Aug 22 22:04:28 2018 InstallationDate: Installed on 2018-08-13 (8 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) 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-08-13 (8 days ago) dmi.bios.date: 08/07/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd08/07/2017:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnAMICorporation:rnD
[Touch-packages] [Bug 1750253] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear()
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1750253 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() Status in ibus package in Ubuntu: Confirmed Bug description: With sddm Displaymanger. gdm3 goes automatic to Ubuntu Wayland. No change possible. No Mouse click possibele but mouse moved. Can't change the Displaymanger. SDDM Change possible. Ubuntu or Gnome not started. Scroll Lock flashed. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Feb 18 15:20:13 2018 ExecutablePath: /usr/bin/ibus-daemon ProcCmdline: ibus-daemon --xim --panel disable ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: Upgraded to bionic on 2017-12-04 (76 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1750253/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788894] [NEW] Hash Sum mismatch: DEP-11 Icons
Public bug reported: During update with apt, checking dependencies for a snap: Get:1 http://archive.canonical.com/ubuntu bionic InRelease [10.2 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:3 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic InRelease [15.4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2344 B] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2340 B] Get:8 http://archive.canonical.com/ubuntu bionic/partner Translation-en [1272 B] Get:9 http://archive.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Get:10 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main amd64 Packages [1068 B] Get:11 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main i386 Packages [1072 B] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1019 kB] Get:13 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main Translation-en [356 B] Get:14 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages [1007 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 DEP-11 Metadata [477 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 48x48 Icons [118 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 64x64 Icons [245 kB] Get:19 http://archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [9184 B] Get:20 http://archive.ubuntu.com/ubuntu bionic/restricted i386 Packages [9156 B] Get:21 http://arch
[Touch-packages] [Bug 1788894] Re: Hash Sum mismatch: DEP-11 Icons
This is not an issue in appstream, but likely the Ubuntu archive. But it could also be snapcraft doing something weird (that cache path is odd!). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1788894 Title: Hash Sum mismatch: DEP-11 Icons Status in appstream package in Ubuntu: New Status in apt package in Ubuntu: New Bug description: During update with apt, checking dependencies for a snap: Get:1 http://archive.canonical.com/ubuntu bionic InRelease [10.2 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:3 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic InRelease [15.4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2344 B] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2340 B] Get:8 http://archive.canonical.com/ubuntu bionic/partner Translation-en [1272 B] Get:9 http://archive.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Get:10 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main amd64 Packages [1068 B] Get:11 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main i386 Packages [1072 B] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1019 kB] Get:13 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main Translation-en [356 B] Get:14 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages [1007 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 DEP-11 Metadata [477 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 48x48 Icons [118 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 64x64 Icons [245 kB] Get:19 http://archive.
[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
I thought one aspect of the bug that nobody specifically highlighted was interesting: 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 Notice the replacement has an extra .systemd on the end of the name. The fix instructions reported above worked 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Confirmed Status in systemd-shim package in Ubuntu: Incomplete Status in systemd source package in Bionic: Confirmed Status in systemd-shim source package in Bionic: Confirmed Bug description: $ 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 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR
LightDM is already able to create the xauthority file locally under $XDG_RUNTIME_DIR, using configuration option user-authority-in-system- dir. This option is off by default on Ubuntu 16.04/18.04, but can be enabled with # echo -e '[LightDM]\nuser-authority-in-system-dir=true' >/etc/lightdm/lightdm.conf.d/50-user-authority-in-system-dir.conf LightDM then sets XAUTHORITY=/var/run/lightdm/$USER/xauthority instead of $HOME/.Xauthority. However, this path goes through the symbolic link /var/run -> /run. For some reason (why?) snap does not like such symlinks, resulting in a warning: # snap install pdftk # pdftk 2018/08/24 17:32:48.267771 cmd_run.go:442: WARNING: XAUTHORITY environment value is not a clean path: "/run/lightdm/mgk25/xauthority" A workaround to canonicalize the XAUTHORITY path (to eliminate symlinks) can be installed with e.g. # echo 'XAUTHORITY=`readlink -f "$XAUTHORITY"` && [ -z "$XAUTHORITY" ] && export XAUTHORITY' >/etc/X11/Xsession.d/10canonicalize-xauthority It would be nicer if LightDM directly used a canonical path in XAUTHORITY with user-authority-in-system-dir=true, or if snap didn't have to be so picky about symbolic links. (LightDM currently does not set ICEAUTHORITY when user-authority-in- system-dir=true.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1648107 Title: $XAUTHORITY should move into $XDG_RUNTIME_DIR Status in lightdm package in Ubuntu: Triaged Bug description: Historically, the X authority file was placed into $HOME/.Xauthority such that X11 clients on remote servers could access it in environments in which $HOME is located on a network file system. Today, this practice has become an anachronism that causes far more problems than it solves: a) Remote X11 clients are typically started today via "ssh -X", which emulates its own X11 server port $DISPLAY and therefore always creates its own X authority file entry on the remote server. Therefore, there is no longer any practical benefit from having the X authority file located in $HOME. b) If $HOME is on a network file system that implements "root squash", then commands such as "sudo xterm" or "sudo wireshark" won't work to start an X client with root privileges, as root is not able to read ~/.Xauthority via NFS. :-( c) If $HOME is on a network file system with Kerberos authentication, then users can easily get locked out by their screensavers once the Kerberos ticket expires. This is because some screen lockers (e.g., gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome- screensaver/gnome-screensaver-dialog) in order to ask the user of a locked screen for their password. Such a tool needs to access $XAUTHORITY right before it can display the password prompt, which will fail if the user's Kerberos ticket has expired (e.g. because a machine was suspended for 24 hours and therefore the ticket was not refreshed automatically on time). Without the ability to ask for a password, the screensaver then cannot call pam_krb5 to renew the user's Kerberos ticket, and the user remains locked out in a deadlock situation. :-( Both b) and c) are regular reasons for support requests in educational/corporate Linux environments with $HOME on Kerberized NFS. The solution is simple. Instead of $HOME/.Xauthority, just use in future $XDG_RUNTIME_DIR/xauthority as the location of the X authority file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER might be a suitable fallback option.) According to https://standards.freedesktop.org/basedir-spec/basedir- spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for holding the X authority file: it is always located in a local tmpfs filesystem, guaranteed to be accessible only to the current user, and will be wiped when the user has closed all sessions. On modern Linux systems, pam_systemd usually creates XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end. (Note that according to https://standards.freedesktop.org/basedir-spec /basedir-spec-latest.html you should set the "sticky bit" on any files created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.) Feature request: please provide an option for LightDM to do the equivalent of export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority chmod +t $XAUTHORITY and encourage Linux distribution maintainers to set this option by default, such that ~/.Xauthority is no longer used. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788894] Re: Hash Sum mismatch: DEP-11 Icons
Not sure what's going on, adding snapcragt and launchpad tasks for those folks to chime in ** Changed in: appstream (Ubuntu) Status: New => Invalid ** Also affects: snapcraft (Ubuntu) Importance: Undecided Status: New ** Also affects: snapcraft Importance: Undecided Status: New ** Also affects: launchpad Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1788894 Title: Hash Sum mismatch: DEP-11 Icons Status in Launchpad itself: New Status in Snapcraft: New Status in appstream package in Ubuntu: Invalid Status in apt package in Ubuntu: New Status in snapcraft package in Ubuntu: New Bug description: During update with apt, checking dependencies for a snap: Get:1 http://archive.canonical.com/ubuntu bionic InRelease [10.2 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:3 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic InRelease [15.4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2344 B] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2340 B] Get:8 http://archive.canonical.com/ubuntu bionic/partner Translation-en [1272 B] Get:9 http://archive.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Get:10 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main amd64 Packages [1068 B] Get:11 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main i386 Packages [1072 B] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1019 kB] Get:13 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main Translation-en [356 B] Get:14 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages [1007 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 DEP-11 Metadata [477 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 48x48 Icons [118 kB]
[Touch-packages] [Bug 1786151] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
FIX: rm /usr/share/dbus-1/system- services/org.freedesktop.systemd1.service -- 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/1786151 Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: Error occurred during upgrade from 16.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Aug 8 23:30:59 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-04-06 (1585 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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.3 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-09 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788920] Re: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1788920 Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Trying to apt-get update. Error shows dpkg lock. Lock removed and processes killed. dpkg issue still remains ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1737 F pulseaudio stu4064 F pulseaudio /dev/snd/controlC0: gdm1737 F pulseaudio stu4064 F pulseaudio Date: Fri Aug 24 19:54:14 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 MachineType: Alienware Alienware 17 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=f6521a16-70d8-461f-a2b9-1717699f5e77 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 04WT2G dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd02/25/2014:svnAlienware:pnAlienware17:pvrA09:rvnAlienware:rn04WT2G:rvrA00:cvnAlienware:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A09 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1788920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788920] [NEW] package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Trying to apt-get update. Error shows dpkg lock. Lock removed and processes killed. dpkg issue still remains ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1737 F pulseaudio stu4064 F pulseaudio /dev/snd/controlC0: gdm1737 F pulseaudio stu4064 F pulseaudio Date: Fri Aug 24 19:54:14 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 MachineType: Alienware Alienware 17 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=f6521a16-70d8-461f-a2b9-1717699f5e77 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 04WT2G dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd02/25/2014:svnAlienware:pnAlienware17:pvrA09:rvnAlienware:rn04WT2G:rvrA00:cvnAlienware:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A09 dmi.sys.vendor: Alienware ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1788920 Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Trying to apt-get update. Error shows dpkg lock. Lock removed and processes killed. dpkg issue still remains ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1737 F pulseaudio stu4064 F pulseaudio /dev/snd/controlC0: gdm1737 F pulseaudio stu4064 F pulseaudio Date: Fri Aug 24 19:54:14 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 MachineType: Alienware Alienware 17 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=f6521a16-70d8-461f-a2b9-1717699f5e77 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.2 SourcePackage: initramfs-tools Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2014 dmi.bios.vendor: Alienware dmi.bios.version: A09 dmi.board.name: 04WT2G dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A09 dmi.modalias: dmi:bvnAlienware:bvrA09:bd02/25/2014:svnAlienware:pnAlienware17:pvrA09:rvnAlienware:rn04WT2G:rvrA00:cvnAlienware:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Alienware 17 dmi.product.version: A09 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1788920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1788927] Re: Removing repo key doesn't work
*** This bug is a duplicate of bug 1656100 *** https://bugs.launchpad.net/bugs/1656100 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1656100, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1656100 Unable to remove signing keys using gnome-software-properties -- 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/1788927 Title: Removing repo key doesn't work Status in software-properties package in Ubuntu: New Bug description: Removing an apt key from within the software-properties GUI doesn't work, neither before (when the permission is not granted to the process and cached already) nor after entering the user password in the polkit prompt. Existance and enabled state of the repository related to the key doesn't influence the result either. software-properties-gtk --debug doesn't print information about the deletion of the key either. Steps to reproduce: 1) Add ppa via add-apt-repository to add an apt repo incl. key import 2) Open software-properties-gtk 3) Jump to the "Authentication" tab 4) Select a key and press the "Remove" button Expected behaviour: Key is successfully removed Actual behaviour: Key is not removed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 24 21:31:58 2018 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1788927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788937] [NEW] intel hd4600
Public bug reported: intel hd4600 no support 3d ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 24 23:20:16 2018 DistUpgraded: 2018-08-24 19:16:53,465 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:0250] InstallationDate: Installed on 2018-08-24 (0 days ago) InstallationMedia: Xubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Wortmann_AG TERRA_MOBILE_1541H ProcEnviron: LANGUAGE=uk TERM=xterm-256color PATH=(custom, no user) LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=68556d80-aa29-43b8-abad-a9d08b5469fb ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago) dmi.bios.date: 05/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W25CSW dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/08/2014:svnWortmann_AG:pnTERRA_MOBILE_1541H:pvrNotApplicable:rvnClevo:rnW25CSW:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TERRA_MOBILE_1541H dmi.product.version: Not Applicable dmi.sys.vendor: Wortmann_AG version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808241830.bcb9d9~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 18.3~git1808170730.de3b34~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 18.3~git1808170730.de3b34~oibaf~b 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.99+git1808241930.cba8fe~oibaf~b version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1807201025.3d3950~oibaf~b version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15+git1807201019.ac8f7b~oibaf~b ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1788937 Title: intel hd4600 Status in xorg package in Ubuntu: New Bug description: intel hd4600 no support 3d ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Aug 24 23:20:16 2018 DistUpgraded: 2018-08-24 19:16:53,465 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:0250] InstallationDate: Installed on 2018-08-24 (0 days ago) InstallationMedia: Xubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Wortmann_AG TERRA_MOBILE_1541H ProcEnviron: LANGUAGE=uk TERM=xterm-256color PATH=(custom, no user) LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=68556d80-aa29-43b8-abad-a9d08b5469fb ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-08-24 (0 days ago) dmi.bios.date: 05/08/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W25CSW dmi.board.vendor: Clevo dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Clevo dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd05/08/2014:svnWortmann_AG:pnTERRA_MOBILE_1541H:pvrNotApplicable:rvnClevo:rnW25CSW:rvrNotApplicable:cvnClevo:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TERRA_MOBILE_1541H dmi.product.version: Not Applicable dmi.sys.vendor: Wortmann_AG version.compiz: compiz N/A ver
[Touch-packages] [Bug 1788927] [NEW] Removing repo key doesn't work
Public bug reported: Removing an apt key from within the software-properties GUI doesn't work, neither before (when the permission is not granted to the process and cached already) nor after entering the user password in the polkit prompt. Existance and enabled state of the repository related to the key doesn't influence the result either. software-properties-gtk --debug doesn't print information about the deletion of the key either. Steps to reproduce: 1) Add ppa via add-apt-repository to add an apt repo incl. key import 2) Open software-properties-gtk 3) Jump to the "Authentication" tab 4) Select a key and press the "Remove" button Expected behaviour: Key is successfully removed Actual behaviour: Key is not removed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 24 21:31:58 2018 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages wayland-session ** Description changed: - Removing an apt key from within the software-properties GUI doesn't work, neither before nor after entering the user password in the polkit prompt. + Removing an apt key from within the software-properties GUI doesn't work, neither before (when the permission is not granted to the process and cached already) nor after entering the user password in the polkit prompt. Existance and enabled state of the repository related to the key doesn't influence the result either. software-properties-gtk --debug doesn't print information about the deletion of the key either. Steps to reproduce: 1) Add ppa via add-apt-repository to add an apt repo incl. key import 2) Open software-properties-gtk 3) Jump to the "Authentication" tab 4) Select a key and press the "Remove" button Expected behaviour: Key is successfully removed Actual behaviour: Key is not removed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 24 21:31:58 2018 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1788927 Title: Removing repo key doesn't work Status in software-properties package in Ubuntu: New Bug description: Removing an apt key from within the software-properties GUI doesn't work, neither before (when the permission is not granted to the process and cached already) nor after entering the user password in the polkit prompt. Existance and enabled state of the repository related to the key doesn't influence the result either. software-properties-gtk --debug doesn't print information about the deletion of the key either. Steps to reproduce: 1) Add ppa via add-apt-repository to add an apt repo incl. key import 2) Open software-properties-gtk 3) Jump to the "Authentication" tab 4) Select a key and press the "Remove" button Expected behaviour: Key is successfully removed Actual behaviour: Key is not removed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: software-properties-gtk 0.96.24.32.4 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Aug 24 21:31:58 2018 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1788927/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock
This was tested on Ubuntu 18.04.1 LTS and is working perfectly. Big thanks to everyone who's worked on this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1651818 Title: busybox-initramfs needs different compile options to work with cryptroot-unlock Status in busybox package in Ubuntu: Won't Fix Status in cryptsetup package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Fix Committed Bug description: SRU for bionic: Acceptance criteria: An encrypted partition can be decrypted using cryptroot-unlock. Regression potential: It's not the default method, so unused by the majority of people. Besides that the patched script runs fine in cosmic. The cryptroot-unlock script in the cryptsetup package does not work in initramfs. It fails because "ps -e" is not available in busybox for initramfs. When building the package with CONFIG_DESKTOP=y CONFIG_EXTRA_COMPAT=y the needed commands (ps, grep) with parameter are there and it works. Tetsted on Ubuntu GNOME 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1651818/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788854] Re: After update from xubuntu i686 version 16.04 to i686 18.04 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-remova
** Summary changed: - After update from xubuntu i686 version 04.16 to i686 04.18 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 + After update from xubuntu i686 version 16.04 to i686 18.04 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 ** Description changed: - I had 32-bits OS of Xubuntu from 04.16, and answered yes to be upgraded into 04.18 on my HP EliteBook 6930p laptop. + I had 32-bits OS of Xubuntu from 16.04, and answered yes to be upgraded into 18.04 on my HP EliteBook 6930p laptop. Severals error came up after the reboot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Thu Aug 23 22:30:08 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-22 (1674 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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 + dpkg 1.19.0.5ubuntu2 + apt 1.6.3ubuntu0.1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago) -- 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/1788854 Title: After update from xubuntu i686 version 16.04 to i686 18.04 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: New Bug description: I had 32-bits OS of Xubuntu from 16.04, and answered yes to be upgraded into 18.04 on my HP EliteBook 6930p laptop. Severals error came up after the reboot. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic i686 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: i386 Date: Thu Aug 23 22:30:08 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2014-01-22 (1674 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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: systemd Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788958] [NEW] /usr/bin/file fails with Bash process substitution
Public bug reported: == System information == Description:Ubuntu 16.04.5 LTS Release:16.04 file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages == Expected behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: POSIX shell script, ASCII text executable == Actual behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: broken symbolic link to pipe:[10687339] Note that Bash process substitution does work properly in general: $ /bin/cat <( echo '#!/bin/sh' ) #!/bin/sh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 24 18:07:43 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (661 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1788958 Title: /usr/bin/file fails with Bash process substitution Status in file package in Ubuntu: New Bug description: == System information == Description: Ubuntu 16.04.5 LTS Release: 16.04 file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages == Expected behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: POSIX shell script, ASCII text executable == Actual behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: broken symbolic link to pipe:[10687339] Note that Bash process substitution does work properly in general: $ /bin/cat <( echo '#!/bin/sh' ) #!/bin/sh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 24 18:07:43 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (661 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file/+bug/1788958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788958] Re: /usr/bin/file fails with Bash process substitution
Reported upstream at https://bugs.astron.com/view.php?id=32 ** Bug watch added: bugs.astron.com/ #32 https://bugs.astron.com/view.php?id=32 ** Also affects: file via https://bugs.astron.com/view.php?id=32 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to file in Ubuntu. https://bugs.launchpad.net/bugs/1788958 Title: /usr/bin/file fails with Bash process substitution Status in osFileManager: Unknown Status in file package in Ubuntu: New Bug description: == System information == Description: Ubuntu 16.04.5 LTS Release: 16.04 file: Installed: 1:5.25-2ubuntu1.1 Candidate: 1:5.25-2ubuntu1.1 Version table: *** 1:5.25-2ubuntu1.1 500 500 http://mirror.atlantic.net/ubuntu xenial-updates/main amd64 Packages 500 http://mirror.atlantic.net/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1:5.25-2ubuntu1 500 500 http://mirror.atlantic.net/ubuntu xenial/main amd64 Packages == Expected behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: POSIX shell script, ASCII text executable == Actual behavior == $ /usr/bin/file <( echo '#!/bin/sh' ) /dev/fd/63: broken symbolic link to pipe:[10687339] Note that Bash process substitution does work properly in general: $ /bin/cat <( echo '#!/bin/sh' ) #!/bin/sh ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: file 1:5.25-2ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-30-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 24 18:07:43 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libmagic1 1:5.25-2ubuntu1.1 zlib1g 1:1.2.8.dfsg-2ubuntu4.1 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2016-11-01 (661 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 SourcePackage: file UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/file/+bug/1788958/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788973] [NEW] aa-logprof not useful in an lxd instance
Public bug reported: Hello, aa-logprof doesn't do anything useful in an lxd instance: First, I remove the /** mrixwlk, rule from the man profile, so I'll be sure to have an easy way to create a denial. Then I generate a denial, install aa-logprof, and run aa-logprof. The aa-logprof output looks identical to a run with no denials at all. I do not know what to suggest -- discovering we're in a container of some sort and reporting that the tools might not work seems like the best we can do, but that might be wrong in the future, and might not be easy to get right today. Thanks root@u18:/etc/apparmor.d# vim usr.bin.man root@u18:/etc/apparmor.d# sudo apparmor_parser --replace usr.bin.man root@u18:/etc/apparmor.d# man man Segmentation fault root@u18:/etc/apparmor.d# aa-logprof Command 'aa-logprof' not found, but can be installed with: apt install apparmor-utils root@u18:/etc/apparmor.d# sudo apt-get install apparmor-utils [...] Setting up python3-libapparmor (2.12-4ubuntu5) ... Setting up python3-apparmor (2.12-4ubuntu5) ... Processing triggers for man-db (2.8.3-2) ... Setting up apparmor-utils (2.12-4ubuntu5) ... root@u18:/etc/apparmor.d# aa-logprof Reading log entries from /var/log/syslog. Updating AppArmor profiles in /etc/apparmor.d. root@u18:/etc/apparmor.d# tail -30 /var/log/syslog Aug 24 12:17:01 u18 CRON[14753]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 13:17:01 u18 CRON[14760]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 14:04:26 u18 systemd[1]: apt-daily.service: Failed to reset devices.list: Operation not permitted Aug 24 14:04:26 u18 systemd[1]: Starting Daily apt download activities... Aug 24 14:04:27 u18 systemd[1]: Started Daily apt download activities. Aug 24 14:17:01 u18 CRON[14816]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 15:17:01 u18 CRON[14822]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 16:17:01 u18 CRON[14828]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 17:17:01 u18 CRON[14834]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 18:17:01 u18 CRON[14841]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 19:17:01 u18 CRON[14847]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 19:49:26 u18 systemd[1]: motd-news.service: Failed to reset devices.list: Operation not permitted Aug 24 19:49:26 u18 systemd[1]: Starting Message of the Day... Aug 24 19:49:27 u18 50-motd-news[14851]: * Read about Ubuntu updates for L1 Terminal Fault Vulnerabilities Aug 24 19:49:27 u18 50-motd-news[14851]:(L1TF). Aug 24 19:49:27 u18 50-motd-news[14851]:- https://ubu.one/L1TF Aug 24 19:49:27 u18 50-motd-news[14851]: * Check out 6 great IDEs now available on Ubuntu. There may even be Aug 24 19:49:27 u18 50-motd-news[14851]:something worthwhile there for those crazy EMACS fans ;) Aug 24 19:49:27 u18 50-motd-news[14851]:- https://bit.ly/6-cool-IDEs Aug 24 19:49:27 u18 systemd[1]: Started Message of the Day. Aug 24 20:17:01 u18 CRON[14881]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 21:17:01 u18 CRON[14887]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 22:17:01 u18 CRON[14893]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 24 23:17:01 u18 CRON[14900]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 25 00:17:01 u18 CRON[14906]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Aug 25 00:24:01 u18 CRON[14910]: (root) CMD ( test -x /etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest --crond) Aug 25 00:59:26 u18 systemd[1]: systemd-tmpfiles-clean.service: Failed to reset devices.list: Operation not permitted Aug 25 00:59:26 u18 systemd[1]: Starting Cleanup of Temporary Directories... Aug 25 00:59:26 u18 systemd[1]: Started Cleanup of Temporary Directories. Aug 25 01:17:01 u18 CRON[14918]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) root@u18:/etc/apparmor.d# ** Affects: apparmor Importance: Undecided Status: New ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor Importance: Undecided Status: New -- 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/1788973 Title: aa-logprof not useful in an lxd instance Status in AppArmor: New Status in apparmor package in Ubuntu: New Bug description: Hello, aa-logprof doesn't do anything useful in an lxd instance: First, I remove the /** mrixwlk, rule from the man profile, so I'll be sure to have an easy way to create a denial. Then I generate a denial, install aa-logprof, and run aa-logprof. The aa-logprof output looks identical to a run with no denials at all. I do not know what to suggest -- discovering we're in a containe
[Touch-packages] [Bug 806120] Re: ~/.xsession does not get run but Xsession(5) still says it does
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/806120 Title: ~/.xsession does not get run but Xsession(5) still says it does Status in xorg package in Ubuntu: Expired Bug description: Xsession(5) still says that $HOME/.xsession can contain commands for invoking X clients. But in natty $HOME/.xsession does not get run. (/etc/X11/Xsession sources all the scripts in /etc/X11/Xsession.d/ and /etc/X11/Xsession.d/50x11-common_determine-startup only sources the user's .xsession if the STARTUP variable has not been set. But it has been set, to "gnome-session --session=ubuntu".) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: xorg 1:7.6+4ubuntu3.1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2 Uname: Linux 2.6.38-8-generic-pae i686 Architecture: i386 CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,move,regex,mousepoll,place,gnomecompat,imgpng,animation,wall,resize,workarounds,wobbly,unitymtgrabhandles,session,expo,ezoom,staticswitcher,fade,scale,unityshell] CompositorRunning: compiz Date: Tue Jul 5 20:43:40 2011 DistUpgraded: Log time: 2010-10-12 10:35:08.860007 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: virtualbox-ose, 4.0.4, 2.6.38-8-generic-pae, i686: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo T61 [17aa:20b5] Subsystem: Lenovo T61 [17aa:20b5] InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) MachineType: LENOVO 7673CTO PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: LANGUAGE=en_IE:en PATH=(custom, user) LANG=en_IE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=07f57763-4d3a-4045-8f1a-e5224fa61703 ro mem=4096M quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: xorg UpgradeStatus: Upgraded to natty on 2011-03-24 (103 days ago) dmi.bios.date: 11/27/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETB9WW (2.19 ) dmi.board.name: 7673CTO dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETB9WW(2.19):bd11/27/2008:svnLENOVO:pn7673CTO:pvrThinkPadX61:rvnLENOVO:rn7673CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7673CTO dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.4+bzr20110606-0ubuntu1~natty1 version.libdrm2: libdrm2 2.4.23-1ubuntu6 version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2 version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/806120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788894] Re: Hash Sum mismatch: DEP-11 Icons
@ximion I tried to delete the cache directory manually (`rm -rf ~/.cache/snapcraft/`) and then run `snapcraft` again. Nothing changed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1788894 Title: Hash Sum mismatch: DEP-11 Icons Status in Launchpad itself: New Status in Snapcraft: New Status in appstream package in Ubuntu: Invalid Status in apt package in Ubuntu: New Status in snapcraft package in Ubuntu: New Bug description: During update with apt, checking dependencies for a snap: Get:1 http://archive.canonical.com/ubuntu bionic InRelease [10.2 kB] Get:2 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:3 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic InRelease [15.4 kB] Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:5 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2344 B] Get:6 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:7 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2340 B] Get:8 http://archive.canonical.com/ubuntu bionic/partner Translation-en [1272 B] Get:9 http://archive.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Get:10 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main amd64 Packages [1068 B] Get:11 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main i386 Packages [1072 B] Get:12 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1019 kB] Get:13 http://ppa.launchpad.net/mc3man/mpv-tests/ubuntu bionic/main Translation-en [356 B] Get:14 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages [1007 kB] Get:15 http://archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:16 http://archive.ubuntu.com/ubuntu bionic/main amd64 DEP-11 Metadata [477 kB] Get:17 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 48x48 Icons [118 kB] Get:18 http://archive.ubuntu.com/ubuntu bionic/main DEP-11 64x64 Icons [245 kB]
